Repository navigation
Forward annotation identity hints to array-record scoring - #77
Merged
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.
Array-record scoring accepts identity keys, but the native evaluator never forwards them and the annotation loader drops
_identity_hints. A hinted array above the assignment cap therefore skips residual matching instead of using the identity buckets supported by #62.Load and validate
_identity_hintsfrom.test.jsonannotations and pass top-level array hints into the existing matcher. Accept string, list, and{ "fields": [...] }declarations. Preserve nested declarations for downstream scorers and keep hints outside the inference schema. Below-cap matching and the per-bucket cap are unchanged. This adds no EPR implementation or changes to unified-evidence scoring.Validation:
git diff --check.