Front page

What is true now, after every correction?

Append-only memory keeps every claim. Canon Transactions replays the whole record set through one canonical resolver, so the newest row never wins by accident and a retirement never erases the history that produced it.

Record set as filed
r1	claim	rev 1	superseded
r2	correction	rev 2	superseded
r3	dispute	rev 2	weighed
r4	correction	rev 3	canonical
r5	revocation	rev 3	retires r1

The record keeps its history; canon selects the current line.

Resolver: cmd/resolve.mjs
Record events: claim · correction · dispute · revocation
Resolution mode: committed ledger replay

Open the canon desk

The canon desk

One entity, one record set, one current answer. Everything below is a single ledger read left to right: what was filed, what the resolver did with it, and which line is canon right now.

Record set on the desk

canon: the one current, in-scope record the agent may rely on
retired: superseded or revoked by an explicit lifecycle link
kept as history: still readable, never promoted to an answer

Untrusted context note filed with the last record

Filed as an untrusted context_note field and scanned by the same resolver. Instruction-like or secret-like text is quarantined; ordinary prose never overrules the committed fixture.

Loading the first committed record set…

Reading the ledger beyond this desk

This desk establishes

One deterministic resolution of the committed record set: the canon, its lifecycle reasoning, and the trace that selected it.

What remains outside this reading

This desk resolves the filed record set. Receipt and cold-recall material are maintained as separate ledger attachments, rather than folded into the current-canon result.

Ledger files worth opening

Read replay/checkpoints.json for the staged resolution, replay/mainnet-receipts.json for the receipt record, PROMPT.md for the contract, and tests/ for assertions.