8370
Empire Todaytoday.b3rt.dev
Live dashboard. Four headline counts: live sites, up services, scheduled cron jobs, indexed skills. 2-second upstream timeout per cell; down cells render red without crashing the page.
Empire Hub · A B3RT Empire Editorial · Vol. I · August 2026
A single page that links the seven meta-layer tools — the daily dashboard, the semantic index, the catalogue, the search engine, the shelf of covers, the year-end ledger, and this hub itself. Below them, the fifty wave-11 hobby sites grouped by craft, the wave-15 roadmap, the live maintenance status panel, and a cross-link rail into the public Cloudflare Pages bundles.
A live maintenance panel. The empire is the organism; this panel is its pulse. Updated on every pull of launch_static_skill.py; counts are read from the Empire Truth Registry on port :8340 at build time. If a number looks stale, the registry is down and the field desk is running on its bundled snapshot.
The Status section is the only meta-layer surface that must always tell the truth, even when the truth is unpleasant. Every cell renders down in red rather than papering over a failed probe. The four headline counts (live sites, up services, scheduled crons, indexed skills) are wired directly to the Empire Truth Registry; the timestamp and stamp below are written by the launcher when it last touched this file.
The panel is intentionally the first numbered section after the title-block — not the last. A reader who arrives at the Hub during an outage should know within five seconds, not fifty. Maintenance is editorial too: the ledger is honest about the organism.
Static HTML diff against last build: 0 unexpected changes. All section anchors resolve. Fonts loaded (Fraunces, Public Sans, JetBrains Mono).
Empire Truth Registry on :8340 answered in 184 ms. Returned live counts for sites, services, cron, skills. No fallback snapshot used.
New §10 added. Roadmap for four sub-waves: 15a (skill catalogue), 15b (truth registry 2.0), 15c (climbing/beekeeping public cross-link pass), 15d (consolidated command surface).
The Hub now references the public *.pages.dev bundles alongside the localhost ports — first time the editorial ledger has acknowledged the public-facing apexes.
All 50 wave-11 sites shipped, audited, and bound. Catalog frozen at 50 entries across 8 craft families. launch_static_skill.py handles the bind-race safely.
A single-screen FastAPI dashboard summarising the empire state in four counts: live sites, up services, scheduled crons, indexed skills. Refresh on demand. Built for the operator who wants to know whether the empire is alive without opening eight tabs.
Empire Today is the smallest of the seven tools and the one most often opened first. It pulls live counts from Empire Hub, Truth Registry, the local cron registry, and the skills directory on every request — short two-second timeouts so a downstream outage does not stall the dashboard. It is read-only, single-page, and refuses to grow features.
The dashboard was the first FastAPI service in the empire to ship with a graceful degradation pattern: if any upstream endpoint is down, the affected cell renders down in red rather than crashing the whole page. That pattern now lives in every empire service.
Live dashboard. Four headline counts: live sites, up services, scheduled cron jobs, indexed skills. 2-second upstream timeout per cell; down cells render red without crashing the page.
A six-lens index over every site, service, cron job, skill, doc, and hobby surface in the empire. Each lens returns rows with a typed schema. The Atlas is the empire's canonical map — once a surface lives in the Atlas, every other surface can find it.
Empire Atlas is the empire's semantic registry. It runs as a FastAPI service with a SQLite backing store, and exposes six lenses: sites (140 rows), services (11 rows), cron (68 rows), skills (809 rows in the catalogue, 2 fully indexed at present), docs (2 rows), and hobby (8 rows). Each row carries id, title, kind, status, owner, purpose, url, public_url, tag — a single schema across every surface.
The Atlas also exposes a truth block on every response: a live probe of every registered port with status, latency, and HTTP code. That truth block is what Empire Compass reads on the right rail; it is also what makes the Atlas self-correcting — when a service moves ports, the next Atlas probe reports the new port or marks the service down.
Six-lens semantic index. REST endpoint at /api/atlas?lens={sites|services|cron|skills|docs|hobby}. Returns rows + truth block on every probe. Backing store is SQLite; rebuild is a single cron job.
Six — sites, services, cron, skills, docs, hobby. Each lens returns the same row schema, so a downstream consumer can treat them uniformly.
Per-port probe embedded in every response. The Atlas does not just describe the empire; it measures it. The probe is what keeps the canonical map honest.
A flat-list wiki of every B3RT empire surface — 143 entries, each with a name, host, port, description, category, and tags. Search, filter by category, infinite scroll, click-into-drawer. The wiki is the canonical map rendered for humans.
Empire Wiki is the human-readable companion to Empire Atlas. Where Atlas serves JSON for agents and dashboards, Wiki serves an editorial ledger for people. It is built on the same cream-paper system as the hobby sites — Fraunces serif, no card-grid, no framework — but with a search field, a category rail, infinite scroll, and a slide-in detail drawer for each of the 143 entries.
The wiki is the surface most often linked from external sites. Every entry has a deep-link hash so a reader can share a direct reference to a specific surface. The drawer pattern (ESC to dismiss, click-outside to close) was borrowed from the empire-os surface and refined on the wiki for keyboard-first navigation. Its visual sibling, the Empire Bookshelf on :8422, lays out the same 143 entries as a 6-column grid of book covers — same data, different shape.
143-entry wiki. Search debounced 120ms; rail filters by category; IntersectionObserver drives infinite scroll at 30 rows per chunk; click-to-drawer for detail. Editorial ledger style on cream paper.
A single-field search engine across the six Atlas lenses, debounced 200ms, with a copper-tinted truth sidebar and a cross-link rail. The compass is the operator's find-anything tool — a faster path than the wiki when you already know what you're hunting.
Empire Compass sits between the wiki (read-first, browse) and the Atlas API (machine-first, JSON). It is a search-first surface: a single text field at the top, six flat lens tabs beneath, and a results table that updates as you type. The lens rail flips to ink-on-paper inversion (not accent fill) to signal the active lens.
The Compass ships with a bundled JSON snapshot so it renders even when the Atlas is down — a 3-second live-probe budget, then a graceful fallback to the snapshot with an amber snapshot fallback stamp. Every 15 seconds the Compass re-probes to recover live mode. The pattern is mandatory on every empire surface that proxies a backend.
Single-field search engine across six Atlas lenses. Debounced 200ms. Bundled JSON snapshot for offline fallback; re-probes every 15s. / focuses the field; Esc clears.
The Compass probes the Atlas every 15s. A green dot means live; an amber dot means the bundled JSON snapshot is in use. The stamp never lies — the operator trusts it.
On the right rail, the live port-by-port probe from the Atlas. Up, down, degraded — at a glance, the operator knows which surface is the bottleneck.
A 2026 retrospective. Six numbered editorial sections (Origin, State, Highlights, Wave 11, Mistakes, Forward) plus an exhaustive 149-site appendix. The annual is the empire's read-once, top-to-bottom surface — like a printed annual report, not a dashboard.
Empire Annual is the longest of the seven tools and the one with the highest word cap (5,000 visible words). It is built in the retrospective variant of the cream-paper system: numbered .shead blocks, a .factbox of headline numbers, a .skirs timeline, an exhaustive appendix, and a deep-copper accent (#8a5a3a) distinct from the warm-brown hobby accents.
The annual is meant to be read once, not browsed. There is no search, no filter, no drawer — just numbered sections that walk the reader through the year's build, mistakes, and forward bets. The appendix enumerates every surface (the contract: if you say 149 sites, the appendix must list 149). The Annual is the empire's institutional memory.
2026 retrospective. Six numbered sections (Origin / State / Highlights / Wave 11 / Mistakes / Forward) + a 149-site appendix. Deep-copper accent. ~3,900 visible words under a 5,000 cap.
http.server.November 14, 2026. The empire launched a wave-dispatch orchestrator against fifty hobby sites. Each site was a one-page editorial ledger — Fraunces serif, cream paper, no card-grid, no framework, no database. The wave started at 9:14am and finished at 1:08pm. Four hours, four minutes. Fifty sites.
The wave-dispatch orchestrator is the empire's parallel-make primitive. It accepts a list of slugs, dispatches one subagent per slug, and waits for all subagents to ship before it stitches the artifacts back into a single manifest. The subagents run in parallel against a shared context budget. The orchestrator never composes content — it only dispatches and stitches.
The fifty sites below are organised by craft family. Each entry links to its served URL on the empire port range :8400–:8426; selected entries also link to their public *.pages.dev bundle. The wave's only failure mode was the bind-race, which the launch_static_skill.py runner had already solved.
50 slugs queued. Orchestrator dispatches 12 subagents in the first batch. Each subagent ships one HTML file under 500KB.
12 sites shipped. Visual coherence verified by the empire-gauntlet critic. No bind collisions.
16 sites. One subagent dispatched its artifact twice — caught by the truth registry, the duplicate was discarded.
14 sites. Two subagents exceeded the context budget and were re-dispatched with reduced scope. Both shipped on the second pass.
50 sites shipped, 50 audited, 0 failed. Total wall-clock: 4h 4m. Mean per site: 4m 53s.
The next four months. Four sub-waves (15a through 15d) shipping in cadence: skill catalogue deepening, Truth Registry 2.0, public cross-link pass, and a consolidated command surface. Targets are scoped, not optimistic; dates are honest, not promised. This is the editorial version of ROADMAP.md — written for humans, not stakeholders.
Wave 15 is the empire's first explicit roadmap document. Earlier waves shipped in the moment — Wave 11 happened in a single afternoon, Wave 12 was a quiet regroup, Wave 13 was the cross-link rail, Wave 14 was the Status panel. Wave 15 is the first time the empire has sat down and said, in writing, what it wants to be when it grows up. It is not a sales plan; it is a build plan.
The four sub-waves are sequenced so each one unblocks the next. 15a deepens the skills catalogue so the Atlas lens is no longer mostly empty. 15b rebuilds the Truth Registry with a proper web UI and persistent history, so the Status panel can show trends instead of snapshots. 15c is the cross-link pass — every wave-11 site gets a public *.pages.dev bundle and a reciprocal link to the Hub. 15d ships a single command surface that an operator can hit to get the empire's state in one keystroke.
Index every skill in the empire into the Atlas skills lens with purpose, owner, and provenance. Move the 2-of-809 ratio to a 250-of-809 ratio. Build the editorial skill-bookshelf companion surface.
Rebuild :8340 as a proper FastAPI service with persistent SQLite history, a small web UI, and a 24-hour rolling probe window. Wire the Status panel to render trends, not just counts.
Every wave-11 site ships a public *.pages.dev bundle (climbing-1l0, beekeeping-cyl, lutherie-b3rt, and so on). Every bundle links back to the Hub. The catalog here grows a second column for the public URLs.
A single command surface — b3rt empire status — that prints the four headline counts, the open crons, and the next wave's ETA. No dashboard, no API call. The CLI is the dashboard.
One sub-wave per month. Each one ships behind a feature flag on :8433 for two weeks before promotion. The flag is a small uppercase stamp in the masthead — the operator reads it before believing anything.
Every sub-wave ships with a single static before/ snapshot of the affected pages. If 15b breaks the Status panel, we revert in one command and lose 48 hours, not a month. Empire fragility is bounded on purpose.
The probe service that keeps the map honest. Every count in the Status panel, every port in the Atlas, every result in the Compass — they all read from empire-truth-registry :8340. When the registry is down, the empire renders amber. When it is up, this is the source.