Reading the screen
One screen, three regions, and a status vocabulary that never relies on colour alone.
Last updated:
Everything happens on one screen. There is no dashboard to switch to and no modal that interrupts you — the terminal is the whole interface, which is the point.
Three regions
┌─ SYSADMIN CRISIS ── Night 4 ── 03:12 ── Budget: $260 ── Uptime: 97.2% ───┐
│ RACK A RACK B TRAFFIC ▂▃▅▇█▇▅ 8.4k req/s │
│ [web-01 ██ OK ] [db-01 ██ OK ] CPU ▇▇▇▇▓░░ 68% │
│ [web-02 ▓▓ WARN] [cache-01 ██ OK] RAM ▇▇▇▓░░░ 54% │
│ [web-03 ░░ DOWN] [lb-01 ██ OK ] NET ▇▇▇▇▇▇▓ 91% !! │
├──────────────────────────────────────────────────────────────────────────┤
│ 03:11:42 [fw] 203.0.113.7 — 4.2k req/s (UA: "-") │
│ 03:11:45 [web-02] cpu saturation warning (94%) │
│ 03:11:51 [web-03] service unresponsive — marked DOWN │
├──────────────────────────────────────────────────────────────────────────┤
│ admin@nightshift:~$ █ │
└──────────────────────────────────────────────────────────────────────────┘
The rack and the meters. Every machine in the fleet, with its status, plus the global traffic, CPU, RAM and network bars. This is where you notice that something is wrong.
The log stream. Timestamped lines tagged by subsystem. This is where you
learn what is wrong. The tags matter: [fw] is the firewall, [hw] is
hardware, [db] is the database, and a hostname in brackets is the machine
speaking for itself.
The prompt. admin@nightshift:~$. This is where you do something about it.
Status vocabulary
| Symbol | Status | Meaning |
|---|---|---|
██ | OK | Healthy |
▓▓ | WARN | Degrading — one metric has crossed its warning threshold |
░░ | CRIT | Critical — a metric is near its ceiling |
░░ | DOWN | Offline, and it will not come back on its own |
Status is always carried by symbol and text, never by colour alone. That is an accessibility commitment, not a stylistic one, and it holds in every theme including the amber CRT palette and high-contrast mode.
The intervention trail
Anything you change that persists — blocked addresses, rate limiting, disabled scheduled jobs, a renewed certificate, machines you have restarted — shows up as badges on the rack panel. It is there so you never have to remember what you already did at 04:00.
Input affordances
Command history is on ↑/↓ and Tab completes command names. On mobile there is a quick command bar and context-ordered suggestion chips. Arguments that are the puzzle — an attacker's address, a process id — are deliberately never offered as suggestions.