Concepts
Receipts
A Receipt is a retrievable evidence object representing a particular recorded ECZ-ID event, decision, action, result or state at a point in time. A Receipt proves what the recording system recorded.
ECZ-ID Core records receipts today. Public, unauthenticated retrieval and verification are not enabled, and Receipts plans are not yet on sale in TrustOps. A Receipt proves what the recording system recorded, not that every underlying real-world assertion was true.
ECZ-ID Receipts today · measured 2026-10-10
- Commercial capability
- Not yet on saleNo Receipts plan is offered in TrustOps yet.
- Signed-in operation
- Recorded by CoreCore records eligible events today, and public records show how many. Receipts plan features (retention, search, history) are not yet available.
- Public developer interface
- No public retrievalPublic retrieval and public verification of individual receipts are not enabled.
Accountability Chain:Receipt
What a Receipt is
A Receipt is an evidence object with an identifier such as RCP-202610-…, a type, an issuer, the parent organisation, references to its subject, actor, counterparties and authority, and the times the fact was recorded and took effect. Its receipt_hash is a SHA-256 digest over the canonical JSON of every other field except the signature.
Intent, decision, Receipt and LedgerCore
| Object | What it is |
|---|---|
| Intent | What was proposed and authorised: the objective and its bounds. |
| Decision | What ECZ-ID determined about one proposed action. |
| Receipt | What was recorded, as a retrievable evidence object. |
| LedgerCore | The integrity, retention and anchoring layer for eligible Receipt evidence. It is not the Receipt. |
What a Receipt can record
The Core contract defines receipt types for resolutions, historical resolutions, identity state, counterparty and reliance checks, Intent lifecycle changes, IntentControl decisions, mediation, bindings, watched changes, actions, results, reciprocal trust and evidence pack manifests. Core’s receipt service natively emits four of them: Intent lifecycle, IntentControl decision, mediation and binding. None is publicly retrievable yet.
- A decision Receipt records a decision. Allow means every configured check passed for that one action; it is not evidence that the action was taken, succeeded, or was safe, lawful or correct. It never claims enforcement.
- A mediation Receipt records that an inline enforcement point reported applying the decision, and that Core judged the report consistent. An action that bypassed the point is not covered, and mediation is not the action’s result.
- A binding Receipt records a decisive binding event. A binding reaches bound only through Core’s challenge and evidence verification; payment never creates one.
Integrity, honestly stated
| Integrity mode | Status |
|---|---|
HASHED | What Core issues today. The receipt hash covers every field but the signature. |
ANCHORED | Never claimed at issuance. A verifier reports it only after reading the LedgerCore anchor back. |
SIGNED, SIGNED_AND_ANCHORED | Never claimed. No receipt-signing key custody is deployed, and signature is null in v1. |
Receipts hold references and digests, never payloads. Core refuses to store parameters, prompts, request or response bodies, card data, secrets, passwords, private keys, tokens, email addresses or documents in a Receipt.
What a reader can see today
The live record reports receipt state without exposing receipts. For this site’s operator on 2026-10-09: evidence.public_receipt_state is NO_PUBLIC_RECEIPT, recorded_receipts_count is 1, and the reason code is RECEIPTS_RECORDED_NOT_PUBLICLY_RETRIEVABLE. Recorded is not published.
Related
This page is explanation, not authority. Current state is only ever the live Resolver record. Live facts on this page were measured read-only on 2026-10-10.