Repository navigation
Re-derive both recurring-failure-mode projections - #10102
Merged
Merged
Conversation
Closed
6 tasks
gunbai-bot
Bot
force-pushed
the
session/keen-ant-717
branch
from
September 2, 2026 18:09
04cee74 to
3e2ce1a
Compare
briansrls
pushed a commit
that referenced
this pull request
Sep 2, 2026
Fourth collision on dag/gunbc/recurring_failure_mode.dag, and the first that was NOT a disjoint append on both sides. Main had REVISED recurrence_ledger_scoped_below_the_recurrence -- #10030's rename of floor_cost_contention_verdict to floor_cost_claim_qualification_unavailable -- while this branch carried the pre-rename copy inherited from an earlier merge. A theirs-then-ours union therefore produced 63 declarations for 62 unique names. Resolved BY CONTENT AGAINST MAIN, not by position and not first-wins: the surviving copy is byte-identical to origin/main's current bytes, and the resolver REFUSES rather than choosing if neither copy matches. Dropping the other side would have left a closed, compiling tree that silently reverted the rename and cited a symbol that no longer exists. A closure check counts NAMES and cannot see two rows with one name disagreeing about their content, so closure by name is necessary and not sufficient where a name survives on both sides. After: 62 declarations, 62 roster entries, 62 unique each, empty symmetric difference both directions; floor_cost_claim_qualification_unavailable x2, floor_cost_contention_verdict x0. Projections untouched: DESIGN.md and docs/design-ledgers.md byte-identical to the main commit merged here. Compile is deferred to the head that actually gets pushed. Main moved again (#10102 re-derived both projections) while this was being resolved, so verifying this intermediate would verify a tree already superseded. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FdxzwWekWhHR2FCTTf8a1b
gunbai-bot Bot
pushed a commit
that referenced
this pull request
Sep 2, 2026
AUTHORITY ONLY. #10115 filed proxy_observation_mistaken_for_action_semantics and #10102 re-derived both projections, so dag/gunbc/recurring_failure_mode.dag conflicted again. Unioned, with the identity-aware dedupe from the previous commit still applied: no duplicate names arose this time, and the resolver would have refused rather than chosen had a name appeared on both sides with divergent content. Closure on THIS merged tree, both directions, not inherited from either side: 64 declarations, 64 roster entries, 64 unique each, empty symmetric difference. Projections untouched: byte-identical to the main commit merged here. 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.
Summary
Carry the
unhandled_state_falls_to_the_not_yet_armrecurring-failure-mode row from the incomplete #10101 handoff and re-derive both committed projections ofgunbc.recurring_failure_mode_roster:gunbc.design_documentmaps each roster identity into the class index inDESIGN.md.gunbc.design_ledgersmaps each roster's authored text intodocs/design-ledgers.md.An exhaustive repository search for
recurring_failure_mode_rosterfound exactly those two projection consumers. The only other reference is aDeclarationRefingunbc.type_reference_decl_file_occurrence_census, which cites the roster as a census subject and does not project its rows. There is therefore no third projection in this tree.This closes the drift that left the class authority and full ledger updated while the second projection remained stale. Supersedes the incomplete projection update in #10101.
Test plan
gunbcthroughtools.generated_artifact_gate main_wet_one.[file] writereceipts; hashes stayed fixed (DESIGN.md23932ed6dc46cc8e53f0136123bbb379, ledger548ab54724082b6f53d81deaba3465a5) while mtimes advanced, proving the second run rewrote rather than short-circuited.DESIGN.mdcontains the exact ordered identity list; verified the ledger contains 62 rows and the new authored row.git diff --check.cargo fmt --all --checkpassed.