FOR TECHNICAL READERS
The stack, the fleet, and the proof.
Plain voice, but we name the mechanisms and the counts. Every sentence below carries a receipt; partial systems stay labeled partial.
The stack
Three platform shells: Expo and Expo Router for iPhone and Android; Next.js 15 for the web as a sibling codebase (not react-native-web), per AD-043. Shared TypeScript-strict core with Zod schemas; Supabase Postgres plus Edge Functions on Deno; every write to the six run-state carriers goes through narrow SECURITY DEFINER doors since AD-088.
Web surfaces deploy on Vercel with three environments; GitHub Actions runs the gate suite; pnpm workspaces wire packages. The theme engine plus a 25-theme library supply runtime-switchable Trios.
Every model call routes through a LiteLLM gateway on Cloud Run (generated config from the capability registry). On the mail Mac, OpenClaw runs local Ollama for classification with zero cloud tokens. A Hetzner VPS hosts the deterministic browser stack for harvest and measurement.
The fleet
Work orders land in lanes on prepaid coding seats (Codex, Cursor, AntiGravity). The pull request is the bus: labels gate:ready and gate:returned. The Chief Architect gates on production-data render measured in a real browser, then merge, then three-environment promotion on green receipts (AD-101).
On 18 September 2026 pack H closed with fifteen of sixteen lanes merged the same day. Seven promotions with receipts ran 8–14 September 2026. On 22 September 2026 the operator walk-through filed nine production defects; nine lanes merged that evening (pack R).
Proof points by Designosaur
Nine concerns, nine names — portraits and stories live on the Designosaurs page; here we name only mechanisms and receipts.
The Designosaurs
Cleo — Should we build anything?
Every work order opens with an adopt-or-justify table: reuse what exists or explain why not. Seven research runners on a schedule feed observations into the notebook (paused September 2026 except the video monitor). AD-060 install/harvest/skip decides what we borrow from the wider web.
Still partial: Conversation intake is practice; the customer wizard and full Cleo dispatcher are not the default path yet.
Val — Scope, ethics, and jurisdiction.
AD-069 and AD-076 route models by jurisdiction and retention posture. The capability registry is the door: if policy does not admit a model, routing refuses it before any call is billed.
Still partial: The ethics gate exists on the generation line; it has not completed a clean end-to-end run.
Dromeo — What should it look like?
The theme engine validates Trio composition on seven axes and per-role contrast gates. A public-site read composes partial tokens and three looks for a partner demo. The /looks/ gallery proves each library theme on operator screens with a measured oracle (button color, surface, type family).
Still partial: Declared design compiled to every slot is proven on two screens (9/9); a generated app end to end is not.
Ada — Code under real checks.
The Designosaur dispatcher spine auto-advances each stage through eleven edge dispatchers. Typed checks and compile oracles run before any judge (AD-080). Repairs consume checker output only (AD-072).
Still partial: AD-058 caps each edge run at about 150 seconds, so Ada ships one screen per run today; there is still no clean Hello World end to end.
Trully — Is this good enough?
MAKER first-to-ahead-by-K voting runs only when no oracle exists and the decision is objectively votable (AD-051, AD-080). Taste routes to advisory scores plus human escalation, each captured as preference data (AD-081). Production-data render is the ship gate; accessibility checks block on AA failures.
Still partial: Generated-screen review on the generation line remains partial; acceptance tier gates are live.
Sun-sin — Safe to ship?
AD-101 environment ladder: test, then staging, then production only on green receipts. AD-088 grant-locked doors mean live run-state is commanded, never edited by hand. GitHub Actions and Vercel carry the promotion record.
Still partial: Migrations and edge deploys are Chief Architect actions after merge; lanes do not touch production.
Tycho — What was decided and promoted?
The wiki compiles entity pages from the notebook with lint and compile reports (SCHEMA.md). The decisions ledger is data, not prose. This public site runs the same receipt audit on every sentence.
Still partial: Not every notebook row has a compiled entity page yet.
Penny — Health, spend, and efficiency.
AD-052 makes the LLM capability registry mandatory truth. AD-102 keeps routing inside a declared envelope while the operator sees the case, not the config. Podium boards show spend and health; the weekly goal audit compares progress to recorded goals.
Still partial: Self-updating routing is live inside the envelope; not every spend line is customer-visible yet.
Wolfgang — Who owns the line and the schedule?
The run-state kernel (AD-088) commands transitions through narrow database doors. Stage transition edges advance work; the work-order shepherd detects stalls (implemented, not yet enabled in production).
Still partial: The generation line is parked for hello-world proof; fleet packs still merge under Wolfgang gate discipline.
Numbers we can show
Figures below already appear on this site or in cited census queries; nothing is rounded for effect.
Four Designosaur roles are partial on the generation line; the cards say which. Nothing here replaces a production walk-through.