fix(legal): persist ordinary source apply progress - #450
Open
zhengdaqi wants to merge 4 commits into
Open
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.
Summary
V24R9 closes the Legal Coverage observation gap found by the V24R8 Case 09
product run. Successful ordinary source merges now persist a deterministic
state-bound applied receipt, and only a verified current receipt can advance
convergence progress.
This is intentionally stacked on V24R8. It does not change Agent Core, O1,
validator acceptance, Progress Lease
8/2, Router, Memory, the model, thecorpus, immutable source repair, matrix handoffs, or authority closure.
Changes
source-merge-applied-<digest>.jsonafter a successful ordinarysource projection, bound to previous/current state, immutable proposal
path/hash, and exact source IDs.
bytes, exact reviewed source rows, safe paths, size bounds, and replay
identity.
creates one semantic checkpoint and replay creates none.
source status, one-time progress, and replay.
exact preserved Case 09 replay driver/result.
QA & Evidence
write/verify, tampering, forged state, immutable repair compatibility, real
Gateway hook/tool behavior, Router/Memory off fixture, and O1 integrity.
Artifact:
.omo/evidence/20260727-v24r9-durable-source-apply-receipt/focused-legal-gateway.log.cancellations, skips, or todos. Artifact:
.omo/evidence/20260727-v24r9-durable-source-apply-receipt/full-suite.log.74abe7..., applied 4 sources/23 facts to4d3a3c..., and observedprogressOrdinal 1 -> 2 -> 2. Artifact:.omo/evidence/20260727-v24r9-durable-source-apply-receipt/case09-replay-result.json.diff passes
git diff --check.Risks & Residuals
The complete production-model Case 09 has not yet run on V24R9. This PR is
code-, Gateway-, protocol-, and exact-failure-replay verified, but it must not
be merged or used to authorize V25/85 cases until a new immutable campaign
passes Gate 0, paired smoke, Case 05, and complete Case 09.
PilotDeck has no PR CI and no historical Cubic integration, so the committed
local evidence is the available code gate.