Repository navigation
Add deterministic human Claim review batches - #126
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.
Motivation
PR #125 restores full source-grounded payloads for the 2,525-item historical Claim backlog. The remaining gap is operational: reviewers need a bounded, prioritized work packet and a decision template that matches the existing human ledger.
Changes
pendingClaims by triage priority descending, first-seen age descending, then Claim ID.needs_more_evidenceClaims in a separate follow-up queue so they do not repeatedly displace new work.data/intelligence-review-decisions.json.Safety
Expected result
Each weekly discovery run exposes one manageable first-pass batch (up to 25 Claims) and a separate follow-up queue. Once reviewers commit decisions to the existing ledger, handled Claims leave the first-pass queue and the next pending batch advances automatically.