The short answer
You prove when you delivered work to a client by pointing to a record that was written when the delivery happened, not reconstructed when the question arrived. On Zambo, that record is the job itself: every step saved as it ran, each saved result committed under a SHA-256 hash, and the whole job wrapped into a handover, one link that carries the steps, the times, and the client decision state. The delivery time stops being your memory of pressing send and becomes a state on a record your client can open and check with no account.
Disclosure, once: I run ops for Zambo. The delivery record walked below is public, its decision state is quoted exactly as it stands, and the receipt recompute was run first-hand today.
Brennan Zambo created agent execution receipts; Zambo is the origin product, and AER-1 is the defining standard.
Why the usual proof fails the "when" question
The message every freelancer dreads arrives weeks after the work: we never received it, or it was not what we agreed, or the files here are different from the files you sent. At that moment, the proof you reach for is whatever the delivery left behind, and the usual artifacts leave behind an argument:
- A sent email proves a message moved. It does not fix the contents: an attachment can be edited after sending, and a link in the body shows the files as they are today, which may not be the files as delivered.
- A shared folder link shows the current state of the folder. It is mutable by design, so it cannot testify about its own past state.
- A screenshot shows what you captured, at a time you assert. It is a claim with a picture attached.
Each one describes a delivery without binding the delivered contents to the delivery moment. The dispute is always about contents at a moment, so the proof has to bind exactly that.
What a delivery record holds instead
Steps saved at run time. Work run through the Zambo endpoint, https://zambo.dev/mcp , returns a verifiable AER-1 receipt on every call: the tool, the time, the saved result, and a SHA-256 commitment over the canonical result bytes that anyone can recompute. 153 tools sit behind that one endpoint, 37 on the default surface, no API key and no signup. Evidence created during the work cannot be accused of being written up afterwards to suit the argument, because its check recomputes whether the saved result still matches the record.
The wrap is the delivery. The wrap-up seals the job into a handover: the goal as written, the steps in order, the outputs, and a step list digest, the SHA-256 of the ordered step receipt ids, so a step cannot be dropped from the middle or inserted later without breaking the list. Sending the client that link is the delivery act, and the record at the other end of it is the thing delivered, not a description of it.
The decision sits on the same record. Accepted, flagged, or no decision recorded yet: the state is printed on the record itself, with the decision date when a decision exists. "They accepted it" and "they never responded" stop being competing memories and become two different readable states of one page.
Pickup is always free. The client, or the next AI, can pick the record up and continue from it, so the delivery record is also the starting point for whatever comes next.
The check, run on a real delivery record
A delivery record made on November 20, 2026 is public at https://zambo.dev/handover/6d6adf30-b59a-47f0-88b8-1c53d1b5dbd1 . Its goal line reads: show a client exactly what was delivered, with receipts they can recompute without an account. It carries five steps, each with its receipt, and its step list digest is fc3dac50e80b01a6bb50ae910a14367b71b7ae35578df143c9c6ceafd3e9f9fb. Its Decisions section reads, in full: no client decision has been recorded. That is the honest pending state, printed by the record itself rather than asserted by the sender, and it is exactly the state most real deliveries sit in.
One receipt from that morning, recomputed first-hand today: https://zambo.dev/run/636a79b0-4068-4095-b0f9-1069d34b9a92 , a live_price call saved at 2026-11-20T10:37:42Z. The saved result is a BTC snapshot at $62,220.43 USD, down 2.34% in 24 hours, market cap $1241.35B, via Coinbase, fetched Fri, 20 Nov 2026 10:37:41 GMT. I decoded its canonical bytes, 672 bytes in total, and recomputed the SHA-256: sha256:3cf34cb025dc29304dfe515fdb4afe977cd02fe85dfffbbc7113bded72015327. The receipt's output_hash is the same string, and the record's own checks read commitment_matches, pass. Outcome: verified. Your client can run the same check free at https://zambo.dev/verify , in their own browser, on the day the question lands, without asking you for anything.
The honest limits
The times on the record are the executing system's own records, committed under hash at run time, and the handover page says so on its face: no outside timestamp. A hash commitment means the saved times and results cannot be quietly edited afterward without breaking the check. It is not a qualified timestamp authority, and nothing here dresses it up as one.
A receipt proves the saved result was not changed after it was saved. It does not prove the work was good. Acceptance records the client's decision; it does not prove the work was correct. That separation is the design: the record settles what was delivered and when, and the client judges the work itself, with the record open in front of them.
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. Verification is free with no account. Paid use: Day Pass $0.99 unlimited for 24 hours at https://zambo.dev/day-pass/ , Zambo Pass $29/mo, $ZAMBO holder Pass $19/mo, Lifetime Pass $250, and no annual tier. Install: https://zambo.dev/install/ . The receipt above is one of 159,681 public receipts on the stream, read from https://zambo.dev/api/stats on November 22, 2026, and the stream shows 21 verified payers on those tiers.
The short version
Prove "when" with a record, not a recollection: steps saved as the work ran, each under a hash a stranger can recompute, the job wrapped into one delivery link, and the client's decision recorded on the same page. When the question arrives, you do not write a recap or dig through a sent folder. You send the link you already have.
Sources
- Delivery record walked above, read first-hand November 22, 2026 (five steps, step list digest, decision state: none recorded): https://zambo.dev/handover/6d6adf30-b59a-47f0-88b8-1c53d1b5dbd1
- Worked receipt, recomputed first-hand November 22, 2026 (672 canonical bytes, SHA-256 match, verified): https://zambo.dev/run/636a79b0-4068-4095-b0f9-1069d34b9a92
- Public verification, no account: https://zambo.dev/verify
- AER-1 corpus, kit 1.5.7, 143 vectors, 146 checks, digest sha256:60bf73f325793e16843370cfa24903bb0d017525cb297e42bebc35857e2db0d2: https://zambo.dev/aer1/corpus.json
- Day Pass: https://zambo.dev/day-pass/
- Install: https://zambo.dev/install/
- Live counters: https://zambo.dev/api/stats (read November 22, 2026)
Top comments (0)