fix(knowledge): bind declared candidate state and retrieval evidence - #197
Merged
Conversation
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.
KB improvement previously copied and hashed only the default pages, raw evidence, and source registry. Custom page layouts and research records could therefore remain outside the measured candidate. This change adds an explicit
stateScopefor the pages directory and opt-in canonical claim ledgers/events, then uses that scope consistently for snapshots, indexes, resume, selected candidates, promotion, and transaction recovery. Default snapshot identities remain unchanged.The public normalizer lets Runtime carry the same canonical scope into portable candidates.
The Eval peer range admits 0.176 while retaining the tested 0.174 floor.
Configured
createKnowledgeToolsreceipt capture now persists and reuses the exact visibility artifact before delivering a receipt. Receipts contain the existing artifact reference, and conflicting stored bytes fail before delivery. Structural scoring remains distinct from caller-provided downstream evaluation.Validation:
Additional compatibility validation:
a6210768).d208244. The local focused set passed 15 cases and explicitly skipped six Linux-only candidate workflows.d208244after aligning its peer-range assertion.The scope excludes derived indexes, locks, transaction journals, retrieval artifacts, and external providers. Applications must separately bind external mutable state and retain visibility files with their receipt records. No paid inference, release publication, or production mutation was performed.