docs(plan): RG0 ratified — RT-G13 isolated cutover clamp verified INERT (NOT-A-BUG)#160
Merged
Conversation
…RT (NOT-A-BUG) RG0's ground-truth question (does the isolated historical->realtime cutover adopt a stale-LOW refetched boundary?) is resolved: it does NOT. Upstream's own adoption guard in getHistoricalEventsIsolated breaks before the assignment whenever (finalizedBlock.number - syncProgress.finalized.number) <= finalityBlockCount; a stale-low clamp gives a negative delta, always <= finalityBlockCount, so the below-floor boundary is never adopted. The multichain site's floor: is load-bearing only because that site's post-catchup assignment is unconditional; the isolated site has no such path. Verified three ways: two blind reviewers (independent reasoning + grafted-source read across all pinned versions) plus a first-hand re-check of raw upstream 0.16.9 historical.ts:827-835. RT-G13 reclassified must-verify->must-fix => should-fix: RT-2 still lands the floor for defense/doc-parity, but the mutation-verified test pins the upstream guard (weaken the <= comparison => stale-low block adopted => fail), not the floor. Records the RG0 verdict + marks the RG0 gate MET in the campaign plan. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
RG0 ground-truth ratification
Resolves the RG0 gate's open question: does the isolated historical→realtime cutover adopt a stale-LOW refetched finalized boundary? Answer, verified: no — it is guarded, not unconditional.
Mechanism (upstream, not the fork)
getHistoricalEventsIsolatedinpackages/core/src/runtime/historical.tsbreaks before the boundary assignment wheneverand only otherwise runs
params.syncProgress.finalized = finalizedBlock. A stale-LOW clamp yields a negative delta, always<= finalityBlockCount(≥ 0), so thebreakfires and the below-floor boundary is never adopted. The multichain site'sflooris load-bearing only because its post-catchup assignment is unconditional; the isolated site has no such path.Verification
historical.ts:827-835.Disposition
RT-G13 reclassified must-verify→must-fix ⇒ should-fix. RT-2 still lands the
floorfor defense / doc-parity, but its mutation-verified test pins the upstream guard (weaken the<=comparison ⇒ a stale-low block is adopted ⇒ test fails), not the floor — removing the floor alone cannot fail the test.Docs-only: marks the RG0 gate MET and records the verdict in the RT-G13 register entry + summary.
🤖 Generated with Claude Code