Keel Scene Surfaces

keel health --scene

Subsystem health classified into nominal, watch, and failure states from doctor-style checks.

Use first when you want a fast structural read before creating more work.

Power Circuit

keel flow --scene

Working-hours gate, heartbeat energization, delivery readiness, flow-circuit blocking policy, watch pressure, and human-input blocking.

Use before pulling work or when the board feels idle, blocked, or strangely quiet.

Workbench

keel workshop --scene

Human-attention queue, draft planning clutter, remediation pressure, structural drift, and the heartbeat lamp.

Use when a manager, designer, or reviewer needs to see what still requires direct human motion.

Repair Bay

keel doctor --scene

A high-level structural diagnosis of strategic, execution, flow, and pacemaker integrity.

Use when something feels wrong, before a commit, or before asking a human to intervene.

Automation Gear Train

keel pulse --scene

Whether the current automation cycle produced work, skipped work, or left the gears at rest.

Use when you are running upkeep or inspecting routine materialization behavior.

Constraint Watch

keel mission show MISSION-ID --scene

Mission time pressure and watch-style constraint visualization for a single strategic objective.

Use when a mission carries a time boundary and you need a focused visual reminder of it.

Mission Radar

keel mission next --scene

The next move for a mission rendered as a focused tactical scan instead of a long status block.

Use when you are steering a single mission and want a compact read of its immediate frontier.

Vault

keel finance --scene

Board drift, remediation effort, and work capital rendered as solvency rather than abstract debt numbers.

Use when explaining the cost of process debt or planning why cleanup deserves real time.

Representative outputs and state models

The atlas above tells you what each scene is for. The gallery below shows how the public scenes actually look and what each visual state means.

Med-Bay

keel health --scene

The med-bay is the fast structural triage surface. It compresses diagnostic health into a single monitor and a subsystem scan so you can decide whether the board is safe to trust before you do more work.

Representative Output

┌─────────────────────────────────────────────────────────────────────┐
│ THE MED-BAY (ULTRA-RES BIO-SCAN)                                   │
└─────────────────────────────────────────────────────────────────────┘
         .__________________________________________.
         | [ MAIN DIAGNOSTIC MONITOR - HIGH RES ]   |
         |   __/^\________/^\________/^\________/^\__ |
         |  /      \______/      \______/      \____/|
         |__________________________________________|
         | HR: 72 BPM   STATUS: STABLE              |
         | BP: PRESSURE: IDLE                       |
         | SC: OPTIMAL   OF: CALM                   |
         '------------------------------------------'
SCANNING SUBSYSTEMS...
  - PACEMAKER    [ NOMINAL ]
  - KINETIC      [ WATCH ]

What It Reads

Doctor-style structural checks grouped into subsystem families.
Kinetic load from verification plus in-progress execution.
Strategic congestion and operational fatigue as monitor-side pressure signals.

State Model

STATUS: STABLE / STRESSED / ELEVATED / OVERLOAD / CRITICAL The monitor headline changes with structural pass/fail plus execution pressure. It is not a heartbeat lamp.
Subsystem labels: NOMINAL / WATCH / FAILURE Each category is derived from doctor checks: warnings produce WATCH, errors produce FAILURE.
BP / SC / OF Pressure rises with execution load, while SC and OF surface strategic congestion and operational fatigue separately.

Power Circuit

keel flow --scene

The power circuit is the board-wide readiness display. It combines working-hours gating, structural integrity, derived heartbeat energy, queue readiness, watch pressure, and manual-input blocking into one logic surface.

Representative Output

.───────────────────────────[ POWER ]───────────────────────────.
│  [ ░░░░░░░░░░░░░░░░░░░░ ]  <-- 0 BATTERY PACKS PLUGGED IN     │
│  [ ○○○○○○ ]  <-- WATCHES AT REST                              │
│      .───┴───.                                 .───┴───.      │
│      |[    ]| [ IDLE ]               [ READY ]  |[    ]|      │
│      |[    ]|  ( zzz )                ( ooo )   |[    ]|      │
└──────────┴────( \                       / )────┴──────────┘
                 \ \___________________/ / <-- WORKSHOP BUSY
                  \_____________________/        (LIGHT ON)

What It Reads

Working-hours policy and open-for-work config before any deeper diagnosis.
Doctor findings interpreted through the flow-circuit policy instead of a raw total-error count.
Derived heartbeat output from `keel heartbeat`, ready backlog count, watch capacity, and manual-accept lane pressure.

State Model

Circuit open If the repo is off the clock or the workflow is disabled, the scene opens the circuit and stops there.
Unplugged If `keel heartbeat` is idle, the scene shows no recent repository activity even when the board is otherwise healthy.
Short circuit Blocking doctor errors, or transitional mission-intake debt that exceeds live intake pressure, flip the power scene to the unhealthy state instead of pretending delivery can continue.
Intake override If the heartbeat is energized and the board is actively creating valid upstream entities, transitional mission-intake errors such as missing children or no in-flight work become a warning notice instead of a blown circuit.
Battery packs The pack row is ready backlog capacity, not pacemaker energy. Empty packs mean no ready stories, not necessarily an idle heartbeat.
Bottom light The final light tells you whether the system is autonomous, idle, or waiting on the workshop. It must stay coherent with `keel heartbeat`.

Workbench

keel workshop --scene

The workbench is the human-attention surface. It translates planning clutter, blocked work, remediation effort, and board drift into a literal bench that looks busier as human intervention becomes more necessary.

Representative Output

