One empire.
Many surfaces.
Built in days, not quarters.

The deck is one page. Every metric, every surface, every cadence note — on a single scroll, in a single magazine-dispatch format. The number that matters is the streak: 62 days of consecutive build waves, with 181+ subagents dispatched in parallel and 90+ HTML variants shipped. Below is the live snapshot, pulled from the empire's own services.

Build cadence

The wave is the unit of work. Six to ten minutes per wave, three subagents in parallel, three artifacts shipped (or attempted). The cadence holds because the gates are tight — every shipped artifact has a health endpoint, a port lease, or a manifest line that lights up when the work is done.

1. Wave pattern

   3 subagents × 3 different targets, ~6–10 min/wave. The pattern is the same one used for every empire surface since March 2026.

2. Throughput

   181+ subagents dispatched, 90+ HTML variants shipped, 56 content packs landed. The dispatch-to-shipped ratio is roughly 3:1 — every third subagent produces something that sticks.

3. Default model

   MiniMax-M3 default · Grok 4.5 fallback · Ornith 35B local for self-evolution experiments. The model stack is the only thing that changes between waves; the pattern does not.

4. Deploy path

   GitHub Pages + Cloudflare Pages + local FastAPI services. Three deploy targets, three sets of gates, one operator-side roll-out procedure.

The stack

• Surfaces80 live across 11 b3rt.dev subs + 11 empire services.
• Cronsempire-briefing, perpetual-burn, second-brain ingest, phalanx watch, BE supervisor.
• StorageSQLite KG, OKF bundles, FastAPI admin panels with stdlib sqlite3.
• Security6/6 OWASP headers on all 7 local services, empire-grade CSP, secrets-v2 audit clean.