Reach

In plain words: App: Reach (external channels)

Partial 2 min read 3 glossary terms 22 connected pages
The short version written for the Snayu team

An app that prepares and sends the Assistant's messages in outside places: email (Gmail, Fastmail), chat (Discord, Telegram, WhatsApp), code forges (GitHub) and social posts, plus a public Discord bot profile.

Why read it: Start here before any work on email, chat bots, GitHub comments or social posting integrations.
  1. 1Four provider families share typed requests and exact account and target policy but keep their own protocols and limits.
  2. 2An offline preparation profile builds requests without logging in or sending anything.
  3. 3The public Discord profile answers one mention per turn under a pinned persona; deployment profiles decide where it runs.

Partial Offline preparation and a dev Discord profile exist; no deployable public bot.

Words on this page, decoded click one for its card

In this section 14 pages

Connected preparation Reach: Offline message preparation An offline tool that prepares a ready-to-send request for Gmail, Fastmail, Discord, Telegram, WhatsApp, GitHub or social posts, recording account, target, payload, policy and expiry, without connecting to any provider. open → Email Reach: Email family How Reach represents an email request (sender, recipients, subject, content, reply references) and how Gmail and Fastmail each translate it into their own protocol. open → Gmail connection Reach: Gmail connection A proposed profile for connecting one Gmail or Google Workspace mailbox, choosing what Reach may read, and preparing replies, including Google's registration, consent and verification hurdles. open → Fastmail connection Reach: Fastmail connection How Reach prepares a Fastmail read or send using the JMAP protocol, keeping account, sender identity, draft mailbox and recipient envelope explicit. open → Chat Reach: Chat family How Reach represents a chat message for one exact conversation and how Discord, Telegram and WhatsApp Business each build it with their own identifiers and rules. open → Telegram connection Reach: Telegram connection How Reach prepares a Telegram bot message for an exact numeric chat, and why reading chat history and personal-account access are outside this profile. open → WhatsApp assessment Reach: WhatsApp assessment An assessment of WhatsApp options for Reach: business messaging via Meta's Cloud API, general AI assistant use, and Meta's limited third-party agent platform. open → Forge Reach: Forge family (code hosts) How Reach reads a bounded issue conversation or prepares an issue/PR comment on a code host, kept separate from any permission to change or run code. GitHub is implemented; Radicle is not. open → GitHub connection Reach: GitHub connection A proposed GitHub App profile where a repository owner installs Reach on selected repos so it can read issue/PR conversations and post timeline comments as a bot. open → Social Reach: Social family How Reach prepares an original public text post for a Facebook Page, a LinkedIn member or organization, or an X account, keeping the exact publishing author. open → Social accounts and advertising Reach: Social accounts and advertising An assessment of what account access each social provider (Facebook, LinkedIn, X) requires for posting, and why posting permission never becomes permission to run paid advertising. open → Habitat Reach: Discord server boundary Defines the first public social place: one private Discord server, one channel, and a minimal-permission bot, and how Discord identity is kept separate from local authority. open → Turn Reach: One question-and-answer turn The step-by-step life of one Discord question: authenticate and deduplicate, resolve caller authority, assemble the briefing, commit the answer, then attempt delivery and record whether it arrived. open → Deployment profiles Reach: Deployment profiles Compares three ways to deploy the public Reach bot: all at home, a VPS edge relaying to a home core, or a standalone VPS, and what each means for availability and security. open →
The original text Underlined words open their plain-English card.

Reach prepares correspondence for a selected external place. Its provider families share typed requests and exact account/target policy while retaining different audiences, protocols and operation limits.

Provider families

Family Concrete providers Shared concern
Email Gmail, Fastmail Mail account, sender, recipients, subject and reply references.
Chat Discord, Telegram, WhatsApp Business Exact conversation and optional reply under the selected bot/business account.
Forge GitHub; Radicle remains a future profile. Repository issue/PR correspondence, separate from software-changing authority.
Social Facebook Page, LinkedIn, X Original public post, exact publishing actor and provider-specific payload.

The explicit reach.connect.prepare@1 profile prepares these requests through a native serial GraphStep Map, including finite WUPHF plans. It performs no account authentication or delivery. The families organize contracts and discovery within Reach; they add no separate CompositionApp or provider authority. State of Work keeps the shared evidence boundary.

Public Discord profile

A mention in the Necropolis wakes one bounded turn. Reach admits the event, forms an answer under a pinned Persona, and records whether the external place received it. The platform account remains a way to appear there, without becoming the LichAssistant.

Habitat defines who and what may enter that social place. Turn follows a question through committed answer and delivery. Deployment profiles choose where its durable authority and transport custody live.

For the configurable Discord foundation, start with operator preparation and its implementation boundary. That offline preparation profile selects platform-qualified participants, groups, conversations and permitted requests before an explicit native GraphStep Map. The Discord interface translates its own ids into that shared contract. It does not activate the public Discord contract below or supply a connected bot.

The separate Discord operator profile supplies an explicit development edge, networkless native document-search worker and local reviewed server setup. It preserves the same generic preparation policy, while retaining its own effects, generation and hosting limits.

Under reach.discord revision 1, an allowlisted mention, guild command, or policy-admitted internal event may return ReachTurn@1 and optional ReachDelivery@1. The contract publishes reach.external_converse@1, reach.external_summon@1, and reach.external_presence@1 for those bounded uses.

This public profile excludes cross-place identity/continuity, moderation, ambient surveillance, attachments, DMs, shell, deployment effects, and consent settled by the platform. Avatar may bind presentation, while Reach retains responsibility for the event, audience, turn, delivery, and receipt. A later projection must obtain its own authority; the result of this turn cannot supply it.

Connected work

The connected-work study proposes a successor for Gmail, Discord and GitHub correspondence, plus optional WhatsApp business messaging and a separate owner–agent probe. It includes private accounts, reviewed or preauthorized sends, onboarding and updates while preserving the current public Discord contract.

The account lifecycle and delivery plan retain the proposed operational boundary. Social accounts and advertising distinguishes organic publishing from later paid campaigns.

Composition Portfolio · Workflow