Repository navigation
Loop 78: Bulk rejection-event validator - #764
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.
Change
Bulk rejection-event validator CLI — reads a JSON list of rejection events, validates each rejection_code against the rejection taxonomy, checks required fields, outputs PASS/FAIL validation report with per-event errors.
Why
F8 in the negative-result infrastructure stretch (Phase F). Enables machine-checkable validation of rejection events before they enter the bulk rejection pipeline. Makes failure data reviewable at scale.
Evidence
make agent-checkall checks passmake validate-rejection-eventsruns against example dataSafety impact
None. Validates structural correctness of rejection events, not biological claims. A PASS result confirms valid fields and known rejection codes, not correctness of rejection decisions. Fail-closed on missing/invalid input.
Proof level
N/A — infrastructure only. No scientific claims affected.
Limitations
Human review needed
No