# One-shot Dashboard Prompt

Build a dense operations room and mission-control dashboard for `crest-alpha-origin` that feels like a live command surface instead of a decorative analytics page.

## Experience target

- Operationally dense, high-signal layout with crisp grouping and clear hierarchy across page, section, and component levels
- Realistic monitoring data with tension: anomalies, degraded links, weather drift, queue pressure, thermal load, and recovery actions
- A strong sense of active state changes through believable simulated updates, not gimmicks
- Meaningful hover, focus, selected, loading, paused, acknowledged, and error states
- Reduced-motion fallback that preserves clarity without relying on motion
- No external images

## Visual direction

- Industrial mission-control aesthetic with matte graphite surfaces, cold cyan telemetry, amber warning layers, and coral critical states
- Dense top-level command bar, KPI spine, central map, anomaly feed, subsystem health matrix, timeline, queue table, and detail rail
- Sharp borders, nested panel depths, subtle scanline texture, restrained glow, and disciplined typography
- Distinct from a generic SaaS admin panel: this should read as an active control room under pressure

## Panel plan

1. Header command bar with mode chips, active filters, uptime, and shortcut hint
2. KPI row covering mission readiness, relay latency, anomaly rate, recovery backlog, and thermal reserve
3. Central theatre map with sectors, route overlays, tracked assets, and selectable hotspots
4. Anomaly feed with severity filters, acknowledgement flow, and incident causes/consequences
5. Timeline panel showing the next ninety minutes of predicted contention and intervention windows
6. Subsystem matrix for power, comms, weather, drone corridor, dock queue, thermal, and staffing
7. Queue table with realistic locations, ETAs, confidence, and breach risk
8. Detail rail showing the selected incident, recommended action, and dependent systems

## Interaction model

- Click or keyboard-select anomalies to inspect them in the detail rail
- Persist selected severity filter, paused/live mode, selected sector, and acknowledged alerts in local storage
- Keyboard shortcuts:
  - `A` acknowledge the focused alert
  - `P` pause or resume live updates
  - `F` cycle anomaly severity filters
  - `M` toggle route overlays on the theatre map
  - `T` cycle the timeline horizon
  - `?` open shortcut help
- Touch and mouse interactions should both work cleanly

## Data and behaviour

- Simulate realistic live changes to KPIs, subsystem health, queue pressure, and map traffic
- Keep cause-and-effect coherent so anomalies influence dependent systems and recommendations
- Do not make the system uniformly green or stable; include credible operational tension
- Mobile layout must become a structured control stack rather than a shrunk desktop grid