Pantheon App — Design Bible

This is a context loader, not a spec, PRD, or gate. Read it before touching any pantheon dashboard page. Judgment stays with the agent; this file makes the judgment informed.

Pre-flight ritual

1. Read the page's charter (§05) — its job, rung, and tier.
2. Read its "touching this affects" list — open those charters too.
3. Check §08 Shared Components if the edit reaches layout, ui primitives, or any component named in 2+ charters.
4. Check §10 Open Decisions — don't re-litigate a flagged decision mid-task or build against an unratified direction.
5. Brand tokens from global.css --pantheon-* vars (v2.0.0). Never reintroduce shadcn blue or the pre-v32 mint cockpit.

The app is the operator's cockpit for the Pantheon fleet. Three rungs, ranked. Every page charter names its rung — a page that can't, or claims two, is a smell (exactly what's wrong with today's SYSTEM section).

The four daily signals (interview 2026-06-10 — all four load-bearing)

• Anything dead/broken? — daemons, probes, deploys
• What did agents do? — sessions, dispatches, commits, task movement
• What needs my decision? — ask-human queue, reviews, blocked work
• Resource/cost drift? — dependencies aging, cost creep, machine load

Production is static CF Pages. There is no hub server in prod.

Current nav — as shipped (NavRail.tsx:11–35)

COMMAND        Portfolio (/) · Review (/review) · War Room (/war-room)
CONSTELLATION  Athena · Metis · Hermes · Apollo · Hades · Proteus · Plutus · Mnemosyne · Atlas
SYSTEM         Status (/status) · Fleet (/fleet) · Dependencies (/dependencies)
               · Dispatch (/dispatch) · System (/system)

Proposed IA PROPOSED — D1, pending ratification

Groups renamed to the question they answer. Maps 1:1 onto the four daily signals. Until D1 is ratified, the current nav is the truth — build against current charters.

Net effect on SYSTEM: 5 overlapping pages → 4 non-overlapping charters.

Format: job · rung · tier · data · touching-this-affects.

Command group

Constellation group — 9 pages, standard anatomy (§06)

System group

Project detail

Ratified direction: all 9 constellation pages kept. Every one follows this skeleton; stubs implement it with NotConnected states, never bespoke layouts.

Wiring a stub = filling slots 02–03 with real queries. Not a redesign license.

Single-consumer streams are safe to evolve with their page. Multi-consumer streams (war-room family, pulse, agents) require checking every consumer above.

1. Mockup-first stands. HTML mockup in apollo repo → approval → React in infra-pantheon. Bible read precedes mockup.
2. Brand: --pantheon-* CSS vars only (global.css, brand.json v2.0.0). Signals: active #22c55e · alert #E8B36A · fault #E86A6A · dormant #6A7AB0 · arc #06b6d4 (ceremonial, max 1/view). JetBrains Mono. Motion budget: pulse-slow 2.4s only. Radius 4px. No shadcn default blue, ever.
3. Language: all dashboard narrative EN (rule #20). Chrome labels EN here — internal fleet tool, no IS surface.
4. Tier discipline: new data-bearing page → LIVE tier if tables exist; never present mock/MSW data as live; NotConnected for missing tables.
5. Deploy: merge to master = ships (deploy-dashboard.yml, heph-hardened, smoke-tested run 27295320871). PR per rule #14 classes; pnpm build 0 TS errors before PR.
6. Same-PR rule: route/nav/data-source/shared-component change → update the bible in the same arc (apollo-repo commit pairs with the infra-pantheon PR).
7. Orphans — do not extend (deletion pending D4): OverviewPage, PortfolioPage, ProjectDetailPage + stale tests + legacy components/portfolio/ + useOverviewData.ts.