fix(eval): enforce deciding evidence in knowledge promotion - #210
Merged
Merged
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
Memory activation and RAG promotion now require Eval's complete deciding result.
Insufficient or indeterminate evidence holds promotion, including tied binary safety results whose diagnostic interval is zero-width.
Memory runs capture source-unit mappings before execution and bind them to resume identity.
Adopt Eval 0.181.0 for Knowledge 17.0.0, migrate the held-out release decision type, and derive package checks from the declared peer range.
Document the existing claim and durable final-evidence controls, with an integration test through the actual retrieval wrapper.
Validation:
4882bd58187261fd6e1a5880d677ddfac0408e072fc43e6a78cee9c008c2ebe3.The native run excludes macOS metadata files accidentally included in an earlier transfer.
The package's Linux candidate-containment guard remains intact; optional provider integrations need their external services.