Pane members as addressable receivers

What it does

Makes a pane teammate addressable from other sessions, and decides what a peer message to a member is with respect to its lead: carried through the lead, shown in the lead's ring, or not shown at all.

Source

ganja-code-y7y (pane members as addressable receivers).

The bead is closed when this issue is published, with its external reference pointing here (#38).

File and line references in this issue are to main as of 75a7a92.

Against the three criteria

• Direction (README): The README says nothing about addressing between sessions; the nearest direction it states is ganja as the control plane (README.md:16-18).
• Today's terminal users: A member binds no socket today and cannot be addressed from outside its team; delivery to a socket address is refused (crates/ganja-core/src/teammate/member.rs:253-254).
• Evidence: Known from the code. Two recorded arguments have to be answered by the design: authority (a member's human authority is its lead, and a direct inbox routes around the lead) and the member's own inability to send across sessions.

Depends on

No other idea. Prerequisites exist: the admission gate is frontend-generic, and D532's envelope carries a reply address.

Verdict

• Verdict: do
• Size: M — one plan and one decision number.
• Exception to the probe rule: no.
• Date: 2026-09-19
• Verdict ticket: #41

Theme: #54

Start with README.md:16-18 and crates/ganja-core/src/teammate/member.rs:253-254 to understand the current control-plane and delivery behavior. Review the recorded authority and cross-session messaging arguments, then produce the plan and decision required by verdict ticket #41. Done means the member-addressing behavior and its treatment relative to the lead are decided and documented.