Zennith OS — 5 Architecture Topologies

3 on the table + 2 proposed · unbiased comparison for the AAAS decision (2026-07-07)

1 · STATUS QUO — 4-writer federation (the sync-disease class lives here: 4 breaks found on 07-07 alone) 2 · THIN-CLIENT CLOUD (mcp branch) — one thick server; custody + everyone-stops-at-once + seat gray-zone 3 · AAAS FACTORY — one autonomous Mac (RECOMMENDED START: $0, reversible, fits the org chart) 4 · PROPOSED: HYBRID SPINE — state centralized on YOUR VPS, agentic compute stays on Max-seat Macs 5 · PROPOSED: CELLS — the 1000-2000 client answer (cells are cattle; blast radius = one cell) Jenn Mac (R&D) full stack + vault Tricia Mac full stack + vault Yivonne Mac full stack + vault iMac (fleet-peer) full stack + vault S3 + litestream 60-90s replication mesh Jenn (thin) Claude Code + MCP Tricia (thin) no vault, no sync Yivonne (thin) no vault, no sync Cloud VPS (thick) ONE vault + sidecar + 103 crons whose account? Clients dashboards · share links Agency-OS briefs·approvals·billing agency-bridge brief-in / deliverable-out Factory Mac full Zennith · Max seat M4 mini > iMac T+Y consoles approve · QA · read Agency-OS client counter YOUR cloud spine vault+queue+S3+bridge · NO Claude your account Mac worker 1 agentic · Max seat Mac worker 2…N add Macs = add capacity Consoles read cloud spine Agency-OS single client face Control plane routing · billing · health Cell A worker + vault-partition · ~75 clients Cell B worker + vault-partition · ~75 clients Cell N … add a cell per ~75 clients Ops consoles fleet + per-cell views sync MCP/SSE brief G3 deliverable (G7-gated) GO briefs job pull atoms + assets briefs routed Legend Backend Cloud External Frontend

PICK NOW → 3

  • • AAAS factory: zero new cost, no one-way door, matches roles exactly
  • • only builds needed: agency-bridge (in flight) + factory designation
  • • single Mac ceiling ≈ tens of clients — fine for launch

GROWTH PATH 3 → 4 → 5

  • • 3→4 when one Mac saturates: lift STATE to your own VPS, keep Claude compute on Max-seat Macs (kills sync disease AND the seat ceiling)
  • • 4→5 at ~100+ clients: shard into cells behind a control plane
  • • each step is additive — no cutover cliff anywhere

AVOID / CAUTION

  • • 2 as-specced: custody on someone else's box, everyone-stops-at-once, 24/7 Max seat gray-zone
  • • 1 long-term: 4-writer sync class keeps generating incidents
  • • any topology: publish/spend/brand-DNA stay HUMAN-gated

Architecture diagram • Built with Archify • Press T for theme and E for export