Glossary · blocked-report
GLOSSARY
BLOCKED report
The page a build writes when it stops. It carries every check verdict earned before the stop, the named reason for stopping, and no certified figure. A stack trace is not a deliverable: a refusal that leaves a log line and an empty folder discards the verdicts the file had already earned.
Principle 5 · Fail closed and stale
Where does BLOCKED report come from?
Principle 5 of the Kymira doctrine, Fail closed and stale. BLOCKED report is the name the doctrine gives to what that principle requires in practice.
What failure is BLOCKED report named after?
The stack trace deliverable. One unparseable date, a raw exception, zero artifacts, and 537 rows of provable verdicts discarded with it.
What does it look like on a real file?
One unparseable date stops the run, and the BLOCKED page still carries the fourteen verdicts the other 537 rows had earned.
Not for
Not a certified page. A BLOCKED report carries verdicts and reasons, and no figure on it may be described as certified.
Nearest terms
Last updated 2026-09-02 · Dylan, founder · one of 40 terms in the Kymira glossary, each one named after something we watched go wrong in a real build or in our own audits.