ANCHORED ACTION RECEIPTS
A signed, anchored receipt for every autonomous action an agent takes on a user's behalf. One canonical wire type records the verb that ran, the rule and recipe that authorised it, the outcome, and cryptographic commitments to the decision, parameters, and request that drove it — the proof a regulated business needs to let an agent act unsupervised.
WIRE TYPES
ar.action.v1 (executed)
Records an automation verb that ran to completion — the verb (e.g. invoiceup.remind), the owner-assigned rule_id and recipe_id that triggered it, the UTC execution time, and HMAC-salted SHA-256 commitments to the decision, params, and request_id inputs. Receipts chain by prev for a full action history.
ar.action.v1 (failed-gave-up)
Records an automation verb that exhausted all retries without completing. The same commitments are anchored — an agent that tried and stopped is as accountable as one that succeeded.
WHAT IT PROVES
WHAT IT DOESN'T PROVE
COMPOSES WITH
AActR receipts reference other family members via body-level composition pointers — verifier-coordinated, not signature-mandated.
An action's lawful basis traces to the APuR purpose binding the agent was operating under.
AActR receipts reference the ADR grant that delegated the authority the agent acted within — the scope the action must stay inside.
An agent action that deletes data emits an ARR erasure receipt alongside the AActR — what happened and what it changed, both anchored.
Verify any
AActR receipt.
Paste any claim ID to verify a receipt, check its anchor, and inspect the issuer signature.
See a live AActR receipt verify →REFERENCES
Anchored Action Receipts are cryptographic provenance and privacy-lifecycle protocols. verify.dekimu.com is a reference implementation, not a qualified trust service under Regulation (EU) No 910/2014 (eIDAS) or successor.