Skip to main content

Every important decision should leave a receipt.

Your teams spend weeks rebuilding the story of a decision after someone asks. MeshQu keeps the record from the start, so the answer is already there.

Today, decisions are defended from fragments.

Reconstruction takes weeks and produces stories, not evidence.
T+0 · Decision

A workflow approves a $42,140 transfer.

Tuesday, 14:22 UTC. A fraud rule fires, an override is set, the transfer goes through. The system moves on.

+45 days · Challenge

Compliance asks for the override reason.

“Why did this decision pass? What did the system actually see at the time?”

The hunt · 5 days

The team reconstructs from whatever they can find.

None of these were created as proof. All of them depend on memory, access, and time.

  • Logs
  • Emails
  • Slack threads
  • Tickets
  • Screenshots
  • Dashboards
  • CSV exports
  • Wiki pages
The verdict

A story is told, not a record retrieved.

Best reconstruction. Plausible narrative. Not authoritative, not verifiable, not portable. The decision is defended, but never proven.

Execution time · Decision Receipt

The same decision, preserved as a signed receipt at execution time.

One signed object, issued in milliseconds, replayable years later — independent of the systems that produced it.

Decision Receipt018f9a1e-6d4c-7a3b-9f52-0c1d2e3f4a5b
decision
DENY · credit application
policy_snapshot_id
018f9a1e-6d4c-7a3b-9f52-0c1d2e3f4a60
signature_kid
msk_demo_v2 · ed25519Signed at decision time. Verify it against key material you obtain independently.
ReplayablePortableIndependently verifiable

Turn every consequential decision into an asset you can defend.

Challenges become lookups.

A question that once launched a five-day evidence hunt is answered from the record.

Operational examples

Stalled AI projects get an evidence basis.

Internal review blocks automation it cannot defend afterwards. Receipts give every decision the independently verifiable record that review is asking for.

AI governance and execution proof

Decisions outlive their systems.

Vendors change, models retire, people leave. The record still verifies — independent of everything that produced it.

Verify one yourself

The Decision Receipt.

A Decision Receipt is a signed, replayable record of how a consequential decision was made, created at the moment it happens and independently verifiable afterwards. It records the policy in force, relevant decision context, the outcome and the integrity information needed to determine later whether the signed record has changed.
The accountability artifact

A Decision Receipt preserves the record of the decision itself.

  • What happened
  • Why it happened
  • Who or what made it
  • The evidence available

The systems can change. The proof remains.

Decision Receipt018f9a1e-6d4c-7a3b-9f52-0c1d2e3f4a5b
v2
decision
DENY
policy_snapshot_id
018f9a1e-6d4c-7a3b-9f52-0c1d2e3f4a60
timestamp
2026-07-15T09:24:11.000Z
integrity_hash
b20158d4684cd066acffea0cf5def73a6d364814ef074cc51d0909cb894ba8b6
signature_kid
msk_demo_v2 · ed25519
transparency_anchor
null · not anchored
ReplayablePortableIndependently verifiable
Signed fixture · synthetic data · verifiable at /verify

A receipt does not prove that the decision was correct, that its inputs were true, that the outcome was fair, or that it was lawful everywhere. It does not prove that a named human personally acted, or that a model followed the rationale it stated.

Grounded in public evidence.

Accepted to participate in the FCA Digital Sandbox, scoped to fraud and money-laundering detection on synthetic data. Behind it, a published research programme:
283
Records
3,044
Signed receipts
121
Curated bundles

Every figure traceable to a public manifest.