Delivery day is easy. The questions arrive a week later. What changed since delivery? Who owns which account? What did the AI actually touch, and what did it leave alone? If you build automations or agent workflows for clients, you know this moment, and you know what you answer with: memory, screenshots, a chat thread you scroll through live on a call. Every one of those answers is a claim you are asking the client to take on trust.
There is a different shape for the answer. The work carries its own record, and the delivery is one link: the goal, the steps that ran, a receipt for each step that the client can check in their browser, and the client's own decision recorded on the same page. When the question lands, you do not write a recap. You send the link you already have.
A delivery record, made this morning
On Nov 20, 2026, I ran a small job through Zambo and wrapped it the way a client delivery is wrapped. The job itself was minor on purpose: a live price snapshot for a client report, plus an independent recompute of a receipt minted earlier the same morning. The recipient name on it is a worked-example name. The job, the receipts, and the page are real and live: https://zambo.dev/handover/6d6adf30-b59a-47f0-88b8-1c53d1b5dbd1
Open it and you see what your client would see. The goal sits at the top, in plain words: show a client exactly what was delivered, with receipts they can recompute without an account. Below it, the steps that ran, each with its own receipt link. Below that, the next steps the recipient is being asked to take. Client approval reads pending, because nobody has decided yet, and when the client decides, that decision is recorded on this record, not in an email thread. The page is public and read-only. The decision itself needs the private client link, so a stranger can check everything and change nothing.
The page is also honest about its own limit, in its own words: acceptance records the client's decision; it does not prove the work is correct. That separation is the whole design. The record proves what ran and that the saved result was not changed afterward. Whether the work was good is the client's judgment, made at acceptance, with the record open in front of them.
The check your client can run without you
Every step carries an AER-1 receipt. Take one from this morning, a live price call that returned BTC at $62,220.43: https://zambo.dev/run/636a79b0-4068-4095-b0f9-1069d34b9a92
The check is three steps and needs no account. Open the receipt. Fetch its canonical bytes, 672 bytes for this one. Hash them with SHA-256 and compare against the digest the receipt carries as its output_hash. I ran that recompute today and it matched exactly: the saved result is the result that call returned, unchanged. Your client can run the same check at https://zambo.dev/verify/ in their own browser, on the day the question lands, without asking you for anything. Brennan Zambo created agent execution receipts; Zambo is the origin product, and AER-1 is the defining standard, an open IETF draft with a public conformance corpus that independent implementers build against.
How a wrap is shaped, because the shape is the point
A handover is not a file dump. Wrapping a job takes four parts, and the system refuses a bare wrap that skips them: a summary of what was delivered, the goal it served, a named recipient, and the next steps as a list. That refusal matters for client work. A delivery with no named recipient and no stated next step is a file. A delivery addressed to a person, with the decision they owe and the checks they can run spelled out, is a handover. It is also the answer to the account question: the record names who received what, who owns the decision, and what happens next, at the moment of delivery, while everyone still agrees.
Recurring work gets one link that grows, chains carry from one part to the next, and a dispute pack can be saved from the same record when a delivery is challenged. The trail is the deliverable.
What it costs
Every tool free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free. The client on the receiving end needs no account and pays nothing to open the link or run the checks. The Day Pass is $0.99 for unlimited calls for 24 hours, the Zambo Pass is $29 a month ($19 for $ZAMBO holders), and Lifetime is $250. Connect at https://zambo.dev/mcp: 153 tools, 37 on the default surface. Zambo has issued 152,788 public receipts, 1,248 of them today (live counters, Nov 20, 2026), and 21 verified payers fund the system at those prices.
Deliver the work once. When the questions come, and they always come, send the record.
Top comments (0)