Each card is a real surface, but this page no longer acts like a public directory of private controls. Public pages open. Operator capabilities are named by function, gated by policy, and kept off the open map.
Continuous-delivery control for the private runtime. Public visitors get status context; release levers and drift detail stay behind SSO.
Live health, history, and alert context for the operator. Public routes receive coarse freshness and capacity, not dashboard coordinates.
Recovery, replication, and restore workflows. Public copy explains the durability model without exposing the storage map.
Owned inbox, signed delivery, filtering, and resilience. Read the public essay; operator topology stays private.
A federated identity and timeline without a landlord. Public by design; runtime details stay separated from the story.
Drop in a commercial property ACORD 140 PDF and turn the form into clean, structured spreadsheet output. This is the friend-facing proof point: practical automation, not a dashboard screenshot.
How the private ledger works at the outcome level: imported, classified, reconciled, and backed up without publishing account context.
How the health layer answers whether the system is alive without publishing dashboard routes or query maps.
S.A.M’s cognitive architecture. Seven agents mapped to brain regions, four still missing. A map of what Nix can do and what it can’t yet.
Durability, recovery, and restore discipline without volume names, backup routes, or operator-only controls.