docs(2c-G): record the owner's rulings verbatim and freeze the amendment (recovers #861's unmerged freeze commit) - #862
Merged
Conversation
…terialization, auto and explicit catch-up, a fresh baseline after every catch-up, three sequential PRs Records the owner's four rulings of 2026-09-11 verbatim in a new §0: - G1+G2: catch-up applies already-certified settlements oldest-first through the existing DlvOwnerApplyV2 machinery, as materialization only. It consumes certified history and never creates it. - Catch-up runs from storage.sync and from an explicit request, both through one shared idempotent engine, and gates nothing. - G3: after every successful catch-up, a fresh AnchorPresentationV3 is published over exactly the caught-up V_n. A partial catch-up anchors only the last fully materialized generation. - G4 and delivery: three sequential PRs, each cut from updated main after its predecessor merges — PR 1 = G1+G2, PR 2 = G4, PR 3 = G3.
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.
Recovery PR for #861. #861 merged at its draft head
d034c6d7, which was the survey only. The commit that froze the owner's rulings,78d4b088, was pushed to the branch but never reached main. This is the same PR-head divergence as #859/#860. This PR carries that commit, cherry-picked unchanged onto current main (c686af48).What it changes
It touches one file,
docs/papers/amendment-2c-g-owner-catch-up-survey.md:storage.syncplus an explicit API. Both use one shared idempotent engine. Catch-up gates nothing: not trader settlement, realization, composition, admission, QuorumBind, fence release or close finality. A failure stays local, and there is no re-entrant sync loop.It makes no code change.
Head check
Local, remote and PR head should all be
910f37b6. Run./scripts/check-pr-head-sync.sh <this PR>before merging.