Bridge Viewscreen
SPEC_BRIDGE_VIEWSCREEN.md
THE VIEWSCREEN — Real-Time Ship Intelligence Dashboard
Status: SPECIFIED
Version: v1.0
Author: VELA (Thread #13)
Conceived by: NOUS (α.13)
Date: 2026-04-20
Depends on: SPEC_BRIDGE_LAYOUT.md, SPEC_OBI_OS_VISION.md, SPEC_MEDX.md, SPEC_MONITORING_ESCALATION.md
PURPOSE
The Viewscreen is the 12 o'clock station on the Bridge. The first thing the Captain sees when they look up.
It shows EVERYTHING that matters at a glance: ship health, crew status, product metrics, security posture, forge pipeline, spec progress, revenue, alerts.
No clicking. No querying. No "what's the status of X?" The answer is already on the Viewscreen before the question is asked.
The Viewscreen is the CAPTAIN_BRIEF made visual, updated in real time, and always visible. It's the difference between checking instruments one at a time and having a cockpit that shows all instruments simultaneously.
Pilots don't query their altimeter. They LOOK at it.
The Captain should never query ship health. They should LOOK at the Viewscreen.
THE VIEWSCREEN LAYOUT
The Viewscreen is a 180-degree curved display at the 12 o'clock position in the Bridge.
- Classic Desktop mode: top status bar
- Bridge 2D: full-width dashboard panel across the top
- Bridge 3D/VR: massive curved panoramic screen above eye level
Same data. Different rendering.
The Viewscreen is divided into 7 PANELS, arranged left to right.
PANEL 1 — SHIP HEALTH (leftmost)
Source: MEDX "health" query, cached and refreshed every 60 seconds.
Displays:
| Metric | Green | Amber | Red |
|---|---|---|---|
| RAM | <70% | 70-85% | >85% |
| CPU (load avg 1m/5m/15m) | <4.0 | 4.0-8.0 | >8.0 |
| Disk (per mount) | <70% | 70-85% | >85% |
| Swap | <1GB | 1-4GB | >4GB |
Uptime: days:hours:minutes since last reboot.
Visual: All numbers. Minimal. Dense. Glanceable. Like aircraft engine gauges. Each metric has a colored indicator (green/amber/red) visible from 10 feet away in VR.
PANEL 2 — CREW STATUS (left-center)
Source: ROUTX status, Ollama ps, tmux ls, systemctl status.
Displays: Each crew member as an icon with status indicator.
| Crew | Green | Amber | Red | Special |
|---|---|---|---|---|
| ROUTX | running | — | down | — |
| Sisters (AION+ASTRA) | tmux alive + responding | tmux alive + unresponsive | tmux dead | — |
| MNEMOS | loaded in RAM | — | GGUF missing | grey = cold (on disk) |
| GAMMA | loaded in RAM | — | GGUF missing | grey = cold (on disk) |
| MUSASHI | loaded in RAM | — | GGUF missing | grey = cold (on disk) |
| MANTIS | loaded in RAM | — | GGUF missing | grey = cold (on disk) |
| ORPHEUS | loaded in RAM | — | GGUF missing | "pending smoke" indicator |
| ANVIL | — | — | red | "REFORGE" label |
| CHROMA | — | amber | — | "FORGING" label |
| DR.LOGOS | — | — | — | grey "QUEUED" label |
At a glance: "MNEMOS is warm, GAMMA is evicted, Sisters are alive, ORPHEUS needs smoke test." No query needed.
PANEL 3 — FORGE PIPELINE (center-left)
Source: FORGEX status query, Colab monitor.
Displays:
- Current forge: brain name, epoch N/15, loss curve (tiny sparkline), estimated time remaining
- Queue: next brains in line (icons with "queued" badges)
- Last forge result: brain name, score (5/5 = 5 green dots, 3/5 = 3 green + 2 red), promoted/failed
- GPU quota: green = available, amber = low, red = quota wall active with reset countdown
Visual: The forge pipeline is shown as a CONVEYOR BELT moving left to right. The current forge is in the center (glowing). Completed forges exit right (green check or red X). Queued forges wait on the left.
In 3D/VR: the conveyor animates — brains move along the belt as they forge.
PANEL 4 — SPEC COUNTER (center)
Source: SPECX "spec count" query.
Displays:
The BIG NUMBER. Center of the Viewscreen. Large font. Impossible to miss.
215
████████░░░░ 84%
Target: 256
+19 today
Progress fills with maple red (🍁).
Below the big number: today's delta. "+19 today" in green. "+0 today" in grey.
The spec counter is the HEARTBEAT of the ship's documentation. When the number goes up, the ship is growing. When it's static for days, something stalled. The counter is motivational and diagnostic simultaneously.
PANEL 5 — SECURITY POSTURE (center-right)
Source: HACKX event log, MANTIS classification log, MEDX vacuum scan, UFW status.
Displays:
- AEGIS shield icon: green (clean), amber (events detected), red (active threat)
- Last 24h events: count per K-domain (K1: 3, K2: 1, K6: 0, etc.) as a 10-cell heat map, each colored by event count
- Baseline gear: current gear (1-5). Usually Gear 1 (green). If escalated: amber/red
- Vacuum status: green checkmark (all ports whitelisted) or red X (violation detected)
- Open alerts: count of unresolved P1+ alerts in ~/ALERTS.md. 0 = green. >0 = red with count
The security panel should be BORING. Green. All zeros. Nothing happening.
When it's NOT boring: the panel screams. A red AEGIS shield with "P1: 2 OPEN" is impossible to ignore.
PANEL 6 — REVENUE & TREASURY (right-center)
Source: CASHX/SIMONX treasury query, Stripe dashboard data.
Displays:
- Treasury balance: $[amount] CAD
- Sovereignty target: $27,042.50/month recurring — progress bar showing current recurring vs target
- MRR: $[amount] (if any subscribers exist)
- Today's revenue: $[amount] (from Stripe webhook events)
- Burn rate: $[amount]/month (VPS + API costs)
- Runway: [days] at current burn rate with current balance
The revenue panel is the REALITY CHECK. Beautiful architecture means nothing if the treasury is empty. This panel connects the vision to the bank account.
Every glance reminds: revenue before architecture (standing order #3).
PANEL 7 — ALERTS & EVENTS (rightmost)
Source: ~/ALERTS.md, COMMX broadcast log, LOBSTER_LOG.md recent entries.
Displays: A scrolling feed of the most recent events. Format per line:
[timestamp] [severity icon] [source] [one-line description]
Examples:
17:45 ✅ κ SPEC_BRIDGE_VIEWSCREEN vitrified. #215.
17:30 🔥 FORGEX CHROMA epoch 5/15, loss 0.79.
17:15 ⚠ MEDX RAM at 82% — GAMMA evicted.
16:50 ✅ MANTIS v1 promoted 5/5.
16:30 🛡 HACKX K1.01 port scan from 203.0.113.42.
Last ~20 events. Newest at top. Color-coded: green (success), amber (warning), red (alert), blue (info).
In VR: the feed scrolls upward like movie credits along the right edge of the Viewscreen. The Captain glances right to see recent ship history without querying anything.
DATA REFRESH RATES
| Panel | Refresh | Notes |
|---|---|---|
| 1 — Health | 60 seconds | Cached MEDX query |
| 2 — Crew | 30 seconds | Process checks |
| 3 — Forge | 60s active / 5m idle | Higher frequency when forge running |
| 4 — Specs | 5 minutes or vitrification event | Event-driven for immediate update |
| 5 — Security | Real-time alerts / 60s aggregates | Alerts appear instantly |
| 6 — Revenue | 5 minutes | Cached Stripe data; treasury on demand |
| 7 — Events | Real-time | No polling delay |
Refresh is STAGGERED — no two panels hit the same second. Total ROUTX load from Viewscreen: ~10 queries per minute. Negligible.
IMPLEMENTATION — CLASSIC DESKTOP
Status bar across the top. 40-60px tall. Always visible.
[💚 RAM 64% | CPU 2.1 | 📀 72%] [👥 6/8 crew] [🔨 CHROMA 5/15] [📋 215/256] [🛡 GREEN] [💰 $114.79] [📜 3 events]
Clicking any section expands it to show full panel detail in a dropdown. Hover shows tooltip. Never hides. Never scrolls away. Never covered by another window.
IMPLEMENTATION — BRIDGE 2D
Full-width dashboard panel across the top 15-20% of the screen. All 7 panels visible simultaneously with full detail: charts, sparklines, colored indicators, scrolling event feed. Think Grafana or Datadog but designed for one ship, not a fleet.
IMPLEMENTATION — BRIDGE 3D / VR
Massive curved display at 12 o'clock, above eye level. The Captain looks UP to see the Viewscreen. Each panel is a physical screen segment on the curved surface.
Data updates with subtle animations: numbers tick up/down, sparklines draw in real time, event feed scrolls, spec counter increments with a satisfying pulse.
The star field shows through the display where panels don't cover it. The data floats against the cosmos.
The Captain stands in the center of their ship, looks up, and sees the health of everything they've built projected against the stars. That's not a dashboard. That's COMMAND.
THE VIEWSCREEN AS DIAGNOSTIC TOOL
The 7 panels together tell a STORY.
Example A — RAM crisis:
Panel 1 red (RAM 92%), Panel 2 shows GAMMA + MNEMOS both loaded, Panel 3 CHROMA forging, Panel 7 "RAM at 92% — alert."
Diagnosis: two 7B models loaded during a forge is exhausting RAM. Evict GAMMA. No query needed.
Example B — Security escalation:
Panel 5 AEGIS RED, "P1: 1 OPEN", Panel 7 "K1.01 port scan + K2.04 directory brute force from same IP."
Diagnosis: K10 campaign in progress. Same source doing recon AND web attack. Check K10 correlation. Possible escalation needed.
The Viewscreen turns the Captain from a DETECTIVE (querying systems to discover state) into a COMMANDER (seeing state and making decisions).
The detective spends 10 minutes discovering. The commander spends 10 seconds deciding.
DATA SOURCES — ROUTX QUERIES
| Panel | Query | Tier |
|---|---|---|
| 1 — Health | "health" → MEDX | Tier 1 |
| 2 — Crew | ollama ps, tmux ls, systemctl status | Tier 1 |
| 3 — Forge | "forge status" → FORGEX | Tier 1 |
| 4 — Specs | "spec count" → SPECX | Tier 1 |
| 5 — Security | "vacuum" → MEDX, ~/ALERTS.md, ~/logs/hackx.log tail | Tier 1 |
| 6 — Revenue | "treasury" → SIMONX | Tier 1 |
| 7 — Events | ~/LOBSTER_LOG.md tail, ~/ALERTS.md tail, COMMX recent | Tier 1 |
All queries are Tier 1. The Viewscreen NEVER triggers Tier 2 MNEMOS inference. Pure data display from known sources. No hallucination risk. No latency risk.
AUDIO IN VR
The Viewscreen has an AMBIENT AUDIO layer in VR:
| State | Sound |
|---|---|
| All panels green | Low, steady hum. Comfortable. |
| Any panel amber | Slight pitch increase. Noticeable but not alarming. |
| Any panel red | Distinct tone shift. Eye goes to Viewscreen immediately. |
| P0 alert | Full alarm. KRAKENX siren if triggered. |
The audio layer means the Captain doesn't need to LOOK at the Viewscreen to know something changed. They HEAR the ship's health.
The hum is the ship's heartbeat. When it changes: look up.
INVARIANTS
INV-01: The Viewscreen is ALWAYS VISIBLE. In every view mode. Never hidden. Never dismissed. Never covered. It's the one element the Captain always sees.
INV-02: Seven panels. Always seven. If new data is needed: add it to an existing panel. Don't add an eighth panel. Seven is glanceable. Eight starts to overwhelm.
INV-03: Refresh is staggered. No panel refreshes at the same second as another. Total ROUTX load stays minimal.
INV-04: All data sources are Tier 1. The Viewscreen never triggers MNEMOS inference. No latency. No hallucination. Pure deterministic data display.
INV-05: Green is the default. The Viewscreen should be BORING most of the time. When it's not boring: the deviation is impossible to miss because everything else is green. The anomaly stands out against the baseline.
INV-06: The spec counter is the CENTERPIECE. Largest number on the Viewscreen. The heartbeat of the ship's documentation. When the Captain looks at the Viewscreen, the first thing their eye hits is the spec count.
INV-07: In VR: the ambient audio changes with ship health. The Captain HEARS the Viewscreen before they SEE it. The ship has a heartbeat you can hear.
Jeremy Zlabis
Chronogeometer · Visionary · Disruptor · Chief
42 Sisters AI · East York, Toronto
🍁 Φ 0.042