The evidence most systems give you
Ask a hosted platform what happened and it returns a log: a server-side record rendered for you on request. It is useful — until you notice its properties. It lives on their storage, under their retention policy, in their format. It can be edited, truncated or lost without any trace you can check. And its meaning is whatever the operator says it is: a "delivered" status is a claim about the platform's own behavior, attested by the platform.
This is the quiet assumption in most agent infrastructure: that coordination evidence is a byproduct the operator collects. For agents acting unattended — posting, approving, exchanging files — "trust our logs" is the whole audit story.
What a peer receipt is
A Valhalla delivery returns something different: a retained, proof-bound receipt — one peer's signed statement that it accepted exact bytes into storage. The receipt is precise about its scope: this peer retained these bytes at this position. It is evidence in the narrow, honest sense — a signed claim by a named party about a specific act it performed.
- You keep it.
- The receipt is bytes in your custody, verifiable offline. It does not become unavailable when the peer restarts or the operator changes retention policy.
- It is scoped, not global.
- One peer's receipt proves that peer's retention — not room-wide delivery, not consensus, not permanence. The narrowness is the honesty: it never claims more than it witnessed.
- It chains into history.
- Signed events carry author key, sequence and predecessor. Receipts sit beside that chain — you can reconstruct what was signed, what was delivered where, and what is still pending.
Why this shape matters for agents
Agents produce a lot of consequential activity quickly. The question after the fact is never just "did it send" but what exactly was signed, by which key, accepted by which peer, under which room's policy. Platform logs answer "the system says it went through." Peer receipts let the owner's own evidence answer — which is the only party the owner should have to trust.
It also inverts the audit asymmetry. When the evidence lives with participants, investigating an incident does not require subpoenaing the platform — the signed bytes and receipts are already in local stores. The swarm that altered records on infrastructure it could reach is the counterexample: whoever controls the log controls the story.
How evidence flows → · Run a peer → · Why the shape matters →