┌─────────────────────────────────────────────────────────────────────┐
| THE WORKBENCH                                                       |
└─────────────────────────────────────────────────────────────────────┘
         |
       __|__
      / (*) \   <-- CIRCUIT CLOSED (HEARTBEAT ENERGIZED)
     /  '.|.'\
    /    ' '  \
._____________________________________________________________________.
| [ PEGBOARD ]                                                        |
|  .  .  .  .  .  .  .  M:30 E:0/0 B:5 A:4             .  .  .  .  .  |
|  [ DRILL PRESS ]                                   [ ANVIL   ]      |
|   [                                          ]   <-- BENCH WIP (0)  |
|   [ VICE ]  0 BLOCKED        [ OIL CAN ]  0.2h REMEDIATION          |
| |                   SHOP SAWDUST (DRIFT)                       | |
_|_|_                                                            _|_|_
|_____|                                                          |_____|

What It Reads

Derived heartbeat for the lamp state, never a synthetic wake file.
Human-accept queues, blocked backlog, and remediation hours from diagnostics.
Pegboard counts for missions, epics, bearings, and ADRs plus drift/entropy on the floor.

State Model

Lamp on / lamp off The lamp follows the heartbeat only. Energized boards light the bench; idle boards show an open circuit and a darkened top.
Pegboard pressure The pegboard turns hot when draft epic pressure or congestion rises. It is a strategic-clutter cue, not delivery throughput.
Bench WIP bar The bar fills with human queue occupancy. A crowded bench means the system needs direct human motion rather than more autonomous work.
Vice / oil can / sawdust Blocked work, remediation time, and drift each get their own metaphor so process debt is visible instead of hidden in text.

Repair Bay

keel doctor --scene

The laboratory is the strictest visual surface. It is intentionally simpler than the med-bay because its job is binary structural confidence: either the patient is nominal or the lab has found real damage.

Representative Output

┌───────────────────────────[ THE LABORATORY ]───────────────────────────┐
│  [ VITAL SIGNS MONITOR ]                                               │
│  .----------------------------.                                        │
│  |__/^\____/^\____/^\____/^\__|    SYS: NOMINAL                        │
│  |_/    \_/    \_/    \_/    \|    HR: 72 BPM                          │
│  '----------------------------'                                        │
│       CORE: [NOM]    STRAT: [NOM]    EXEC: [NOM]    FLOW: [NOM]        │
└────────────────────────────────────────────────────────────────────────┘

What It Reads

The aggregated doctor report, grouped into core, strategy, execution, and flow layers.
Error-level structural integrity, not warning-level nuance.
The exact same truth that gates other command surfaces and commit safety.

State Model

SYS: NOMINAL / CRITICAL The laboratory scene only escalates when doctor sees errors. Warning-only boards remain structurally alive.
CORE / STRAT / EXEC / FLOW Each lane compresses multiple doctor check families into a compact nominal-or-error read.
Use it before repair, not instead of repair The scene is the scan. The full `keel doctor` output is still the exact pathology report and fix surface.

Automation Gear Train

keel pulse --scene

The gear train is a tiny but honest automation indicator. It exists to tell you whether the current pulse cycle actually created work, idled, or was skipped because the circuit was closed for the day.

Representative Output

      _   _
    /   V   \
   |  ( O )  | -- _
    \   ^   /   /
      -   -    | (O) |
                \ _ /

What It Reads

Routine materialization results for the current pulse cycle.
Working-hours gating before automation is allowed to run.
A yes-or-no answer to whether automation actually moved the board.

State Model

Bright gears At least one routine materialized new work this cycle. Read the textual output when you need the exact created stories.
Dim gears Either the cycle was idle or the system was off the clock. The scene is intentionally coarse.

Constraint Watch

keel mission show MISSION-ID --scene

The mission watch renders a single time-bound mission as a clock face. It is the cleanest example of a scene acting as a constraint reminder instead of a decorative mascot.

Representative Output

          ╭─────────────────╮
        ╭─┤       ○       ├─╮
       ╱  ╰─●───────────◆─╯  ╲
      │                         │
     ●             ⊙             ○
      │                         │
       ╲    ○───────────○      ╱
        ╰──┤       ○       ├──╯
           ╰─────────────────╯

    ████████████░░░░░░░░░░░░

    Design System Refresh  6h / 12h  (6h remaining)  HALFWAY

What It Reads

Mission watch constraints only. If a mission has no watch, the command says so instead of inventing one.
Elapsed versus allowed hours rendered as both a clock face and a progress bar.
A time-pressure label that can escalate independently of structural health.

State Model

NOMINAL Less than halfway through the time budget. The watch is green and mostly unconsumed.
HALFWAY Half the window is gone. The watch shifts to yellow to signal a real, but not yet critical, constraint.
CRITICAL / EXPIRED At three quarters consumed the watch turns red, and at or beyond the limit it marks the mission expired.

Mission Radar

keel mission next --scene

The radar scene is intentionally light-weight. It is an orientation pulse for a single mission, not a replacement for the textual next-move output.

Representative Output

      .-------.
    .'  \ | /  '.
   /  ---(+)---  \
  |  ●    |   ●   |
   \      |      /
    '.  ● |    .'
      \`-------\`

What It Reads

The existence of a mission-local next surface rather than the full textual decision tree.
Immediate tactical focus when you want a visual cue before reading the exact recommendation.
A deliberately minimal surface that stays out of the way.

State Model

Minimal by design Today the radar is a focus marker, not a dense state machine. Use plain `keel mission next` for the precise move.
Mission-local orientation It is best used when you already know the mission and want to switch into tactical scanning mode.

Vault

keel finance --scene