- Question
- When work passes between agents — or between two copies of one agent — whose memory is authoritative, and what does a handoff survive?
- Where it stands today
- An opt-in mesh transport with signed messages, peer authority limits, and quarantine, plus an attribution model that ties a memory to an agent, a delegation, and a task rather than to whichever process happened to write it. The direction this points at is governed fleet memory: shared memory across a team of agents where each entry carries its author, its delegation, and its revocation state, and a handoff can be checked against a signed receipt.
- Evidence
- Observed the receipt format that would carry a handoff's evidence is public —
continuity-receipt, with a standalone verifier and conformance vectors. No multi-agent result has been published against it. Protocol and internal plumbing are not the same thing as a result, and this card will say so until that changes. - Open problem
- Identity that holds across models and hosts; resolving two agents that remember the same event differently; what happens when copies diverge and meet again; who may write to shared memory under whose delegation, and how a revocation reaches the other nodes.
- Code & entry points
- Reachable only behind an explicit experimental flag; off by default.