Topics · Domain workflow
Risk and compliance teams can check the signed action and authority context without relying on a vendor summary after the damage is done.
Concrete scenario
A trading agent executes a swap at 02:14 while risk limits differ from the daytime profile. PnL is wrong by morning. The vendor insists the action was policy-compliant, but the exported log omits the authority scope and tool-call preimage active at execution.
Problem
Agents combine tool calls, delegated authority, and policy gates at machine speed. When something goes wrong, a dashboard summary is not enough. The action needs its own proof.
Mechanism
Each accountable tool call or bounded action can mint a receipt recording action type, policy context, delegated authority material, and routing profiles at execution time — signed bytes that survive outside the agent SaaS console and retention windows.
Verifiable outcome
Scope boundary
Receipts capture signed agent actions — not model safety in unconstrained environments, completeness of every latent chain-of-thought step, or vendor model behavior absent instrumentation.
Spec authority