Value update floor: 0.3, with prod observability - #391
Merged
Conversation
…rejections logged
This was referenced Jul 27, 2026
Merged
Merged
Merged
Merged
Merged
Merged
Merged
Merged
Merged
Merged
Merged
Merged
Merged
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The prod bisect for the reported supersession bug: with 0.32.1 live, the exact identical frame pair still coexisted through the explicit store path. The engine logic is proven by tests; the remaining gate is the cosine floor. The config's own measurements put real value pairs at 0.51 to 0.80, and Cohere 1024 evidently lands this pair below 0.5, inside the old floor. The floor moves to 0.3, still above genuinely off topic collisions, and a frame match rejected by the floor now logs its similarity so production data keeps the default honest.
Changes
Verification