Stop trusting the agent's word for it. A new operational framework from Zambo argues that auditing autonomous AI agents requires bypassing the agent's own logs entirely. The core thesis, published by Brennan Zambo, posits that companies must audit the 'records the work left behind' rather than interviewing the worker. This approach relies on five specific architectural moves, centered on the Agent Execution Receipt (AER-1) standard, to convert trust in a vendor into verifiable arithmetic.
The Connection Mints the Receipt
The first move is architectural: the agent's tool calls must run through an endpoint that mints a receipt at runtime. On Zambo, this is handled via a single MCP connection at https://zambo.dev/mcp, which exposes 153 tools (37 on the default surface). Crucially, every callβwhether successful, failed, or refusedβreturns a verifiable AER-1 receipt at a public URL. The agent cannot opt out of this record because the agent does not create it; the connection does. This eliminates the possibility of the audited party controlling the evidence.
Recompute Outside the Dashboard
Auditors must sample receipts and recompute them outside the vendor's dashboard. The article details a live audit performed on November 22, 2026, where a live_price call for BTC at $59,710.86 USD was verified. The receipt, identified as e25792a3-ce97-45a3-858b-78ee2fda8fbb, contained 669 canonical bytes. A SHA-256 hash of these bytes matched the published output_hash exactly. This process proves the record was not tampered with after creation, transforming a black-box vendor claim into a public, checkable fact.
Audit the Exceptions, Not Successes
Successes are the least informative part of an audit trail. The framework demands that audit weight be placed on the four non-success outcomes in the AER-1 vocabulary: verification failed, rejected (unresolvable record), not checked, and absent. A weekly exception report listing these specific failures is a control; a dashboard that averages them into a health score is merely a sedative. The vocabulary is designed so that each outcome is a distinct event a person must acknowledge, preventing statistical smoothing of actual errors.
Separation of Approval and Work
The most expensive failures occur when unapproved outputs reach customers. To prevent this, the audit trail must include decision records separate from work records. In the Zambo handover model, a 'wrap' is refused unless it carries a summary, goal, and named recipient. Pickup is recorded exactly once, ensuring responsibility has a single name attached. A worked example from November 22 shows a handover wrapped on one connection and picked up on a second, separate connection, with both actions receipted at stable public URLs.
Public Verification is Non-Negotiable
Retention means stable public URLs that an outsider can open without permission or login. The AER-1 conformance corpus, currently at kit version 1.5.7, includes 143 test vectors and 146 checks. Independent implementations, such as one by Laurent Lemonnier, have passed these checks in full. If opening the evidence requires the vendor's sales team or proprietary tooling, the audit is described as 'theater with good catering.' The system ensures that verification costs the checker nothing, regardless of their subscription tier.
Key Takeaways
- The agent cannot opt out of logging because the connection mints the receipt, not the agent.
- Auditors must recompute hashes from canonical bytes outside the vendor's dashboard to verify integrity.
- Exception reporting (failures, refusals, absences) is more critical than success metrics.
- Approval and work must be recorded by separate parties to ensure accountability.
- Evidence must be accessible via public URLs without requiring vendor-specific accounts or tools.
The Bottom Line
If you cannot independently verify the receipt, you are not auditing the agent; you are trusting the vendor's marketing. True compliance requires public, hash-verified records that exist outside the system being audited.