docs(2c-G): owner catch-up and owner-side economic admission — survey and frozen rulings - #861
Merged
Merged
Conversation
… and rulings draft, for owner ruling Surveys Req 4.5 and Req 6.31 against main at 5133eaa. Owner apply (dlv.reconcile) and dlv.close both bypass economic admission, although core already has both write sets and the 0x0027 credit arm. The owner's R_econ reserve leaf therefore stays at the birth generation. Because the write sets require the leaf at exactly the parent generation, no owner apply past the first and no close can be admitted, and close proceeds never reach R_econ. This is a completeness gap on the critical path to the two-asset E2E, not a safety defect. Proposes G1 (admit the owner apply, with the 0x0027 evidence built from the certified fold's own Req 21.16 material), G2 (catch-up as ordered admitted applies), G3 (a fresh owner baseline after catch-up, Req 6.31) and G4 (admit the close), with the alternatives. Nothing is frozen and no code changes.
cryptskii
marked this pull request as ready for review
September 11, 2026 12:54
cryptskii
changed the title
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
1 participant
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.
For owner ruling — do not merge before the rulings
docs/papers/amendment-2c-g-owner-catch-up-survey.mdsurveys Req 4.5 and Req 6.31 (owner catch-up) againstmainat5133eaa2. No code changes; nothing is frozen.Finding. Owner apply (
dlv.reconcile) anddlv.closeboth bypass economic admission, although core already has theDlvOwnerApplyandDlvWithdrawwrite sets and the0x0027credit arm. The owner'sR_econreserve leaf therefore never leaves the birth generation. Because both write sets require the leaf at exactly the parent generation, no owner apply past the first and no close can be admitted, and close proceeds never reachR_econ. This is a completeness gap on the path to the two-asset E2E, not a safety defect.Proposed rulings:
0x0027evidence built from the certified fold's own Req 21.16 material.The alternatives are in §5. PR #860 is merged; this is independent of it.