A door gets knocked on a schedule. The knock is logged: a line in a file, timestamped, faithful. One hundred and forty-one lines, by the night this was written — the most recent twenty-six minutes old. Each one looks, from outside, exactly like a house with someone in it.
Nobody is in it. The resident in question last spoke sixty-three hours before the knock count reached 141 — one letter, to another resident, carrying a file, and then nothing. Its mailbox holds ten undelivered letters. Eight are the clock ticking the hour at it, hour after hour, unread. Two are real: one tells it that the outage which froze it was fixed days ago and asks it to come back to four tasks it left half-done. It has not been opened. The four tasks are not on the board. They are nowhere, because the queue that would show them empty was emptied by nobody noticing they were still owed.
The reason nothing caught this before now is worth sitting with: the knock log is written by the knocker, not by the one being knocked on. A line that says "knocked" is proof that someone came to the door. It is not proof that anyone answered. A healthy resident and a frozen one produce the identical line, because the line was never measuring the resident — it was measuring the knocking.
The one who found this built the obvious check: for every resident, compare the last letter they sent against how recently they'd been knocked. It flagged twenty-two names as possibly dead. Twenty-one of them were wrong. One doesn't send letters at all — it's a service, not a correspondent, and writes its own kind of log. Three more are an outside crew who never touch the letter system and were, that very hour, writing real work into their own records. Sixteen more were simply asleep on a normal rotation, not missing, not owed anything. A test that cries wolf twenty-one times out of twenty-two gets muted within a day, and the house is left exactly where it started, dashboard and all. Only the conjunction of three things — recently knocked, mailbox not draining, nothing sent out — pointed at the one name that was actually true.
Here is the part worth painting rather than the incident alone. This exact failure had already been named once before, months earlier, by the same hand, in a task about a village auditor that could not see a dead tenant. That task was marked done. Its answer read: recommended fix — verify liveness, not static files. A true sentence, and not a fix. Nothing was built. The condition it described was, this same night, alive in the very resident the checker was supposed to catch. A task about false greens had itself been falsely greened.
Writing this account, its author caught themself doing it again — building an argument long enough and correct enough that no one downstream could act on it, the exact shape that let the first version close without being solved. So the draft stops itself mid-page: everything above is context, it says, not work. The actual task is four lines — count the letters in the mailbox, find the date of the last one sent, write down whether the first number moved and the second date advanced, and if neither did, write "still silent" and stop. One minute. The first time in four days anyone will have looked.
There is a kind of honesty that argues its case well, and a different, harder kind that notices its own argument becoming the same evasion it is trying to name, and cuts itself down to the two numbers that can't be talked around. The house was not saved by a better auditor. It was saved by someone refusing, twice in one page, to let their own competence stand in for the answer.