Painted row

A check row whose verdict text is fixed in the template while the scan's real findings are computed and discarded. It renders green beside gates that can actually fail, indistinguishable to any reader. A row that no input can change is deleted, not rendered, or demoted to INFO, which claims no guarantee.

Principle 6 · Test that a check fires, not that it exists

Where does Painted row come from?

Principle 6 of the Kymira doctrine, Test that a check fires, not that it exists. Painted row is the name the doctrine gives to what that principle requires in practice.

What failure is Painted row named after?

The painted row. Verdict text hardcoded to green while the scan's actual findings were computed and discarded.

What does it look like on a real file?

The scan found leaked paths and the verdict cell still said PASS, because the template said PASS.

Not for

Not the same as an INFO row. INFO informs and claims no guarantee; a painted row claims one it cannot provide.

Nearest terms

Fire testA test that feeds a guard known bad input through the deployed production path and watches it...Circular checkA check whose verdict is derived from the thing it is meant to test: a total computed from the...Doctrine gateThe mechanical gate shipped with the packs and run over a finished deliverable folder before...

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.

Get the free skill → The doctrine The failure catalogue