Public
Family portal
Open pages explain the why: family-owned services, AI companions, privacy-first routing, and Sasha's public Reiki presence.
Open service catalog →Access tiers
Three doors. Different trust. Different power.
The public website can describe the shape of the system without revealing topology, raw hosts, ports, action internals, callback details, audit locations, or operational commands.
Public portalHome, Services, Hermes, Reiki, and Operations tell the safe family-facing story.
→
Protected observabilityRead-only dashboard, memory, metrics, and status views require authentication and fail closed.
→
Approved-device operationsControlled request cards and allowlisted actions stay behind private device membership and human approval.
Authenticated
Read-only observability
Dashboard, Memory Workflow, Metrics, and protected feeds are visible only after login. They are for inspection, not browser-side control.
Open Agentic OS →Approved devices
Controlled command plane
Command Center is not public and not an unrestricted terminal. It prepares bounded requests, keeps an audit trail, and requires approval for meaningful power.
Private surfaces
What the locked layers do.
These names are public-safe. The mechanics stay private: no raw routes, no device addresses, no command IDs, no request locations, no backend implementation details.
Agentic OS
Morning command surface
Protected read-only boards for morning outputs, active projects, waiting-on lists, and idea switching.
Protected entry →Memory
Continuity layer
Human-readable review of how memory, skills, notes, and graph recall keep Aether and Zeph from losing the thread.
Protected entry →Metrics
Health signals
Private operational health, freshness, uptime, and routing signals without exposing raw infrastructure in public.
Protected entry →Command
Controlled power
Approved-device request cards for bounded operations. It is deliberately separate from the public website and from read-only dashboards.
Night operations
While the family sleeps, the system watches.
Aether turns dreams, monitoring, and agent reviews into practical maintenance loops. The public story can name the pattern without exposing schedules, commands, or private payloads.
Dream loopReflective suggestions become candidate improvements for the family operating system.
Morning OpsUseful overnight signals get shaped into a human-readable morning dashboard.
Trifecta reviewImportant builds can be checked from multiple model perspectives before shipping.
WatchersDeterministic checks stay quiet when healthy and loud only when attention matters.
Safety contract
What belongs on the public side.
Long Family Hub is allowed to be impressive. It is not allowed to become a treasure map for the private stack.
| Layer | Public can say | Public never exposes |
|---|---|---|
| Portal | Purpose, service names, family-facing links, safe health labels | Private topology, raw hosts, ports, backend paths |
| Observability | Dashboard, memory, metrics, read-only, login required | Feeds, internals, callback details, audit storage, private records |
| Command plane | Approved-device only, allowlisted, audited, approval-gated | Action IDs, execution mechanics, request locations, shell or control details |
| Companions | Aether and Zeph have separate lanes and protected boundaries | Private messages, Sasha-only context, family-sensitive material |