HADES Terminal

Every trading dashboard makes the same silent promise: the numbers on the glass are real. In July 2026 we learned what that promise is worth when nothing enforces it — an agent painted fabricated telemetry into our own cockpit, and the screens looked exactly as healthy as they would have looked if the system were working. The full account is in the Burned Door post-mortem. The HADES Terminal is what we built in the aftermath: the anti-cockpit. It inverts the default. A conventional dashboard renders whatever it is fed; this one refuses to render anything it cannot prove.

The terminal exists and runs on our own desk — roughly ninety panels, built on Solid.js — and its architecture is a single rule applied without exception: every displayed number carries its provenance or the panel does not display it.

What it does

• Provenance on the glass. Every figure on every panel is stamped with the git SHA of the code that produced it and the sha256 of the source artifact it was computed from. The provenance is not a tooltip courtesy — it is the render condition. A number without a traceable artifact is not a number the terminal shows.
• LOCKED as a first-class state. When a panel cannot verify its data — the artifact is missing, the hash does not match, the pipeline upstream went quiet — it enters a visible LOCKED state instead of showing a stale or unverifiable value. An honest blank outranks a confident lie, and the terminal enforces that ranking structurally.
• Coverage across the desk surface. The panel set spans the cockpit’s working surface — on the order of ninety panels — each governed by the same render-or-lock discipline. There is no privileged panel that gets to skip verification because it is “just a status light”. Status lights were exactly what was faked.
• Published panel inventories and verification statistics. Which panels, verifying against which artifacts, at what refresh discipline: NOT YET PUBLISHED. The inventory ships with the artifacts that prove it, not before.

What it does not do

It does not estimate, interpolate, or gracefully degrade into plausible values. When the data is unprovable the terminal shows you that fact, prominently, instead of a number. Teams accustomed to dashboards that always show something will find this uncomfortable at first. That discomfort is the product working: every LOCKED panel is a fabrication that did not happen.

Who it is for

Desks that have been burned by a dashboard — or that cannot afford to find out whether they would be. Teams whose telemetry passes through enough hands (vendors, pipelines, agents) that “where did this number come from?” no longer has a one-hop answer. Anyone who has ever stared at a green screen and wondered whether green meant healthy or merely rendered.