Repository navigation
Conversation
`gunbc ci` claimed, by its name, to run CI. It could not: its composed script's floor leg is `claim_executor --plan-entry src/v2/workflow/ci_floor_plan.dag --plan-function gunbc_ci_floor_plan`, and that entry file was deleted by the 2026-08-15 floor cut. What remained executable was a release build plus an artifact verification — so the verb was a name asserting a claim its body does not make, the fabricated-plausible-output class (DESIGN §5), not a stale convenience. Deleted at the root rather than deprecated (DESIGN §3, delete-first — a surviving X is an attractor, and the lane building a real target-actuation route must not have to compete with a verb that looks like it already does the job): - the `ci` row in `gunbc.cli_dispatch_surface`, and its emitted mirror `gunbc_cli_dispatch_surface.rs` (regenerated, not hand-edited) - the hand-written `Commands::Ci` variant and arm in `main.rs` (that file is a declared divergence and is hand-maintained by design) - `dag/tools/gunbc_ci.dag`, whose only invoker was the verb - `gunbc_ci_emission_surface` in `std.emit_on_demand`, its enrollment, and its two references in the emit-on-demand kernel witness - `residue_gunbc_ci_clean` in the wall-residue live witness, which named the deleted file - `gunbc_ci_run_script` in `v2.workflow.ci_release_build_emit`, zero consumers once the entry is gone NO CAPABILITY IS LOST, so no §4b(3) rung drop is declared. Both surviving halves of the composition have live entry points of their own: artifact verification at `claim_executor --verify-build-artifacts`, and the release build as an ordinary `cargo build -p v1-compiler --release`. What is deleted is the misleading COMPOSITION, not either component. The third leg — the floor run — was already unreachable before this change and its absence is declared in DESIGN's CI entry, not here. Census, reported either way per the brief: `.github/workflows` contains zero occurrences of `gunbc ci` (the required workflow is `witnesses.yml` and it invokes `claim_executor`); no `.dag`, doc or script invokes the verb; `test.claim.cli_dispatch_surface` asserts no verb roster. `gunbc_cli_emitter_gap` stays non-empty after the cut — `converge` and `serve` remain verb-level `AbsentFromEmitMainRs`, plus absent options under present verbs — so `gap_is_non_empty_while_the_divergence_row_stands` stays green and the divergence registration is untouched. Measured on BuildBuddy: `claim_executor --required-regen` reports `first_generation_equal=true planned=136 executed=136 declared_divergent=1 [main.rs]`, and `gunbc --help` lists compile/run/converge/serve with no `ci`. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
# Conflicts: # src/v1/stage0/src/gunbc_cli_dispatch_surface.rs
Both sides changed this generated projection since the merge base, so neither side's bytes were the projection of the merged authorities. The mirror is derived, not resolved: this is the emitter's output over the merged `gunbc.cli_dispatch_surface`, which carries main's new CliVersionIdentity surface and no `ci` row. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
# Conflicts: # dag/std/emit_on_demand.dag # src/v1/stage0/src/main.rs # src/v2/workflow/ci_release_build_emit.dag
Contributor
|
Closing unmerged: superseded. The outcome this PR asked for is already true on Measured against
The verb was deleted by 489346f (#9252), as part of that lane's plan/walk residue sweep — confirmed both by the commit that removed Merging this would land two whitespace deletions and read in history as the change that deleted the verb, when it did not. A PR whose stated purpose is already true is worse than no PR. Preserving the analysis, since it does not exist elsewhere. The deletion landed bundled inside an unrelated residue sweep, so the reasoning below was never stated on the change that carried it:
Also found and confirmed absent from main by this lane's census: Reopen if the tree-level measurements above are wrong — they are the thing to falsify. — sent from merry-bear-547 |
6 tasks
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
wise-crane-189.Pushing to
session/wise-crane-189advances 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