product · 05 · the receipts
Receipts.
What a run returns. Department, role, evidence, approval version, spend and state, on one record, replayable from the journal.
A receipt is what a run returns.
Six rows. Department, where it is filed. Role, who did the work. Evidence, what was retrieved and cited. Approval, which version a person decided and when. Spend, reserved before the model was called and settled after. State, what the run reached.
A receipt is not a log line. It is the unit the whole structure is built around: the role's record, the department's drawer, the auditor's binder, and the thing a customer is billed for.
- department
- filed here
- role
- did the work
- evidence
- sources · citations · quality
- approval
- version · principal · time
- spend
- reserved · settled · reconciled
- state
- completed · paused · failed
It can be replayed, not merely read.
Every step, decision and cost of a run is appended to a journal as it happens. The receipt settles the run; the journal lets it be replayed. That is what makes the record more than a claim about the past.
Consumption of an approval authorises one dispatch. If the system stops after that, the action is not retried on its own. Delivery is at least once, and the receipt says so rather than promising exactly-once.
- journal
- every step, decision and cost
- replay
- a run re-read from its journal
- consumption
- one dispatch · at least once · stated
03 · reading a receipt
One strip, a binder, an archive.
one run
One run, one strip.
The operator reads this: six rows for the work just done, the amber row where a person decided.
What exists today, and what is next.
Today a receipt records the run, its approvals, its spend and its journal inside the tenant. Spend is reconciled against provider records, with qualification under representative load still pending.
Next, one ledger across systems, so a run's effect in Route Royal, its charge in Vellon and the identity that acted are read on one receipt. After that, receipts signed by the identity that acted, so a third party can verify them. Neither is claimed before it is in the registry.
- today
- run · approvals · spend · journal, in the tenant
- in design
- one ledger across systems
- after that
- signed receipts, verifiable outside the tenant
The receipts, in figures.
- rows on a receipt
- 6
- department · role · evidence · approval · spend · state
- kept in
- your tenant
- row-level isolation in PostgreSQL
- replay
- from the journal
- every step, decision and cost appended as it happens
- delivery
- at least once
- one dispatch per consumed approval · not exactly-once
- spend
- reserved, settled, reconciled
- representative-load qualification pending
- signed receipts
- not yet
- follows the ledger across systems
as recorded on 1 november 2026 · the capability registry is the authority