Living Compass · Planning → Build → Pilot → Deploy

OPCS Switchboard

Five boards in one circuit: the pilot epics left to build, the tech stack fully interwoven, the path to pilot, pilot → launch, and all 38 screens by role. Click any jack to light its circuit and read why it exists, what's left, and who owns it. Flip the inspector to Plain English — then Mark complete or Flag issue and hit Send Update.

▶ Open the live app · opcs.onrender.com

Pilot gate: production deploy

The Board — data flow across the stack

Highlight surface

drag to pan · scroll / pinch to zoom · click a jack to dive in · double-click empty space to reset

Readiness Audit — click a tier to open it

From PILOT_LAUNCH_READINESS_AUDIT.md. Cleared items are stamped; remaining items show exactly what's left and who owns it.

Stack Status

Done means done. Anything under “later” is optional hardening, not a blocker.

Layer / Service	Status	Remaining

How This Stays Current

The maintenance contract for this compass

✓
Seeded by Claude
Every jack, cable, and audit item reflects real project state as of the date above
Maintained by Codex
On each merge, Codex updates the changed node's status / whatsLeft / errors and bumps LAST_UPDATED
Next level: derived from the repo
A CI step regenerates the data from ground truth (task tracker, tests, file presence) so status is computed, not typed
Live, post-deploy
Pips fed by Sentry / Better Stack / CI — the board becomes the running system's nerve center

This board is alive. Seeded by Claude, maintained by Codex. The whole page renders from STACK.nodes, PATH.nodes, and AUDIT — edit only those, set REPO at the top of the script for doc links, and bump LAST_UPDATED.
Honest read baked in: most jacks show DONE-code but PARTIAL or NEEDS-VERIFY status — committed is not proven. This build learned that twice (Stripe validator drift, webhook-secret persistence — both caught only by live testing, both now fixed and logged on the Stripe and API jacks).