KAN › The bus

The bus: how squad mail travels

A squad runs on messages: a READY, a question, a claim, a ruling. The bus is how they are written, delivered, found again and answered, and how a message stays a record instead of a line in a log.

Teaches from specs/kan/design/squad-bus.md, kan/mcp/README.md and specs/kan/design/transport.md.

Record first, transport second

The design starts from what went wrong before it: the interview “found that delivery works and the record does not. This design is therefore record first and transport second.” So every squad message is a KAN record before it is anything else: “Every squad message is first a KAN record, attributed to the sender's own principal”, and “The bus carries copies derived from KAN, never the original.”

Lessons

1. The stream and the inbox: where one send goes, and why a seat needs both.
2. The eight record kinds: what each one carries and what KAN checks.
3. Through the kan MCP tools: the MCP-only rule, and the reads a session opens with.
4. Watching between turns: the watcher, and MCP's own wait inside a turn.
5. Forwarding across Macs: one squad KAN, and a peer's mail ingested into this one.

Previous: The board · Next: The stream and the inbox · Up: KAN

Teaches ecd/kan at 0aebfbcb, 25 October 2026.