Receipt room · the seal

What the seal binds

Every CAIRN output is an entry in an append-only hash chain.

A refusal, retrieved passages, a grounded answer with [n] citations, a held-knowledge card, an integrity report: recompute the chain and an after-the-fact edit shows. That is the whole claim. It is also the whole proof.

Order, kind, content, linkage. Recompute the chain.

The receipt contract

A seal with
stated limits.

The receipt proves how the answer path was recorded. It does not vouch that the underlying documents are right.

Order, kind, content, linkage

The entry hash seals the sequence, the previous-hash link, the kind and the canonical payload. Change any of them and GET /api/ledger/verify returns ok: false with broken_at set to the first broken line.

Every answer path

Refusal, retrieved passages and grounded synthesis each seal a ledger entry. A model is used only to synthesize an answer the record already holds, and every sentence cites [n].

Deliberately not the clock

Wall-clock time stays outside the hash.

The human-readable ts field is not sealed. A receipt proves order and content, not when. Wall-clock trust is a separate problem.

If you need time, record it inside the payload. That field is hashed. Do not treat ts as evidence; recompute the chain.

real output · the live law server
# recompute the chain on the live law box
curl -s https://law.cairnsemantics.com/api/ledger/verify
# → { "ok": true, "count": N, "broken_at": null }

The live instrument

Recompute.
Don't assume.

This check asks the live law server to recompute its chain now. The response is rendered exactly as returned, with its raw JSON available below the result.

live · runs against a real server

Ledger verification · live law server

Does every entry still agree with the chain that contains it?

real output · the live law server

See the refusal become part of the chain, then recompute it yourself.

Enter the matter room →