Reach · 08.01
Connections: How Agents Reach People & Systems
The Connection primitive: peer identity resolved across channels, durable inbound queues, and rich two-way attachments.
The reach primitive, plainly
Connection is the primitive answering one question: how does an agent reach a person, a system, or another agent? Every channel, integration, and protocol surface in this category is a Connection — Slack, WhatsApp, email, an MCP server, an A2A skill, a webhook. What they share is durable inbound queuing (a message a channel delivers isn't lost if Agentis restarts mid-processing) and peer identity that follows a person across channels rather than treating "the same human on Slack and WhatsApp" as two unrelated strangers.
Continue
An App runs several workflows as one pipeline. The App Orchestrator executes dependsOn chains and run-all — and 'order' is a display sort, not a dependency.
Discord, Slack, Telegram, WhatsApp, and Voice — direction, threading, attachments, and the quirks of each.