Skip to main content
The object

Decision Receipt

A signed, replayable operational accountability artifact.

A portable record of why a consequential decision occurred. Inspect the structure, verify the signature, replay against preserved context, and traverse the operational sequence it belongs to.

  • Signed
  • Replayable
  • Portable
  • Chainable
  • Independently verifiable
Inspect receiptVerify a bundleDownload bundle
Decision Receiptdr_01HZX7K9R8F6Y3TQX4V9B2J1M5
v0.1
Decision
APPROVED
Actor
Fraud Workflow Engine
Policy snapshot
pol_2026_04_uk_retail_v3
Issued
2026-05-06T14:22:11Z
Verified
Signature valid
Anchored
0x9f2a4e0c8b1d2f3e4a5b6c7d8e9f
ReplayablePortableIndependently verifiable
§ 01

Inspect the object

Hover or focus any field on the receipt to inspect its semantics. Verify and Replay sit beneath as operational capabilities — both run locally and reveal real claim outputs, not network theatre.

Decision ReceiptTap a field to inspect
§ 02

Traverse the operational sequence

A single receipt proves one decision. A chain proves a workflow. Hover any step to inspect its receipt and the continuity from the prior step; verify the chain integrity end-to-end.

Inspect this narrative
One narrativeReplayable end-to-end as a single accountable sequence — across people, systems, and AI.
§ 03

The bundle is self-describing

Receipts ship inside verification bundles that carry their own schema, policy snapshot, evidence manifest digest, expected public keys, and canonicalization profile. Replay and verification do not require contacting MeshQu.

bundle_manifest.jsonsha256:7c2a05ee9b1d…91bf
  1. {
  2. "bundle_version": "v1",
  3. "canonicalization_profile": "meshqu-canonical/v0",
  4. "files": [
  5. { "path": "receipt.json", "sha256": "9f2a4e0c…7d8e" },
  6. { "path": "policy_snapshot.json", "sha256": "a3f9c1b2…d8e4" },
  7. { "path": "evidence_manifest.json", "sha256": "e1c4ab90…7af2" },
  8. { "path": "transparency_proof.json", "sha256": "0x9f2a4e0c…" },
  9. { "path": "chain_proof.json", "sha256": "chn_01HZX…" },
  10. { "path": "trusted_keys.json", "sha256": "k1d_2026…q2" }
  11. ]
  12. }
Bundle action

Run the verifier locally against this bundle. No network call.

§ 04

Real operational scenarios

The receipt becomes real through operational context. The same primitive carries different operational shapes — AML escalation, sanctions override, AI-assisted review, procurement approval, agent tool invocation, credit decision, compliance attestation. Switch between scenarios to see how the same envelope adapts.

AML

AML escalation

REVIEW

Velocity-anomaly threshold tripped; escalated to human analyst for context resolution. Receipt records the policy version + evidence references the analyst was given.

ChainStep 03 of 5 · open chain
Actor
Fraud Workflow Engine → Senior analyst
Policy snapshot
pol_2026_04_uk_retail_v3
Evidence references
evd_01HX5N4Q… · evd_01HY3M2T…
Replay
replay.valid
Verification
integrity, signature, snapshot_replay, transparency, chain_link all valid; chain_seal n/a (open chain)
§ 05

Designed to be inspected outside the systems that produced it

Decision Receipts are portable accountability artifacts that can be independently verified outside the systems that produced them. Open schemas, public-key verification, transparency-log compatibility, evidence manifests.

Sits comfortably alongside Sigstore, DSSE, and in-toto style attestations without claiming conformance to any single specification. The shape is the contract; the bundle is the portable witness.

§ 06

Tooling

Inspect, verify, and build against the Decision Receipt object. Verification works offline against the issuer’s public key — the bundle is self-describing and outlives the systems that produced it.

Inspect
Verify
Build