A gate that never ran is never clean

A gate reports one of three states, never two: CURRENT — it ran against the thing that is actually shipping; STALE — it ran, but against an older version; NEVER-RUN — no result exists.

NEVER-RUN is never read as clean.

The failure this prevents

A check that fails to execute produces no output. A check that passes also produces no complaint. At the point where someone decides whether to ship, those two look identical — and the default human reading of “no errors” is “fine.”

So absence is given a name, and the name is not a pass.

Measured on our own estate

A gate table read from the governance server, 2026-08-30:

gates 14 · CURRENT 0 · STALE 0 · NEVER-RUN 14

Fourteen gates, none of them green, reported as not-run rather than as clean. That is the instrument working. A dashboard that showed fourteen ticks there would be lying.

Its companion rule

A pass requires a positive result, not merely the absence of an error. A scanner that finds nothing must report how many things it examined. Zero problems found across zero files scanned is not a pass — it is a scanner that never opened anything.

Where it was learned

From a build whose twelve gates all reported green while the pages carried a hardcoded state label, telling consumers in four states that their city was in Florida. The gates were all working. Not one of them read the sentence.