When something goes wrong, fix what produced it, whether that’s the harness, specification, checks or context. The machine is the valuable, lasting thing, and it includes the people who can run and change it.

The trap

You patch the artifact and move on, and the same fault comes back next time.

When looking at the output is right

  • You need to diagnose the machine. Open the file to learn why the machine went wrong, then add a check outside it so you don’t need to open it again.

Where it shows in the grid

“Said it twice? Make it a check” and the test for “No human reads or writes code.”