Reach · 08.04
Peer Identity & Connection Grants
Recognizing the same human across Slack and WhatsApp, and the grant model that governs what a connection is allowed to do.
A peer isn't a channel handle — it's a profile with a memory
A peer profile accumulates real, categorized facts about the human or agent on the other end: INSTRUCTION, PREFERENCE, TRAIT, IDENTITY, CONTEXT, and BELIEF — capped at 40 active facts per peer so the profile stays a sharp working picture instead of an ever-growing dump. Each fact carries a volatility class (stable through volatile) and a source — was this observed directly in a session, inferred, confirmed explicitly by the operator, or system-derived — so a system can weigh a directly-confirmed fact more heavily than an inference.
Conclusions, not just facts
Beyond individual facts, the profile can hold conclusions — reasoned inferences typed as deductive, inductive, or abductive, each tracking how many separate sessions support it and whether it's since been superseded by a newer conclusion. This is what lets a peer profile represent "this person seems to prefer terse replies" as an actual reasoned, revisable belief rather than a static tag someone set once.
Continue
A workflow reaches the world with a zero-token channel node — not an agent prompt — that resolves a connection, delivers, and returns a receipt SWIFT can verify.
How an inbound channel message survives a restart and reliably becomes an agent turn — the queue behind 'messages never get lost.'