Repository navigation
Record the first consumer qualification: Cerberus on 0.3.0 - #8
Merged
Merged
Conversation
The Ladder had only ever verified itself. This records its first end-to-end run outside this repository: installed the documented way into a clean HOME, driven against Cerberus's real gates and a real GitHub Actions run, and carried from policy-less BLOCKED through qualification and activation to `READY FOR HUMAN GATE TRUE` under authoritative evidence/3. docs/qualification/cerberus-0.3.0.md holds the install, the consumer's policy (Deep-Sixed/Cerberus#20, which changes nothing but its policy and .gitignore), the qualify table - 12 qualified, 0 disagreeing, 0 uncovered, artifact chain correctly out of scope - the authoritative composite, and six targeted mutations each refused for the reason that names them: a moved worktree, a CI record from another repository, a job that ran another commit, a record under the pre-hardening contract, main's green run imported for this head, and a deleted activation record. Nothing in the verifier was changed to make it pass. Four observations are recorded rather than fixed, so qualification does not become tailoring: compose locating the baseline beside its first argument, the consumer toolchain its local gate needs, the older script pair inside the pinned checkout, and the v0.3.0 tag this session could not push. README's activation paragraph still described adoption as the activation record alone; it now names the committed `evidence` line and the migration window's refusal, and points to the record. Documentation only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016m6di8xFVdwwq949mJx9U1
Deep-Sixed
marked this pull request as ready for review
September 25, 2026 03:17
This was referenced Sep 25, 2026
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.
Work package: consumer qualification. Branched from
mainat6ea587e, the merge of #7. This is the Ladder run end to end outside its own repository, against a real consumer instead of more self-tests. Documentation only: the qualification needed no verifier change.Result
Cerberus at
3956a48(companion PR: Deep-Sixed/Cerberus#20, policy and.gitignoreonly) reachedREADY FOR HUMAN GATE TRUEunder authoritative evidence/3, and every targeted mutation was refused for the reason that names it.install-ladder.shfrommain@6ea587einto a cleanHOME→ runtimec86bf47,evidence-v3.2/0.3.0check-install.shpassesINSTALL CONFORMS, using the bootstrap copyverification.tomladopting evidence/3validatejob./scripts/ci.shPASS: 319 passed, managed Python 3.14.5, no drift[ci]artifact chainOUT OF SCOPE (no behavioural gate);ci provenanceand 7ci stepqualified from the real runAUTHORITY SWITCH TRUEEVIDENCE ADMISSIBLE TRUE,DEFINITION CHANGE NONE,CLEAN CLIMB TRUE,READY FOR HUMAN GATE TRUESTALE EVIDENCE 3,STATE MATCH FALSEmain's green run imported for this headAfter restoring, the untouched evidence composes to READY again with no tracked changes.
What's in this PR
docs/qualification/cerberus-0.3.0.md: the full record. Install, the consumer's policy, every step's output, the qualify table, the composite, the mutation matrix, what was not covered, and four observations.README.md: the activation paragraph still described adoption as the activation record alone. It now names the committedevidenceline and the migration window's refusal, and points to the record.Observations, recorded rather than fixed
No verifier change was made to get a pass. Nothing observed let bad evidence through:
composefinds the baseline beside its first argument. With the first record outside.verification/, it reportsGOVERNING BASELINE MISSINGeven though the baseline exists beside the others. It fails closed, but the message is misleading. I hit this in my own first attempt at M4, which was refused for that reason rather than for the contract; the re-run placed the record correctly.gitand Python 3.11+.INSTALL.mdsays to run the bootstrap copy.v0.3.0tag could not be pushed from this session (HTTP 403, the same restriction that refuses branch deletion). The installer pins by commit, so nothing here depended on it.Verification
Climb against
8efda0bbaac6 + sha256:fcc3d0d27665, over a baseline onmainat6ea587e:lint,tests-py311andtests-py314came from CI run35848441550,
testsran locally, and the six judgment rungs are attested.drift: false; Ruff clean.35848441550
and pull_request
35848472183.
🤖 Generated with Claude Code
https://claude.ai/code/session_016m6di8xFVdwwq949mJx9U1
Generated by Claude Code
Generated by Claude Code