Type: Node / Attestive Artifact
Working Definition: A receipt is a durable artifact that proves a specific governed act occurred under a specific authority at a specific time — not a record of what was decided, but the attestation that makes it possible to audit that the act happened as claimed.
Function in the Grammar: A receipt is provenance at its most functional: the artifact a future auditor consults to verify that an institutional act was legitimate. Every consequential institutional act generates both a result (a decision, a recognized status, a fulfilled commitment) and a receipt (a proof that the act was performed, by whom, under what authority, using what instruments, at what time). The distinction matters because results can be described without being verified, while receipts make verification possible. A receipt does not guarantee that the act was wise or correct — it proves that it occurred in the form the institution requires for legitimacy.
Receipts are generated at the moment of action, carried forward in the ledger, and consulted during audit. They are backward-facing artifacts: designed not to enable the act but to attest it after the fact to those who were not present.
Formal Pattern
Receipt(r, act: α, institution: I) iff
r specifies: Act(α), Actor(a), Role(a, I), Timestamp, AuthoritySource
r specifies: Form(α): what form the act took (decision, certificate, record, inference)
r specifies: Instruments(α): what tools, rules, or models were used
r specifies: Inputs(α): what the act operated on
r specifies: Outputs(α): what the act produced
r is generated at the time of α, not reconstructed later
r is stored in Ledger(I) and remains retrievable
Receipt(r) is adequate for audit iff
a future actor can verify from r alone that α occurred as claimed
r is not merely a summary but contains sufficient detail for reconstruction
r cannot be produced by an actor who did not have authority to perform α
Examples
| Domain | Act | Receipt |
|---|---|---|
| Law | Court issues a warrant | Signed warrant document with judge's identity, case reference, statutory authority, scope, and date — not the investigative result, the proof that a judge with authority issued the order |
| Finance | Transaction authorized | Transaction record with payer, payee, amount, authorization code, timestamp, and clearing institution — what auditors check to verify the transaction was legitimate |
| Science / publishing | Peer review completed | Review certificate: reviewer identity (or anonymized token), submission reference, review date, editorial decision, and criteria applied |
| Corporate governance | Board votes to approve | Signed minutes with quorum count, vote tally, motion text, and presiding officer — not the outcome, the proof that a valid vote occurred |
| Digital governance | AI interpretation produced | LLM certificate: model identity, inference parameters, input and output hashes, timestamp, known limitations — not the interpretation, the proof that a specific model produced a specific output under specific conditions |
| Ordinary life | Payment made | A receipt from a merchant: items, prices, total, payment method, timestamp, and merchant identifier — the proof that the transaction occurred in the form claimed |
Distinctions
Receipt ≠ Record. A record is the institution's description of what happened — the content of an act, the decision reached, the status changed. A receipt is the attestive artifact that proves the act occurred in the required form. Records describe; receipts attest. A ledger contains both, but they serve different functions: the record answers "what was decided?" while the receipt answers "can we verify this was a legitimate act?"
Receipt ≠ Certificate. A certificate attests to a state or capability: "this person is qualified," "this artifact is authentic." A receipt attests to a specific past event: "this act occurred, by this actor, at this time, under this authority." Certificates are forward-facing (they authorize future acts); receipts are backward-facing (they prove past acts). A professional license is a certificate; the record of the examination that qualified the licensee is a receipt.
Receipt ≠ Ledger Entry. A ledger entry is the institution's record of an act in its ordered memory. A receipt is the artifact that makes that record auditable. A ledger entry may say "post published, human_reviewed: true, 2026-06-26." A receipt would include who performed the review, in what capacity, under what editorial authority, with what inputs considered. Ledger entries support institutional continuity; receipts support institutional audit.
Receipt ≠ Evidence. Evidence is information made available for judgment under conditions that allow its weight and provenance to be assessed. A receipt is a specific artifact designed to prove that a governed act occurred. A receipt may serve as evidence in a dispute about whether an act occurred; evidence in a dispute about what was decided may include the record, the receipt, and many other documents.
Receipt ≠ Proof. Proof is what a sufficient body of evidence establishes — a conclusion. A receipt is a specific artifact type, not a conclusion. A receipt may be one piece of evidence contributing to proof; proof itself is the result of evaluation, not a class of artifact.
Common Failure Modes
| Mode | Description |
|---|---|
| Receipt generated after the fact | A receipt is produced after the act it purports to attest — backdated, reconstructed from memory, or fabricated. Future auditors cannot verify the act occurred when the receipt claims. Where to look: receipts whose metadata suggests creation significantly after the timestamp they carry. |
| Receipt without authority trace | A receipt attests that an act occurred but does not specify the authority under which it was performed. The act is documented but not verifiably authorized. Where to look: receipts that specify actor and timestamp but carry no reference to the rule, role, or constitutional provision that authorized the act. |
| Instrument underspecification | A receipt records the outcome of an act without specifying the instruments used — which version of a rule, which model, which parameters. Future auditors cannot assess whether the instruments used were appropriate. Where to look: receipts for AI-assisted governance acts that record the conclusion but not the model or inference conditions. |
| Receipt treated as record | A receipt is consulted to learn what was decided rather than to verify that a legitimate act occurred. Receipt-as-record confuses the audit function with the governance function. Where to look: institutions that produce receipts but have no process for treating records and receipts as serving different purposes. |
In Substrate
The Substrate receipt is the central audit artifact. Every governed institutional act — a bridge-rule invocation, an LLM interpretation used as evidence, a human review decision, a status change — produces a receipt that includes: the act type and content, the actor's role, the timestamp, the authorizing bridge rule and its version hash, the L5A anchor status at the time, any LLM certificate generated, and the output hash. Receipts are stored in the ledger and indexed for retrieval. The constitutional test for any act: can a future auditor reconstruct from the receipt exactly what acted, under what exact authority, using what exact version, at what exact time?
Cross-References
- Ledger — receipts are stored in and retrievable from the ledger
- Provenance — a receipt is the governance-grade instantiation of a provenance claim for a specific governed act
- Authority — every receipt must cite the authority under which the act occurred
- Institution — receipts are generated by and for institutional acts
- Continuity — receipts are what make the accountability chain reconstructable
- Evidence — receipts may function as evidence in disputes about whether governed acts occurred
- Commitment — receipt of commitment creation is what makes commitments verifiable
- Standing — receipts must reference the recognized institutional eligibility of the actor who performed the act