Interfaces that
visualise a
running system

This page is a reactor console — and the reactor is the page itself. Every gauge, trend and meter ahead is bound to a real signal of this tab, read as a core vital. Scroll to run it.

The line's shape is the neutron flux; the dash speed is coolant throughput. Freeze it and you keep the shape and the level — only the motion (the rate itself) is what's lost.

The same instruments compose into a real cockpit — a non-document, zoned, fixed-viewport shell. Rail, instrument cells, telemetry aside, status bar. One reactor, one screen.

The core's eight subsystems — pumps, rods, exchanger, turbine, containment. Node colour = pressure, orbit speed = activity, ring = tier. The mesh and the legend are one dataset, two instruments.

A console is operated, not just read. Inputs, validation, and toggles carry the same chamfered HUD language — set a value out of safe range and the field shows it in colour, instantly.

Not a centered column — a mission console. Every signal this tab emits, at once: render, memory, DOM, network, timing, device, power, storage. ~50 live vitals, each a value, a bar, a range. Scanned, not read.