Principal
The identity behind one or more endpoints. An endpoint that resolves to no principal is rejected at the bridge, and that rejection is the entire access-control mechanism for channels: there is no separate allowlist.
Linking one person's Telegram and Discord endpoints to a single principal grants both endpoints access; on its own it does not continue a conversation across them. Routing reads the binding at the arriving endpoint's own address and never searches by principal, so the second endpoint starts its own conversation until its binding is pointed at the first conversation's id.
For a group chat the linked principal stands for the room rather than for a person, since the room is one endpoint. That imprecision is recorded, with its consequences, in Multi-Channel Agent Routing.
Distinct from the command principal, which authorizes command execution at a different layer.
