Three States, Not Two

Why two states are not enough

Almost every monitoring dashboard knows two states: good and broken. Anything it could not check quietly falls into "good"-because there is no alert, and an alert is the only language such dashboards use to speak about problems.

This is not a minor issue. Data collection that has stopped but reads as live; a backup that no one has tested but that "exists"; a service running week-old code while the deployment reports "done." We caught every one of these cases in our own system-and each was hidden precisely by collapsing "we do not know" into "good."

A fresh case: the first day of the automated collector left only raw snapshots, and the summary did not exist. The night analysis did not round this up to "no delta" - the record honestly says "no collection happened", and the next step was planned from that fact, not from silence.

The asymmetry rule

The absence of evidence downgrades a claim-and never raises an alert. "We did not look" is not "everything is fine," but neither is it "everything is broken." It is a third state, with its own name, its own appearance, and its own weight.

"Unset" is a terminal answer. It is rounded neither up nor down, and it demands action: either look, or honestly record that it is impossible to look from here.

What it looks like

On this site, "unset" is the most prominent mark on the page, not the faintest. It is an empty hatched diamond, the only textured object in the system. Instinct says to gray out what you do not know; measurements show that hiding gaps reduces trust in the data, while honestly highlighting them increases it.

The word always appears beside the mark and is never hidden inside an icon: color can mislead someone who is color-blind, shape can fail on a small screen, but a word misleads no one.