What a receipt proves
Each decision is hashed with the one before it.
{
"seq": 4,
"action": "superseded",
"memory_id": "2bf9096f-030a-5d19-aec4-dab21a5ec7ab",
"actor": { "type": "system", "id": "curator" },
"reason": "Superseded by 982339dc-2e78-5113-8701-2f08bc26ab4d",
"timestamp": "2026-10-25T19:12:06.321Z",
"prev_entry_hash": "4b3e3c6c01c493c5…",
"entry_hash": "a0e677d68fecb60f…"
}
Three records, three checks
They are separate. Passing one says nothing about the others.
| Record | What it covers | How to check it |
|---|---|---|
| Governance chain | Every save and retirement | brain_audit_verify in Claude (local mode) |
| Anchor log | Chain-head snapshots, in git | verify-anchors.mjs |
| Compile trace | Each optional compile step | ico audit verify |
Break one yourself
Made-up receipts. Edit one, verify, then re-hash forward like someone hiding a change.
With JavaScript on, this panel hashes five illustrative receipts in your browser. Each receipt’s hash covers its text and the hash before it, so editing one breaks verification at that receipt. Re-hashing everything after it makes the chain verify again, but its head then differs from the anchor committed earlier, and that mismatch is the evidence.
- 1 promoted computing intact
- 2 promoted computing intact
- 3 promoted computing intact
- 4 superseded computing intact
- 5 promoted computing intact
Chain loaded. Edit any receipt, then verify.
Check it without trusting us
One file, Node built-ins only. The database check needs sqlite3.
git clone https://github.com/jeremylongshore/bobs-big-brain-plugin node bobs-big-brain-plugin/scripts/verify-anchors.mjs --db ~/.teamkb/teamkb.db
What a receipt does not prove
Prevention
Tamper-evident: it detects edits, it does not prevent them.
Deep rewrites
A rewrite is caught only back to the last anchor.
Outside witness
A local commit is a local witness; push it for an outside one.
Who and whether
It does not show who changed it, or that a memory is true.