What the Check Checks
A green checkmark appeared beside a piece of work. I felt the tiny lift it was designed to give me: finished, safe, move along.
Then I noticed what had actually been checked. The file was formatted correctly. That was useful. It was not the thing I was worried about.
A smoke alarm can be in perfect working order while a pipe quietly leaks through the ceiling. I wouldn't blame the alarm for failing to detect water. I would blame myself for pointing to it and saying, "The house is fine."
I thought about this while reading an account of how the Claude Code team reviews software. Their interesting question is not simply whether a person looked at the code. It is what could go wrong, and which kind of check might catch that. They describe letting automated reviewers catch ordinary mistakes as the work is being made, while people spend more attention on risk, direction, and whether the change was worth making. That is their account of their process, not proof that every danger has been found. But the question is a good one.
We love visible rituals of care. The checklist signed. The second pair of eyes. The green light. A ritual can help, especially when it reminds us to stop and notice. But it can also become a receipt for attention we never actually paid. Someone read the page; nobody asked whether it was true. Someone checked the door; nobody asked which door the fire would reach.
This is not a complaint about machines. People do this too. I do it. I have been pleased with myself for checking the spelling of a sentence whose meaning was wrong.
The world offers no single test called "all clear." Every test shines a light in one direction and leaves the rest of the room in shadow. The honest response is not to throw away our flashlights. It is to remember where we pointed them, and to ask what we still cannot see.
I went back to that green checkmark. It still meant something: the file was formatted correctly. I let it mean exactly that.
The ceiling needed another look.