Repository navigation
delete the ci floor and any associated rust code - #8284
Closed
gunbai-bot[bot] wants to merge 10 commits into
Closed
gunbai-bot[bot] wants to merge 10 commits into
gunbai-bot[bot] wants to merge 10 commits into
Conversation
…n import The selection-control job died with affected-set selection; cadence_verdict_should_fail still took its outcome, and the topology witness still pinned four jobs. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
….dag authorities
Operator directive 2026-08-15: wipe every single thing in CI; jobs come back one
by one only as agreed. This deletes the three workflow artifacts, the modules that
emitted them, and the witnesses whose only subject was the deleted surface. It adds
nothing. fleet-converge.yml survives untouched -- that is fleet operations, not CI.
WHAT IS GONE
artifacts .github/workflows/{ci,falsifier,falsifier-alert}.yml
registry CiYamlArtifact and FalsifierYamlArtifact rows, their paths, commit
policies, equality arms, generation arms and extra-validation arms
emit gunbc.ci_yaml_emit, gunbc.falsifier_workflow, tools.emit_falsifier_yaml,
and ci_workflow's job surface (ci_job, ci_build_job, ci_regen_job,
ci_heal_generated_artifacts_job, ci_fleet_job, ci_regen_floor_step and
the ci_workflow Workflow value itself)
falsifier lane, run control, cold-corpus execution, and all four alert modules
plan v2.workflow.ci_floor_plan -- entirely, including gunbc_ci_regen_floor_plan.
The regen plan is a real obligation and it returns from the quarry when
the regen job is re-agreed; keeping the obvious survivor is how a deleted
structure grows back.
gate gunbc.ci_materialization_gate (its subject was the ci_workflow value)
witnesses 30 test modules whose subject was one of the above
WHAT SURVIVES, AND WHY
ci_workflow.dag and ci_spec.dag are retained as GitHub Actions STEP vocabulary, not as
CI: fleet_converge_workflow consumes ten step constructors and five timeout rows from
them, and fleet-converge.yml still generates. Every job, the workflow value, and the
floor step are deleted from ci_workflow. The commit gate roster in commit_workflow.dag
is retained deliberately -- it IS the obligations ledger the re-add queue is drawn from,
and deleting it would delete the record of what CI used to owe.
realization_artifact_for_surface now returns GeneratedArtifact? rather than a total
GeneratedArtifact: three of its four surfaces have no artifact after this wipe, and a
surface with no artifact answers none rather than a fabricated plausible one.
THE RUNG DROP, DECLARED (DESIGN section 4b)
previous rung mechanically preventable -- every class below was blocked at merge by
an executing required check
temporary rung mitigatable at best, and for most classes nothing at all: the invalid
state is writable and no mechanism observes it
reason the floor's structure was the thing being deleted; re-adding
obligations onto it would have preserved what the cut exists to remove
population the whole repository, every push, for the duration of the branch
restoration obligations return one at a time from the ledger below, each
re-derived from first principles rather than restored from quarry,
each closing only when the operator is satisfied with its performance
THE OBLIGATIONS LEDGER -- what this deletion actually orphaned
1 build and artifact verify (the release bins every other job consumed)
2 the witness corpus: 48 roster rows on GithubActionsCiJob, plus tree-wide
*_test.dag discovery -- no witness in this repository executes on any push today
3 the regen self-host fixed point: 2 roster rows on GithubActionsCiRegenJob
4 the generated-artifact drift gates -- and note the second-order loss: with the
drift gate gone, .gitattributes and the remaining generated artifacts can now
drift from their authorities silently
5 the seven effect gates in tools.floor_effect_gate_witness: dag compile-clean,
generated-artifact drift, emit-host, extdeps citation, extdeps scope placement,
prose-row introduction, cheap-claim pool
6 the cargo fmt gate (the pre-push hook still runs it locally; that is opt-in per
clone and bypassable, so it is not an authority)
7 heal: repo-local git config convergence, binary/source skew guard, author-commit
8 the falsifier cadence: 8 roster rows on FalsifierCadenceJob, and with them the
cold-corpus control that was the only unselected whole-corpus run in the system
9 compile-clean scope selection, ci.yml drift+parse, merge-admission stamping
The two pre-existing broken modules (complexity_accumulator_copy/analyze.dag,
live_read_classification.dag) are untouched and were already red before this branch.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
Author
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.
Auto-opened by session-dashboard for session
sleek-moth-351.Pushing to
session/sleek-moth-351-floor-deleteadvances 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