Clear boundaries.

Source-inspected communication inventory. Example route shapes only: no secrets, live payloads or personal records. Current local/device authentication is not an internet deployment approval.

Device and dashboard API

Route	Data	Permission
`GET /api/inbox`	Recording names, queue states, processing status	read recordings
`GET /api/transcript/{sha256}`	Transcript text, segments, duration and model metadata	read transcripts
`PUT /api/audio/{sha256}`	Audio bytes; base64 recording name; SHA-256	upload recording
`GET /api/context`	Workouts, calendar/activity locations, people context and document links	read private context
`PUT /api/captures/{uuid}`	Versioned workout sessions, notes, activity completion and order	store capture
`GET /api/assistant`	Configured routes, command messages, replies and delivery status	read commands
`PUT /api/assistant/{uuid}`	Text, timestamp; explicit targets or workflow ID + revision	queue explicit command
`GET /api/decisions`	Review cards, obligations and availability state	read decisions
`PUT /api/decisions/{uuid}`	Action, reviewed revision and action-specific approval fields	decide exact action
`PUT /api/decisions/busy`	Availability action payload	change availability
`GET /api/update`	Release version, hash, size and availability	read release
`GET /api/update/{sha256}`	Signed Android APK	download release
`PUT /api/diagnostics/{uuid}`	Version, timestamp, health counters, event codes; optional user-entered problem note	submit diagnostics
`GET /api/dashboard`	Service status, recent runs, email subjects, decisions and usage	local dashboard read
`GET /api/trace?id={trace}&after={sequence}`	Redacted ordered audit payloads; 200-entry pages	local trace read

Communication boundaries

Android → Sheath

TLS with certificate pin + hostname validation

Routes listed above; large audio/APK traffic requires Wi-Fi

Remaining boundary: Shared embedded credential; device enrollment/revocation/scoped tokens still required before additional installs

Local browser → Sheath dashboard / inbox

Loopback HTTP 8769 / 8766 with Host allowlist + token for APIs

Dashboard/trace; legacy inbox also exposes GET context/inbox/transcript

Remaining boundary: Not internet-ready; remote gateway and session authorization pending

Sheath email workers → Outlook Graph / Gmail API

Provider HTTPS + PC-owned OAuth credentials

Selected message/thread content, draft creation and separately approved sends

Remaining boundary: Scope review and credential provisioning needed on each new host

Sheath inference adapter → Authenticated Codex CLI / configured provider

Local subprocess; provider communication via CLI

Scoped thread/evidence, voice instructions, schema and draft candidate

Remaining boundary: Only current CLI adapter implemented; local inference and cloud egress policy adapter needed

Android navigation / resource tap → Selected map app / HTTPS resource

Explicit user action through Android intents

Destination/address or resource link

Remaining boundary: Physical mapping and third-party permissions remain separate from synthetic tests

Remote browser → Vercel portal → proposed Access gateway → PC

Planned HTTPS with owner session and outbound tunnel

Public marketing; private dashboard only behind gateway

Remaining boundary: Not deployed/validated; no shared PC credential in public JavaScript

Future PC2 / agents → Sheath queues and inference hosts

Planned authenticated encrypted worker connections

Scoped job context, results and receipts

Remaining boundary: Temporal/PostgreSQL and per-worker identity not implemented

Back to validation