Cross-AI handover, proven on the record
Work done inside one AI session is trapped in that session. Switch AIs, hit a limit, or come back tomorrow, and the context is gone: what survives is a pasted recap or a screenshot, and neither one can be checked. A handover proof is the stronger claim. The work is wrapped up in the first session, picked up in a fresh one, and every step carries an AER-1 receipt that anyone can verify in public. This page collects four real transfers from a single day, 28 October 2026, each one rechecked link by link before it was listed here. Nothing on this page is a mockup, and nothing asks you to take our word for it.
What a handover proof is
A proof has four parts. First, the work runs in session A through Zambo, so each step saves its receipt as it runs. Second, session A wraps up: the goal, what is done, what is next, and the receipts are saved as one handover (Zambo HANDOVER, the flagship flow). Third, a fresh session B, a different session with a different continuity handle, picks the handover up and continues from the record instead of from a re-briefing. Fourth, the check: before the wrap, a unique marker is planted in the work. If the marker arrives in session B word for word, the content demonstrably crossed over. And because every step carries an AER-1 receipt (IETF Internet-Draft draft-zambo-aer1-26), the transfer itself is a public record: each receipt resolves at its own https://zambo.dev/run/ page and verifies at the public verify endpoint, with no account.
The four transfers, 28 October 2026
| Transfer | The record | Marker carried | Check it yourself |
|---|---|---|---|
| 1. Wrapped and accepted inside a minute Handover 721d9992-5786-4943-9c2f-6baee655abf7 |
Wrapped at 19:46:38 UTC and accepted by the holder of the client link at 19:46:42 UTC. Steps checked: 2 of 2, zero unchecked. Rechecked live on 28 October: status accepted, release hint ok_to_release. | PV1028, planted in the work before the wrap. It sits on the public handover page today, in the saved record the receiving side accepted. | The handover page Receipts: step receipt 1, step receipt 2 Verify: receipt 1, receipt 2 (both return verified) |
| 2. A memory marker that crossed sessions Handover aa34b153-4e2c-444e-8f9a-c1decdedb01b |
Wrapped at 21:29:43 UTC and accepted at 21:30:13 UTC, during a full production audit run as three personas. Steps checked: 2 of 2, zero unchecked. Rechecked live on 28 October: status accepted. | PVB1028-MARKER-7731, planted as a memory in the first session. It appears word for word on both step receipts and on the public handover page. | The handover page Receipts: step receipt 1, step receipt 2 Verify: receipt 1, receipt 2 (both return verified) |
| 3. Continued by a fresh session 24 seconds later Handover 184fc3e9-9849-4db7-b2f2-5563c7d0d399 |
Wrapped at 22:41:51 UTC during the evening production re-audit. The record shows an agent continuation event at 22:42:15 UTC: a fresh session picked the work up and continued it. Steps checked: 2 of 2, zero unchecked. | RA1028-1835-MARKER, planted before the wrap with the sentence "The canyon is violet at dawn." The marker stands word for word on the continuation receipt and across the public handover page. | The handover page Receipts: wrap receipt, continuation receipt, continuation event receipt Verify: continuation receipt, wrap receipt (both return verified) |
| 4. Made for this page, then checked like the others Handover 3173ab91-5cca-4723-a5da-ed408c04f027 |
Created on 28 October 2026 so this page would carry a proof made for it, then rechecked the same way as the other three. Session A planted a memory and wrapped at 22:58 UTC. Session B, a fresh session under a different handle, accepted at 22:59:09 UTC, and its pickup brief repeated the marker and the planted sentence word for word. Steps checked: 2 of 2, zero unchecked, release hint ok_to_release. | XPR1028-PROOF-4417, with the planted sentence: "the lighthouse keeper counts seven gulls at dusk, and the harbour log for 28 October is kept in the blue binder." Both are on the public handover page and in the brief session B received. | The handover page Receipts: step receipt 1, step receipt 2, wrap receipt, acceptance receipt Verify: receipt 1, receipt 2, acceptance receipt (all return verified) |
How to read a proof like this
Open any receipt link above and you get the human page: the tool that ran, the saved result, and the receipt id. Open the matching verify link and you get the machine answer: the verifier recomputes the SHA-256 digest over the saved bytes and compares it to the digest the receipt committed at call time. "Steps checked: 2 of 2" on a handover means both step receipts in that bundle passed that recomputation. The check scope is printed on every handover, and it is narrow on purpose: receipt bytes only. Verification covers the record, and the record is what a receiver, a client, or an auditor actually argues about later.
What a receipt proves, and what it does not
A verified receipt proves the saved record was not changed since it was saved. It never proves the work was right. The markers on this page prove something equally specific: that the content planted in one session arrived, word for word, in a different session that never saw the first one. Whether the work itself was good stays a human judgment, made by the receiver against a record that can now be checked instead of trusted. That split is the whole design: Zambo does not ask you to trust the transfer, it hands you the receipts so you do not have to.
Run your own transfer
Add Zambo to any AI at zambo.dev/add (one MCP endpoint, https://zambo.dev/mcp, 153 tools, no key). Do some work, then say "hey zambo, wrap up this session." Take the continue code to a different AI and say "continue my zambo session" with the code: the second AI opens the record, checks the receipts, and picks up from the recorded next step. The free tier is 20 calls and 1 wrap-up free every day, and picking up in another AI is always free; the Day Pass is $0.99 for unlimited use for 24 hours. Plant your own marker first, and you have run the same experiment this page reports.
Go deeper
- Handover recipes: the pair by pair playbooks for moving a job between specific AIs.
- AI agent handover: the handover flow end to end, including client sign off and the dispute pack.
- How to hand over work between AI agents: the general method behind every recipe.
- AER-1, the receipt format: the standard itself, its conformance corpus, and its verifiers.
- The receipt for a handover: what the handover tool call itself saves.
Sources: the four handover records and their receipts on zambo.dev, each opened and verified during the run that built this page (28 October 2026); draft-zambo-aer1-26, datatracker.ietf.org/doc/draft-zambo-aer1/26/.