Repository navigation
Connect historical Claim batches to the Evidence Review Workbench - #127
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 restored source-grounded historical Claim payloads and PR #126 added bounded 25-Claim review batches. The Evidence Review Workbench still could not load those batches, and its local decision export was not in the exact schema consumed by the persistent review-state tracker.
Changes
Safety
No browser upload, GitHub write, automatic factual verification, company-profile update or model-support promotion is introduced. The existing explicit Approval Manifest and separate manual Evidence-to-PR workflow remain unchanged.
Validation
The PR CI runs the complete Python data validation, static site build and Playwright browser smoke suite.