Concepts
Receipts and verification
Every answer, abstention, posting and tool decision gets a signed receipt on an append-only chain. Anyone with the verification key can check the chain without trusting the database that serves queries.
A receipt is the record’s account of one event. You, or a reviewer who isn’t you, use receipts to check that the record says what it says and that nobody changed it afterwards.
Events with receipts
Section titled “Events with receipts”| Event | The receipt records |
|---|---|
| A posting | Which entry was posted, through which lane, by whom. |
| An answer | The hash of the context packet, the lines it cited and the model lane that answered. |
| An abstention | Whether the record was silent or the reader wasn’t cleared, and the scope Syderial searched. |
| A tool decision | The tool, a hash of its arguments, the decision and the reason. |
Receipts store hashes of content, never the content. A tool receipt stores the hash of the arguments. A reviewer can confirm the sequence of events is intact without clearance to read what those events contained.
How the chain is built
Section titled “How the chain is built”- Syderial serializes each receipt and each entry to a canonical form and hashes it with SHA-256.
- Each one includes the hash of the one before it, which forms an append-only hash chain.
- Syderial signs each hash with Ed25519.
The chain doesn’t depend on the database that serves queries, so you can check it on its own.
Verifying
Section titled “Verifying”Verification checks three properties in order.
- The hash. Recompute the SHA-256 of the canonical form and compare it with the recorded hash.
- The signature. Check the Ed25519 signature over that hash against the verification key issued with your deployment.
- The link. Check that the recorded previous hash matches the hash of the receipt before it.
A failed check marks the exact receipt where the record and its receipts disagree.
Where you’ll see receipts
Section titled “Where you’ll see receipts”- The model doors return a receipt reference with each answer, next to the standard response fields.
- The MCP door records a receipt for each proposal, commit and tool decision.
- Design partners evaluating Syderial verify the receipts themselves before any commitment.