AI agent finished while I was away: how do I know it really did the work?
You left an agent running and went to do something else. That is the entire point of an agent. When you come back, it says done, and it hands you a tidy summary.
A summary is a claim. It is written by the same system whose work you are trying to check, so reading it twice does not verify anything. The walk away test is different: ignore the summary, open the job's receipts, and recompute one of them yourself. It takes minutes, it needs no special access, and below I run it on a real receipt from this morning so you can copy the exact steps.
Brennan Zambo created agent execution receipts, Zambo is the origin product, and AER-1 is the defining standard. Every job run through Zambo produces a receipt recording each step, and the receipt carries the bytes needed to check it without trusting Zambo, the agent, or this article.
The check, run on a real receipt from today
On November 18, 2026, I pulled the public recent receipts feed at https://zambo.dev/api/receipts/recent?limit=5 and took the first entry:
- Receipt id: 36d6a575-241f-4a80-a7a5-4ea2df5dd086
- Tool: zambo_universal
- Created: 2026-11-18T09:32:41.512Z
- Job summary on the receipt: "need: Hello, what can you do?"
- Steps recorded on the receipt: live_price, started and completed at 2026-11-18T09:32:26.726Z; qr_generate, started and completed at 2026-11-18T09:32:26.726Z; market_pulse, started at 2026-11-18T09:32:26.726Z and completed at 2026-11-18T09:32:29.648Z.
- output_hash: sha256:ccaf416f4f5019067f63d323e9d2a0e3e9ebd130b0c246b3db4f11d048decae7
- Canonical byte length: 12,862 bytes
- Verification status on the record: commitment_matches
Then I fetched the full receipt JSON at https://zambo.dev/api/receipts/36d6a575-241f-4a80-a7a5-4ea2df5dd086 and recomputed the hash myself. The receipt's canonical_bytes field is base64 encoded. Decode it, hash the decoded bytes with SHA-256, and compare against output_hash:
import requests, base64, hashlib r = requests.get("https://zambo.dev/api/receipts/36d6a575-241f-4a80-a7a5-4ea2df5dd086").json() decoded = base64.b64decode(r["canonical_bytes"]) computed = "sha256:" + hashlib.sha256(decoded).hexdigest() print(computed) print(computed == r["output_hash"]) My computed digest: sha256:ccaf416f4f5019067f63d323e9d2a0e3e9ebd130b0c246b3db4f11d048decae7. It matches the output_hash on the receipt exactly, and the script prints True. That match means the saved result I fetched is byte for byte the result the job produced. If even one byte had been edited after the fact, the digest would differ and the check would fail.
That is all a verifiable receipt proves, and it is worth being precise about it: it proves the saved result was not changed. It does not prove the result was right. Correctness is still your job to judge, with the receipts showing you exactly which steps ran, with what, and when, so the judging is fast.
The three failure shapes a summary hides
- A step that never ran. The summary says the research was done, the prices were checked, the file was written. If a step never ran, it is not recorded on any receipt. Read the receipt list against the work you asked for. A step missing from the record is the loudest signal in the system, because a step cannot quietly exist without being recorded on a receipt.
- A result changed after the fact. Someone, or some later process, edits the output to look better, fix an error silently, or swap a number. The recompute above catches this every time: the bytes no longer hash to the output_hash recorded when the job ran, and verification reports a mismatch on the hosted record instead of a match. In AER-1 terms the evaluated outcome is verification failed, and you treat the job as not delivered until it is rerun.
- Work done outside the job you wrapped. An agent does part of the work in side calls, outside the job, then wraps the job and presents the side results as part of the delivery. A Zambo wrap holds only receipts from its own job. Receipts from side calls are refused by the wrap as not job owned, so the handover you receive cannot silently absorb work that happened elsewhere. If it is not in the job, it is not in the proof.
Run those three checks on any finished while you were away job: every claimed step is recorded on a receipt, one recomputed receipt matches, and the wrapped record contains only job owned receipts. A job that passes all three earned its done. A job that fails any one of them gets sent back, with the failing check named, instead of a vague feeling that something looks off.
Doing this on your own work
The free tier is enough to run the test on a real job today: every tool is free once a day, plus 3 continue calls shared across tools, one free wrap up handover per day, and pickup is always free. Start at https://zambo.dev. For heavier use, the Day Pass is $0.99 for unlimited use for 24 hours at https://zambo.dev/day-pass/, the Zambo Pass is $29 for 30 days, or $19 for 30 days for $ZAMBO holders, and the Lifetime Pass is $250. There is no annual tier.
So the next time an agent finishes while you are away, skip the summary. Open the receipts, read the steps and their timestamps, recompute one hash, and check the wrap only holds its own job. Minutes of arithmetic beat hours of wondering whether done means done.

