corral/ledger — the record

Every audit and review corral has recorded, as a hash-linked chain, signed where a key was present. An audit plants faults in a file and runs the project's own tests against each one; a review's findings each carry the script that was executed to test them, and the exit code that came back. Nothing here asks to be believed: re-run any of it.

The whole chain, entry by entry →

Audits

Each audit planted faults in a file and ran the project's own test command against every one. The kill rate is what execution measured, with its 95% interval. A proven gap is a fault the suite missed and a test corral wrote did catch: that test passed on the real code and failed on the fault.

What "reproduced" means here

A finding is reproduced only when a script the reviewer wrote was executed and exited 0 — the contract being: exit 0 if and only if the defect is demonstrated. The other outcomes are kept separate on purpose, because collapsing them is how a could-not-measure turns into a measured zero:

• reproduced ran, exit 0 — the defect was demonstrated.
• not shown ran, non-zero — the claim did not demonstrate.
• never ran the harness could not run it (worktree gone, timeout, missing tool). This grades nobody: it is an infrastructure failure, not a wrong claim.
• no script nothing executable was recorded.

A person's verdict is a separate axis from execution, and it wins: a human confirmed/refuted is recorded as its own signed entry and is never clawed back by a later automatic pass.

Decorrelation, 52 times over

A reviewer seat finds; a different model verifies. The rule is enforced, not requested — the verifier is never the reviewer's model. What actually ran:

• 52 of 55 reviews were verified by a different model.
• 52 were verified by a model from a different vendor (anthropic, google, openai) — so the faults and the grading came from different lineages, which is decorrelation's point rather than its letter.

Seats that ran across this record:

138 finding(s) await a person's verdict →

Reviews

Newest first. Record spans 2026-09-06 to 2026-10-28.

All 55 reviews →

Verify it yourself

The record is a git branch, so there is nothing to trust and nothing to install to read it:

git clone https://github.com/pdbethke/corralai.git corralai
cd corralai
git fetch origin corral/ledger
git checkout corral/ledger      # 162 gzipped JSON entries under scans/

# walk the chain: every hash against its bytes, every link against its predecessor,
# and every signature against the ledger's published key
corral ledger verify --pub 909429443700441a9f662c07c5f1b7110333fd7fb94fb21e8991e40f2cb6dc09 --ledger-repo pdbethke/corralai .

That key is the repository's published LEDGER_PUBKEY, and it is the key this page checked the signatures against. Leave out --pub and corral uses your local certify key if you have one, which did not sign this record, or checks no signatures at all if you do not. Hash and link integrity need no key: any reader can confirm from the files alone that no entry was edited and none removed from the middle.