Type: Node / Attestive Artifact
Working Definition: A receipt is an attestive Record concerning a specific governed Act and its claimed actor, authority, form, inputs, outputs, and time. It makes the claim that the Act occurred as stated auditable without proving occurrence, authorization, validity, or effect by itself.
Function in the Grammar: A Receipt is provenance in an attestive artifact form. A future auditor may consult it to assess whether an institutional Act occurred under the claimed conditions. A governing Rule may require a Receipt for some consequential Acts, but not every Act produces one automatically. The Receipt preserves inspectable claims about actor, authority, instruments, inputs, outputs, and time. Independent assessment still determines authenticity, occurrence, authorization, validity, and effect.
Receipts may be generated at the moment of action or reconstructed later. The creation time and relation to the attested Act must remain explicit because contemporaneity affects assessability without defining the artifact type. Receipts are backward-facing artifacts, designed not to enable the Act but to attest it 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 states whether it was generated at the time of α or reconstructed later
r is stored in Ledger(I) and remains retrievable
Receipt(r) is adequate for audit iff
a future actor can inspect from r what is being attested about α
r is not merely a summary but contains sufficient detail for reconstruction
r identifies its own producer separately from the actor and authority it attributes to α
Examples
| Domain | Act | Receipt |
|---|---|---|
| Law | Court issues a warrant | Signed warrant document with judge's identity, case reference, statutory authority, scope, and date; it attests to the order without proving authority or validity by itself |
| 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; the record supports audit of the claimed vote |
| Digital governance | AI interpretation produced | LLM certificate with model identity, inference parameters, input and output hashes, timestamp, and known limitations; it attests to production conditions rather than proving the interpretation correct |
| Ordinary life | Payment made | A merchant receipt with items, prices, total, payment method, timestamp, and merchant identifier; it supports the payment claim but may still be challenged |
Distinctions
Receipt ≠ Record. A Receipt is a specialized Record whose subject is a governed Act and the conditions under which it is claimed to have occurred. Other Records may represent a Decision's content, a Process, a Claim, or a state without performing this attestive function. A Receipt attests; it does not prove its own subject.
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 Act: "this act occurred, by this actor, at this time, under this authority." Certificates are forward-facing and may support later action. Receipts are backward-facing and support assessment of past Acts. A professional license is a certificate; the Record of the examination that qualified the licensee may serve as 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 offered relative to a Claim under conditions that allow its profile to be assessed. A Receipt is an artifact designed to attest to a governed Act. It may serve as Evidence in a dispute about whether the Act occurred, but that role is neither intrinsic nor self-validating.
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 |
|---|---|
| Concealed reconstruction | A later reconstruction is presented as a contemporaneous Receipt, or its basis is hidden. Where to look: creation metadata that postdates the attested Act without any disclosed derivation from earlier Records. |
| 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
- Review: the governed examination whose claimed completion a Receipt may attest without proving adequacy
- Record: the broader artifact type of which Receipt is the attestive special case
- 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