AI Ops Deck — pick a design direction

Flow: zero navigation — one dense always-on screen, made to sit on a second monitor. You don't "use" it, you glance at it. Anything urgent jumps to the red strip at top with a one-click action. Language: dark NASA console, monospace, phosphor status colors, uppercase micro-labels.

Flow: the opposite of a wall of panels — a triaged to-do feed. Every source (CI fail, HALT, rate limit, orphan, gate report) becomes an item with inline actions; you work top-down to inbox-zero. Raw dashboards exist but are secondary. Directly attacks notification fatigue: one inbox, deduped, severity-sorted. Language: Linear/Things — light, calm, generous whitespace.

$ reaper-ctl kill 88231 --escalate
→ SIGTERM … no exit (5s)
→ SIGKILL … [dry-run]

Flow: lives where you already live — feels like k9s/lazygit in a browser tab (or actual terminal via the harness Rust TUI). One focus view at a time, everything through hotkeys and a command palette (:plans, :ci, :kill 88231, :limits). Fastest possible for a power user; zero mouse. Language: Tokyo-night terminal brutalism, box tables, status bar.

Flow: built around your diagnosis doc — the landing page answers exactly one question: "how far is each project from live, and did it move?" GOLIVE scoreboards first; ops/CI/limits are drill-downs behind each card. This is the weekly-ritual (S3) instrument: scoreboard flat + commits piling = churn alarm, stated in plain words. Language: calm editorial print — serif numerals, warm paper, sparklines, zero blinking.

Flow: spatial — your machines and clouds are nodes on a living map; runners, agents, plans and deploys are chips that light up on the node where they run. Click any node → inspector with actions. Answers "what is running where" literally. Language: dark glassmorphism, glowing edges, sci-fi ops-center.