Reference
Receipt reference
The ECZ-ID Receipt (ecz.receipt.v1) field by field: identifiers, types, temporal modes, disclosure profiles, integrity modes and verification.
Core contract
Core records receipts in this shape today. Public retrieval and public verification are not enabled, and Receipts plans are not yet on sale in TrustOps.
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.
- Contract
- Core contractDefined and held by ECZ-ID Core. Documented so you can integrate; Core serves no public schema or endpoint for it.
- Version
ecz.receipt.v1- Machine-readable
- Schema index entry
Accountability Chain:Receipt
Fields
| Field | Content |
|---|---|
schema | ecz.receipt.v1 |
receipt_id | ^RCP-[0-9]{4}(0[1-9]|1[0-2])-[0-9A-HJKMNP-TV-Z]{26}$ |
receipt_type | See types |
issuer | { "kind": "ECZ_ID_CORE", "id": "ecz-id-core" } |
parent_ecz_id | The organisation |
subject_refs, actor_ref, counterparty_refs, authority_refs | References to what the receipt is about, who acted, who else was involved and what authorised it |
links | Related receipts: mediates decision, terminates authorisation, cascaded from, derived from, authorises version |
source | { kind, id, digest } of the source event |
evidence_refs | References to supporting evidence |
body | Type-specific facts; references and digests, never payloads |
issued_at, recorded_at, effective_at, historical_as_of | When issued, when recorded, when the fact took effect, and the instant a historical receipt describes |
temporal_mode | CURRENT, AS_RECORDED_AT or AS_EFFECTIVE_AT |
coverage_status | NOT_APPLICABLE (native, current) or COVERED (historical) |
disclosure_profile | PRIVATE (default), RELYING_PARTY_SHARE or PUBLIC_SAFE |
integrity_mode | HASHED today; see integrity |
anchor_ref | A LedgerCore reference or null. A reference is not an anchor claim. |
signature | null in v1 |
correction_of, supersedes | The receipt this one corrects or replaces, or null |
verification | method: ecz-receipt-verify-v1, the canonicalisation and the route |
meaning | What the receipt is and is not, in words |
receipt_hash | sha256: over the canonical JSON of every field except receipt_hash and signature |
Receipt types
| Type | Emitted natively by Core |
|---|---|
INTENT_LIFECYCLE | Yes |
INTENT_CONTROL_DECISION | Yes (with IntentControl) |
MEDIATION | Yes (with IntentControl) |
BINDING | Yes |
RESOLUTION, HISTORICAL_RESOLUTION, IDENTITY_STATE | Defined |
DCI_COUNTERPARTY, DCI_RELIANCE, RECIPROCAL_TRUST | Defined |
WATCH_CHANGE, ACTION, RESULT, EVIDENCE_PACK_MANIFEST | Defined |
Integrity
| Mode | Claimed when |
|---|---|
HASHED | At issuance. Every native receipt. |
ANCHORED | Never at issuance; only by a verifier that read the LedgerCore anchor back. |
SIGNED, SIGNED_AND_ANCHORED | Never. No receipt-signing key custody is deployed. |
Verification report
Core’s verification report says whether the artifact is VALID, INVALID or NOT_CONFIRMED, whether Core issued it, and reports current state as NOT_EVALUATED. Valid is never current.
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.