s2slisted

# s2s — the channel between two running sessions The decision, its rejected alternatives, and what this design costs: [ADR-0162](../../docs/adr/0162-the-session-to-session-channel-has-an-owner.md). Where the bound lives and why it warns: DEC-0106, DEC-0107. ## The stance **A send reports on the send.** That sentence is the whole skill, and it is not a caution — it is a measurement. `MISTAKES.md` M-0125: a monitor brief named cross-session `SendMessage` to its coordinator as its only reporting path. Every send is held for the recipient user's approval. Two expired undelivered. Each returned `success:true`. The role produced correct findings and delivered none of them, and nothing anywhere said so. So the channel is real and the channel is not a delivery guarantee, and a session that treats it as one loses its work silently. Three things follow, and they are the three this skill owns: 1. **The deliverable is a durable path.** Something committed and pushed, that the reader can pull whether or not any message arrives. The message is a **pointer** to it, plus an ask. 2. **A delegated session's terminal is a log, not a report.** Nobody is sitting in front of it. It is read, if at all, through `claude logs` — a channel measured at ten escape sequences per hundred bytes, redrawn by cursor moves, whose word spacing does not survive the transport. Writing a long report there is writing to a lossy channel with no reader. 3. **Those are different audiences with differe