Home-only

In plain words: Reach deployment: Home-only

Designed 2 min read 8 glossary terms 4 connected pages
The short version written for the Snayu team

The home-only Reach profile: every service, record and credential stays on one home machine with outbound-only connections, so Reach is unavailable whenever home is down.

Why read it: Read this if you are planning a single-host Reach deployment.
  1. 1No VPS, tunnel, public listener or inbound callbacks; all connections are outbound.
  2. 2Discord edge holds the bot token only; other services split credentials by job.
  3. 3After a reboot, only events Discord still supplies can be recovered.

Designed Page states: designed, not deployable.

Words on this page, decoded click one for its card

The original text Underlined words open their plain-English card.

Reach sleeps when home sleeps. reach.home.public@1 keeps its WardSecurity Desk, VesselEngine Room, Workers, corpus, effect ledger, and PhylacteryMemory Vault in one home-local ApplicationDeploymentManifest@1, with no VPS, Tether, Veil, public listener, callback, or inbound A2AAgent-to-Agent Line road.

This profile is Designed, not deployable. State of Work records Reach’s delivery boundary.

The profile admits public corpus/ContextBriefing Pack and guest effects. Its separated services narrow parser and credential compromise, but do not isolate the body from home-account or VesselEngine Room compromise, which may expose private home truth and resident credentials.

Services and roads

The Discord edge holds the bot token and Gateway/event/delivery observations. It has no provider credentials, corpus writer, database secret, policy, or ambient SigilID Badge. Core/WardSecurity Desk/Workers own admissions, task SigilsID Badges, RunsJob Records, turns, and policy, but receive no bot/provider bearers, non-local listeners, or host control.

Fetching evidence and making remote attempts also have separate owners. The corpus refresher holds allowlisted HTTPS access and staging custody; the PortalCloud Model/A2AAgent-to-Agent Line gate holds only the credentials and attempts for its exact destination. PhylacteryMemory Vault owns canonical Core/Reach records and has neither a non-local listener nor a replica.

Gateway WSS and Discord REST, source HTTPS, and exact provider/A2AAgent-to-Agent Line HTTPS are outbound. Authenticated typed local ports connect services; other ingress is closed. The standalone E2E contract supplies the same corpus, fresh egress, quarantine, turn, nonce, and known/unknown delivery law. Every canonical record commits at home.

Failure and recovery

After reboot, use RunJob Record/outbox truth to resume safe pre-submit work and reconcile uncertain provider/Discord effects. Reconnecting recovers only the events Discord still supplies, so older missed events have no promised recovery. While power or Internet access is lost, Reach performs no cognition, provider/A2AAgent-to-Agent Line work, or delivery.

Home compromise closes admission, revokes bot/provider/A2AAgent-to-Agent Line/database/service credentials, and reconciles external identities. Recovery follows the clean-rebuild contract: rebuild a trusted body, restore only independently verified non-secret records from an admitted backup, and reenroll from zero authority before activating a fresh epoch. An off-host backup cannot operate as a second PhylacteryMemory Vault.

Acceptance

Qualification must follow a public turn across two boots and prove dedupe, corpus citations, and per-attempt egress. It must also exercise uncertain provider/A2AAgent-to-Agent Line and Discord effects, service-secret/network isolation, zero non-local listeners, and restore. Private ContextBriefing Pack, consequential effects, callbacks, inbound peers, and simultaneous epochs must all refuse.

Deployment matrix · Reach turn