Repository navigation
Correct factual rung-drop restoration claims - #9925
Merged
Merged
Conversation
gunbai-bot
Bot
force-pushed
the
session/clever-hawk-149-drop-facts
branch
from
September 1, 2026 11:23
d51d256 to
9b4553e
Compare
added 6 commits
September 1, 2026 11:48
…49-drop-facts # Conflicts: # dag/gunbc/rung_drop.dag # docs/design-ledgers.md
…49-drop-facts # Conflicts: # docs/design-ledgers.md
…49-drop-facts # Conflicts: # DESIGN.md # docs/design-ledgers.md
…49-drop-facts # Conflicts: # DESIGN.md # docs/design-ledgers.md
…49-drop-facts # Conflicts: # DESIGN.md # docs/design-ledgers.md
briansrls
pushed a commit
that referenced
this pull request
Sep 1, 2026
Pure-projection conflict: DESIGN.md and docs/design-ledgers.md, no .dag authority conflict. Both regenerated with main_wet_one on their own path. Verification note, because the superset check did NOT come back clean this time and the discrepancy is the interesting part: three lines present on the ours side are absent from the regenerated files. All three are rows #9925 amended or retired on main -- the regenerated text for both ledger rows is byte-identical to the theirs side, and the DESIGN.md drop index goes 26 -> 25 because main retired a row. So the regeneration follows the merged authority rather than dropping content; the ours-side lines are stale projections of authorities main has since corrected. Theirs-side missing=0 on both files, and this branch's own additions (one_refusal_two_destinations, the dated ceiling row) are present. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FdxzwWekWhHR2FCTTf8a1b
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.
Outcome
Corrects two factual defects found while auditing standing
RungDroprestoration triggers against DESIGN §4b(3):emit_stage_blockingcondition and labels only the exhaustive whole-roster capability as the restoration trigger;regen_produceron executed evidence that candidate production is unconditional, then moves the still-mitigatable hand-maintained host mirror to its ownGuaranteeStallinstead of extending the retired drop with a new obligation.Executed regen evidence
The probe lived only on closed throwaway draft PR #9919. Its deliberate drift was reverted to the exact pre-probe tree before the clean arm:
6beb63bc5bcea490e449371d55822238e0635daa33498757658, job99826921457;planned=149 executed=149 adjudicated=149,first_generation_equal=false,candidate=target/stage0-regen-candidate, then refusal onv1_std_core.rs33500467935, job99832373188;planned=149 executed=149 adjudicated=149,first_generation_equal=true,candidate=target/stage0-regen-candidate; required build lane passedTogether the arms establish production before adjudication on both verdict paths. The drift arm alone would only have established conditional production.
Generated projections and merge receipt
The hand projection at
330a2d7831awas byte-exact and still incomplete: CI run33504368058, job99844904359examined all 35 generated artifacts, matcheddocs/design-ledgers.md, and identifiedDESIGN.mdas the sole drift. The authority projects into two artifacts and only one was refreshed; the actuator writes a set, while a hand writes the member it is thinking of.Generator idempotence was subsequently established repeatedly with byte-identical two-pass local
main_wet_oneruns over both paths named by the dry gate. CI's generated-artifact phase independently regenerates and compares the committed set.Two deliberately scheduled final integration laps then measured the missing landing mechanism:
e39d014988, regenerated and parsed both projections twice, and pushed head0c2f2268a33. Both passes producedDESIGN.mddigestb559dfc7b2cbe9bd877692059c5b81c4a387e33625eef506fc5b46d394215a43and ledger digest975b639e1e935b5a7237db618555bca9205a8b73799a8d4eb616e5595c74794a. Main advanced before the immediate post-push merge-tree probe.4c6e5dfcd4, regenerated and parsed every named projection once, and pushed current head0a8bf30b97c. It producedDESIGN.mddigest09a5854cbb64732e5ffacd319029d328b212606c982df641796fdb902e3f574aand ledger digest8fc48e87576be86d54e5d54f426172ab04f42fcb4e2c0658e3a9c5d8b7e715b1. The second pass was deliberately omitted because it establishes generator idempotence, already repeatedly measured and independently backed by CI, while pass one itself is the lap-specific parse and projection. Main again advanced before the immediate post-push merge-tree probe.The last ten observed main-merge gaps were 357, 562, 1527, 888, 2314, 285, 1099, 256, 716, and 11 seconds (median about 640 seconds; four under 400 seconds). The single-pass lap merged
4c6e5dfcd4at 15:35:35; main advanced to792d6e3466at 15:41:32, a 357-second gap shorter than the reduced lap. No positive-duration regenerate/push sequence can reliably beat an 11-second short tail. Regeneration, push, and merge therefore need a serialized stale-base-refusing landing window; further unsynchronized laps are unbounded churn.The branch tree at
0a8bf30b97cis correct against the authority it merged:recurring_failure_mode.daghas 36 declarations and 36 roster entries, declared-minus-rostered and rostered-minus-declared are empty, there are zero conflict markers, both parent-minus-resultRungDropidentity joins are empty, and both projections were generated once against and parsed with the merged authority. What stands between this tree and merge is the absence of a serialized landing window, not a defect in the tree.Checks
main_wet_onefor every path named by the dry gategit diff --checkcargo fmt --all --check