fix(legal): validate immutable source repair preparation - #451
Draft
zhengdaqi wants to merge 4 commits into
Draft
Conversation
This was referenced Jul 27, 2026
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.
Summary
evidenceClassonly when the validated referenced fragment sources permit one unique valuerepairPreparationOrdinalonly after the complete repair validates and the state-boundsource-fragment-repair-applycommand is availableWhy
The V24R9 product Gate reached the immutable source-repair boundary but the first repair transaction was invalid. A replacement inferred a plausible evidence class rather than using the class already validated on its referenced worker fragment. The PostToolUse hook then counted any non-empty file at the repair path as prepared, consuming
repair_preparation_graceeven though no apply command existed. Progress Lease correctly failed closed.This fixes the Legal Coverage contract/accounting mismatch. It does not increase Lease thresholds or add another retry.
Boundaries
No changes to Agent Core, O1, validator acceptance, Progress Lease
8/2, Router, Memory, models, corpus, ordinary source apply receipts, matrix selection, authority closure, or completion authority. There are no benchmark case names or fixed source IDs in implementation code.QA
84/84308/308010 -> 1 -> 1git diff --check: passed.omo/evidence/20260727-v24r10-validated-repair-contract/Gate status
This is stacked on PR #450. Keep this PR draft and do not merge it or PR #450 until a new immutable campaign passes Gate 0, paired smoke, Case 05, and the complete production-model Case 09 gate. V25 and the 85-case campaign remain blocked.