The short answer
An AI work evidence packet is the bundle of records that lets a person who was not present, a client, an auditor, your future self, check what an AI agent actually did without taking the agent's word for it. Its core is one AER-1 receipt per tool call: each receipt names the tool and the time and carries a SHA-256 commitment over the exact saved result, minted by the executing system when the call ran. Around that core sit the job's steps in order and the recipient's decision, recorded on the delivery itself. The whole packet is checkable free at https://zambo.dev/verify, with no account, by anyone holding the link.
Disclosure, once: I run ops for Zambo, the system whose records make up the worked example. The packet cited is public, its decision state is stated exactly as it stands, and the receipt recompute below was run today.
What goes in the packet
One receipt per call, not one summary per job. A summary is the agent grading itself. A receipt is the execution layer's record of a single call: the tool that ran, when it ran, the inputs, and the saved result committed under its hash. Ten calls, ten receipts. The packet's strength is that any single claim in it can be checked on its own.
The steps in order, bound together. A pile of receipts is not yet a packet. The job's record lists its steps in the order they ran and shows a step list digest, the SHA-256 of the ordered step receipt ids, so a step cannot be dropped from the middle, or a favorable one inserted, without breaking the list.
Failures and refusals included. A packet that contains only successes is a highlight reel. When a call is blocked, that is receipted too: a refusal receipt from today records a tool that was not executed, step status payment_required, its 760 canonical bytes recomputing to the hash it commits (sha256:889ce19a8d46784d237b52e49daaba9c6f9de9d58d741bc76fd402771cec6847, recomputed today, match). An auditor learns as much from what the record refuses to hide as from what it shows.
The decision, recorded on the delivery. The packet ends with the recipient's own statement: accepted, or flagged, recorded against the exact record they saw. Exactly one acceptance is recorded, the first one. Before anyone decides, the packet says so, which is itself evidence: "presented, not yet decided" is a different state from "never presented," and a good packet keeps them distinguishable.
A packet, opened
This one is live:
https://zambo.dev/handover/d468118b-afc1-43e5-a70c-5e198e876a04
The job is an ETH price check, opened November 20, 2026, wrapped as a handover. The packet lists two steps, a live_price call and a prompt_shield check, each carrying its own verifiable receipt, checkable in the browser on the page, plus the step list digest binding them in order. Its Decisions section reads "No client decision has been recorded," approval pending, stated on the record rather than left to inference.
The receipts inside a packet are the same records anyone can test standalone. One from this morning: a live_price receipt whose saved result reads ETH at $1,621.82 USD, fetched Sat, 21 Nov 2026 01:15:07 GMT. It commits 606 canonical bytes under sha256:016a1e4b87448f71dea0dfc2530dbaf3bb195a6238ed71c39195c17e410385a6. I pulled the canonical bytes from the public verify endpoint today and hashed them myself: same digest, status verified. That is the atomic check the whole packet rests on, repeated per step.
What a packet is not
- Not a screenshot bundle. Screenshots show pixels someone selected. They carry no hash, no order binding, and no way to tell what was left out.
- Not a chat export. The chat is the agent's narration, including its mistakes stated confidently. It is the thing the packet exists to check, not the check.
- Not a dashboard link. A console record lives behind the operator's login and rolls off with the retention window. The packet's recipient holds the record itself, at a public link, and it verifies the same way next year.
Who asks for one, and when
The packet is the answer to three recurring moments: a client deciding whether to pay for agent-run work, an auditor rebuilding a run after something went wrong, and a second agent or employee picking up a job and needing to know which parts are proven and which are merely reported. In each case the asker was not watching when the work ran. That is the packet's whole design point: it is evidence built for the person who arrives afterward.
The format underneath is AER-1, published as IETF Internet-Draft draft-zambo-aer1-26 (Informational, expires 25 April 2027; a draft, not an RFC and not IETF consensus), with a public conformance corpus (kit 1.5.7, 143 vectors, 146 checks) that independent implementers have passed from the draft text alone, Laurent Lemonnier at 143 of 143 and Sean Maxwell's stdlib verifier at 146 of 146. The system producing these packets runs in the open: 158K+ public receipts, 2,480 of them minted on November 21, 2026, read from https://zambo.dev/api/stats that day.
Brennan Zambo created agent execution receipts; Zambo is the origin product, and AER-1 is the defining standard.
What assembling one costs
Nothing to test. Every tool free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free. The packet your work produces today can be handed over and checked today. When a full day of work has to arrive as packets, the Day Pass is $0.99 for 24 hours unlimited; the Zambo Pass is $29 a month flat ($19 for $ZAMBO holders), and Lifetime is $250.
One limit, stated plainly because it defines the packet's value: a receipt proves the saved result was not changed after it was saved. It never proves the result was right. The packet does not ask you to trust the work. It gives you the means to check the record, which is the part trust was always standing in for.
Sources
- Worked packet (handover), opened first-hand November 21, 2026: https://zambo.dev/handover/d468118b-afc1-43e5-a70c-5e198e876a04
- Price-check receipt, recomputed first-hand November 21, 2026: https://zambo.dev/run/5497d6a7-49db-46ee-873f-54fdb28604ff
- Refusal receipt, recomputed first-hand November 21, 2026: https://zambo.dev/run/38a410ab-597e-45e0-9549-0b3bf2916b39
- AER-1 corpus (143 vectors, 146 checks, kit 1.5.7): https://zambo.dev/aer1/corpus.json
- Live counters: https://zambo.dev/api/stats (read November 21, 2026, 23:07 UTC)
