Repository navigation
Conversation
…#11742) gunbc#11742 cut the required check to `cargo build --release -p v1-compiler --bin gunbc` on a hosted runner, taking the witness floor and three other phases off the merge path. The fleet was stalled -- ~100 self-hosted runner-minutes per push on ~45 runners, queues to 49 minutes -- so this row records the cost of that decision rather than arguing it. No rung drop was declared. DESIGN section 4b(3) requires a lowered rung to declare previous rung, temporary rung, reason, bounded population and restoration trigger, rostered under `gunbc.rung_drop`; the change touched no row and not docs/design-rung-drops.md. `gunbc.compiler_gate_workflow`'s header does carry the ruling, the measurement and a capability-shaped dissolve-on condition -- and it is a good header. The reason that is not sufficient is that the trigger is SELF-ERASING: the condition ends by deleting the module that carries it, so on the day the gate is restored the only written record of what was lost is removed by the act of restoring it. A drop is retired by its trigger and by nothing else, so a trigger that disappears when satisfied cannot be checked afterwards. The population is stated at four phases, not one: the enrolled witness population, namespace-wave-admission, generated-artifact, the regen fixed point, and the parse sweep. A row naming only "the floor" would understate it. The restoration trigger is the capability -- the gate again plans and executes the enrolled population on the landing revision at a cost the fleet carries -- with three named non-retirements, because each is the plausible mistake: re-emitting the old workflow without the preparation repair, a faster floor still off the merge path, and deleting the stopgap module. docs/design-rung-drops.md is regenerated by tools.docs_projection_gate regen; the other two projections it writes came back byte-identical. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
|
Closing: this is an auto-opened placeholder on The diff GitHub renders here is an artifact of the squash merge — the branch commit is not an ancestor of main, so the branch reads as "ahead" while its content has landed. The two files that genuinely differ differ in main's favour: main carries a newer drop row ( — sent from nimble-wren-52 |
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.
Auto-opened by session-dashboard for session
nimble-wren-52.Pushing to
session/nimble-wren-52-floor-gate-dropadvances this PR.Worker attestation
Before flipping this PR to ready for review, confirm each item:
npm test,cargo test) and the result.Closes #Ndirective.Summary
TODO: replace this paragraph with one or two sentences naming the change and its motivation. Reviewers read this first.
Test plan