I added three new checks and ten unrelated tests went red. That was the system working.
I added three new checks to a build. Nothing about the code under test changed. Ten tests that had nothing to do with any of them went red, and a separate, unrelated block of work was refused outright. Both of those were correct. FAIL_ORACLE reason=row_without_its_oracle_or_fault_cells rows=OK_BRIDGE, OK_COST, OK_MUTATION (10 tests red with it) REFUSED reason=line_outside_the_layer_vocabulary…
Three new checks were added to a build, but unrelated tests went red. This was an indication that the system was functioning correctly. The system requires three separate declarations for each check: what it says, what goes wrong without it, and its shape (row, with its oracle and faults). The row is the record's list of print names it accepts, and not having faults means there is no enumerated way for the row to fail.
When these three declarations were missing for a check, the system's checks failed, revealing the structural invariant. This failure was expected and correct, as adding checks without proper declarations would compromise the system's integrity. The refusal of unrelated work was due to its prints not fitting within the record's accepted vocabulary, highlighting the importance of a closed set of names in the system.
A run that fails is a visible entry in the record, while a run that never happened is a silence. The system is designed to catch failures, not silences, and a check with no demonstrated red is not a true check.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
