Repository navigation
Delete the transition-admission rows the deleted wall left behind - #11771
Merged
Merged
Conversation
…before the carrier cut gunbc#11704 made a file under dag/gunbc/namespace/transition_admission/ refuse on every required run. #11529 and #11484 squash-merged immediately BEFORE it, each leaving its rows in the tree, so main carries 11 of them and every required run refuses at tree_carried_admission_refusal. Every row is owned by one of those two merged pull requests and its motion is on main, which is the consumed-by-its-own-merge state the carrier cut exists to make unreachable. Nothing else reads them: admissions are now carried in the commit messages of the change that needs them. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
gunbai-bot
Bot
changed the title
…made false #11774 deleted the namespace-wave-admission wall, the roster and the types. Seventeen row files landed by other lanes survive on main, each importing the deleted gunbc.namespace.transition_admission; this deletes them all. consumed_row_owner_charge_unenforced is UN-RETIRED: gunbc#11704 fired its trigger and #11774 deleted the capability that fired it, so the retirement is un-done rather than left standing on a mechanism the tree no longer carries. The class is now subsumed by namespace_wave_admission_wall_removed, which the row points at. The failure-mode row likewise stops claiming a live mechanism. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Ledger-Repair-Judged: docs/design-rung-drops.md Ledger-Rows-Repaired: docs/design-rung-drops.md namespace_wave_admission_wall_removed Heal-Candidate-Run: 35486969243
…8-rows # Conflicts: # docs/design-rung-drops.md
gunbai-bot
Bot
changed the title
…o session/zesty-crab-208-rows # Conflicts: # docs/design-rung-drops.md
…w 68971) Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Ledger-Repair-Judged: docs/design-rung-drops.md Ledger-Rows-Repaired: docs/design-rung-drops.md consumed_row_owner_charge_unenforced Ledger-Rows-Repaired: docs/design-rung-drops.md roadmap_sizing_authored_to_derived Ledger-Rows-Repaired: docs/design-rung-drops.md roadmap_live_forecast_new_witness_eval_step_cost Ledger-Rows-Repaired: docs/design-rung-drops.md roadmap_page_style_new_witness_eval_step_cost Heal-Candidate-Run: 35495912741
…o session/zesty-crab-208-rows # Conflicts: # docs/design-rung-drops.md
Ledger-Repair-Judged: docs/design-rung-drops.md Heal-Candidate-Run: 35497982231
gunbai-bot Bot
pushed a commit
that referenced
this pull request
Sep 24, 2026
…rovenance The six transition_admission paths go back into v2.compiler.reference_conservation_census reference_conservation_stratified_sample_paths. The sample is pinned to fec339d and declared byte-for-byte rerunnable, with at least six paths per stratum. The census renders an unreadable path as its own `unreadable` line, never an omission, so a deleted path belongs in that rendering, not in a shrunken list. Recomputing the sample is not this change's work. CORRECTION to the first commit's message, which named the wrong landing PRs and a wrong count. The 56 surviving rows came from gunbc#11625 (32), #11565 (10), #11667 (10) and #11689 (4). #11681 contributed none: its 13 rows were already deleted by #11696. #11771 removed 23 rows, not 17. Co-Authored-By: Claude Opus 5.5 (1M context) <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
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.
#11774 deleted the namespace-wave-admission wall, its roster type module
gunbc.namespace.transition_admission, and the phase that read it. It did not delete the row files other lanes had already landed, and lanes whose branches predate it keep adding more: main carried 11 when I opened this, then 17, then 23.This deletes every file under
dag/gunbc/namespace/transition_admission/, leaving the directory empty — the state #11774's own drop row describes ("the roster directory ... is deleted with the wall"). Each row imports the type module that PR deleted, so they resolve to nothing; nothing else in the tree imports them.Two rows of mine that #11774 made false, corrected here
gunbc.rung_drop.consumed_row_owner_charge_unenforcedis un-retired. namespace-wave-admission: admissions carried by the change, never by the tree #11704 fired its trigger; Remove the namespace-wave-admission required CI gate (operator ruling 2026-09-19) #11774 then deleted the capability that fired it, so leaving it Retired would report a rung held by a mechanism the tree no longer carries (DESIGN §4b(1)). It returns to Standing, records that sequence, and hands the class tonamespace_wave_admission_wall_removed, which carries the real restoration trigger. This follows theUN-RETIRED 2026-09-04precedent already in that file.consumed_admission_externalized_to_the_next_roster_touchstops claiming a live mechanism: the class was briefly at rung 2 on every required run and is now held by nothing.Evidence, and one gap I did not close
src/v2/workflow/floor_naming_hygiene.dag— that was my branch being behind main's repair (main repair: attach floor_naming_hygiene's module header to its declaration #11780), fixed by merging main, not a defect of this change.docs/design-rung-drops.mdis taken from main unedited. I first hand-edited it, then ran the projection regenerator and it disagreed with my edit. I am not hand-writing a generated file twice: the generated-artifact phase regenerates it from the.dagrows, and heal repairs any drift. If that phase reds, the repair is the generator's bytes, not mine.🤖 Generated with Claude Code