Every finding carries the command that reproduces it

declared status○declared status: guaranteed Declared deterministic and blocking, implemented, and naming the behavioural test that is to prove it. Whether a recorded run supports it is the evidence verdict, shown beside it.

recorded evidence○recorded evidence: not run Declared guaranteed, and not supported by a recorded run: the test is named, and no passing run of the current inputs is recorded. how evidence is recorded

majordomus doctor
# FAIL wiring      finish-on-push — hook .git/hooks/pre-push does not exist  [reproduce: ls -l .git/hooks/pre-push]
majordomus --json doctor | head -1

Detail rendered from docs/claims/reproduce-command.md.

From the statement to the proof

1. 1 · the public statement

   Every finding carries the command that reproduces it

   Made on Finish contract.

2. 2 · the canonical claim

   reproduce-command○declared status: guaranteed in docs/CLAIMS.yaml

   Defined in read it on this site · docs/DESIGN.md

3. 3 · the implementation

   lib/common.sh

4. 4 · the test and the scenarios

   Test: test/cases/02_doctor_basic.sh

   Executed in Prove a rule is actually enforced, not merely written down, Find out what has drifted since anyone last looked, Gate CI on the tool itself, with an exit code that is a contract.

5. 5 · the recorded runs

   ○recorded evidence: not run how evidence is recorded

Verify it yourself

The test runs in a disposable temporary repository and asserts the behaviour, not a string in the source.

bash test/run.sh 02_doctor_basic

Where this claim is used

Related claims same implementation

• ○declared status: guaranteed The canonical policy is parsed and rejected if it contains an unknown key
• ○declared status: guaranteed Exit codes are a contract, and no code means "warn and continue"
• ○declared status: guaranteed State read back is labelled exact, advanced, diverged or different_context against git
• ○declared status: guaranteed The right prior record is resolved by worktree and branch, and an unrelated one is never offered
• ○declared status: guaranteed A layer installed with --personal is one person's own in a shared repository: it changes no tracked file, no .gitignore line and nothing git status shows, and the command that makes the claim verifies it
• ○declared status: guaranteed Checkout-local state lives under .ai/local/, is ignored by git, and is absent on a fresh clone or worktree
• ○declared status: guaranteed The tool runs read-only from any location, and two locations of one version agree about one repository
• ○declared status: guaranteed The ledger's event vocabulary is closed, on the way in and on the way out

The moments this answers

• → accepted "done" because the model said so, and paid for it the next morning A fluent completion claim is accepted as evidence because nothing wrote down, beforehand, what would have to be true.
• → read a promise in the README that no test stood behind A sentence describing what the software does is written once and never connected to anything that would fail if it stopped being true.
• → pasted a command from the documentation and watched it fail Examples are written once, in prose, and nothing ever executes them again.
• → published a page that promised more than any test could support Public material is written by a different act from the code, so it drifts ahead of the behaviour and nothing brings it back.
• → could not reproduce a result because nothing recorded the state it came from The result is recorded and the conditions that produced it are not, so it is an anecdote rather than a measurement.