agentreceipt.org

Audit, Compliance & Compute Verification

Agent Receipt

Auditable provenance system recording every agent transaction, tool call, and decision in a cryptographically secured ledger.

Three Pillars

Why This Becomes Necessary

Human overseers cannot identify root causes of agent failures or systemic cascades without tamper-proof, structured records of the exact parameters and transfers executed at each decision point.

What a Solution Must Provide

Append-only ledger storage, cryptographic signing of each record, structured schemas capturing prompts, tool calls, and environmental states, retention policies, and query interfaces enabling efficient forensic zoom-in.

Regulatory & Standards Angle

DORA Article 12 mandates backup and recovery procedures for critical ICT systems; an append-only agent receipt ledger that survives outages and supports forensic reconstruction satisfies DORA's operational resilience and audit trail requirements.

Related Primitives

Cross-Cluster Context

Relevant: DORA Article 12 - DORA Article 12 requires financial entities to maintain backup and recovery capabilities; cryptographically secured agent receipt ledgers directly support the audit, recovery, and incident-reporting obligations it imposes. Source
Research: Distributional AGI Safety — Tomasev, Franklin, Jacobs, Krier, Osindero
“Actions and decisions taken by AI agents ought to have auditable provenance, including the key decision parameters. This provenance should be structured to allow for attribution, enabling overseers to trace a specific harmful outcome back through a complex chain of agent interactions to its root decision... This could be achieved by recording transaction and decision logs in a cryptographically secured, append-only ledger...”
Read paper →