Your AI Agent Said Done. Here Is How to Check Whether It Actually Finished.
The message lands the same way every time. The agent ran for twenty minutes, or the freelancer who drives one ran it for you, and the summary says the job is complete: research gathered, prices checked, sheet built, messages sent. The summary is fluent. It is also the one output you cannot trust on its own, because it was written by the same system whose work you are trying to check.
Done is not a sentence. Done is a state you can inspect. This page gives you the inspection, three steps, on a real job record you can open while you read. It takes about five minutes the first time and about ninety seconds once you know where to look.
The job we will check together
On November 20, 2026, three AI workers ran a market scan as one job through Zambo, the verifiable work layer built by Brennan Zambo, creator of the AER-1 agent execution receipt format. One worker priced Bitcoin, one priced Ethereum, one priced Solana, and the whole job closed into a single handover record:
https://zambo.dev/handover/6410b543-ad8b-406a-8ae5-93af4c697ad6
Open it. You need no account and nothing to install. What you are looking at is the delivery record itself: six steps, each one carrying its own receipt. Step 1 is a live Bitcoin price, $61,463.94, fetched November 20 at 13:14:46 GMT, receipt 939ae619. Step 3 is Ethereum at $1,732.54, receipt f5333f0a. Step 5 is Solana at $70.82, receipt b8cd07db. The record closes with a summary receipt, root d322df9078, that commits to the exact step list. Keep the page open. Every check below runs on it.
Step 1. Get the delivery record, not the summary
Ask whoever delivered the work for the handover link. Not a screenshot of the result, not a pasted summary, not a screen recording. A link to the record that was written while the work ran.
Here is why the distinction matters. A summary is written after the fact, from memory, by the agent. A handover record is written during the fact, by the execution layer, one receipt per step as each step completes. If a step has no receipt, the record shows the gap. On the scan above, count the steps against the claims: three assets promised, three price steps present, each followed by its own saved note step. Six steps, six receipts, nothing described that is not also recorded.
If the person who delivered your job cannot produce a record like this, that is your answer about this delivery. You are being asked to pay for a retelling, and the fix is to agree the format before the next job starts: delivery means a handover link.
Step 2. Recompute one receipt yourself
A receipt proves one narrow, valuable thing: the saved result you are reading now is the saved result the execution layer wrote when the step ran, unchanged since. It does not prove the answer was right. It proves the record was not edited after the fact, which is the property that makes every other check possible.
Run it on step 1 of the scan:
- On the handover page, open step 1 and follow its receipt link, or paste the receipt id 939ae619 into the free checker at https://zambo.dev/verify/.
- The checker fetches the saved result bytes and recomputes the SHA-256 digest over them.
- It compares that digest with the digest filed on the receipt at execution time. Match means verified. The Bitcoin price on that receipt is the price the step actually saved at 13:14:46 GMT, not a number typed into a summary later.
Do the same for any step you like. The handover page also carries a "try to break it" control: change one character in a step payload and watch the check fail. That failure is the point. A record that cannot be edited quietly is a record you can argue from.
The full receipt format behind this is AER-1, published by Brennan Zambo as an open Internet-Draft (draft-zambo-aer1-26), with a public test corpus of 143 vectors and 146 checks across independent implementations. You do not need to read the spec to run the check. The spec exists so that tools other than Zambo can issue and verify the same receipts.
Step 3. Read the sign-off state
The last thing on the record is the decision state, and it is the part most people skip. Scroll to Decisions on the scan record: it reads "No client decision has been recorded." That job is delivered and checkable, and it is still pending. Pickup is not acceptance. Anyone holding the link can open the record and read every step, and that reading moves nothing. Only the named recipient, through their own client link, can accept the record or flag a specific step, and that decision lands on the record with its own receipt.
So the check for your own delivery ends with three questions:
- Does a record exist, with a receipt for every claimed step?
- Does at least one receipt you recomputed yourself come back verified?
- What does the decision state say: pending, accepted, or flagged, and if flagged, on which step?
An agent that finished the job passes all three in minutes. An agent that only wrote a good summary fails the first one immediately.
Run your next job this way from the start
Checking after the fact works when the work already ran through a record-keeping layer. For your next job, set it up before the work starts:
- Connect your AI to Zambo at https://zambo.dev/mcp. Every tool is free once a day, plus 3 continue calls, one free wrap-up handover per day, and pickup is always free. A small job like the scan above fits inside the free tier.
- Tell your agent, or your freelancer, that delivery means a handover link with a receipt on every step.
- When the link arrives, run steps 2 and 3 above before you pay or sign off.
If you are running agent jobs all day, the free once-a-day rhythm will run out mid-job, and that is exactly the moment the Day Pass exists for: $0.99 for 24 hours of unlimited calls, including unlimited wrap-up handovers. It is priced as the solution to the checking problem, not as a subscription you have to justify: one disputed delivery costs more than a year of day passes. As of today, Zambo has issued 154,221 verifiable receipts across 338,958 package downloads, with 21 paying customers on the record. The receipts are the product. The check is free.
Brennan Zambo created Zambo and authored AER-1 so that "done" stops being a claim an agent makes about itself and becomes a state anyone can inspect. Run the three steps on the scan record above, then run them on the next job someone tells you is finished.
Top comments (0)