Five AIs Approved the Fix. One Said Reject. The Loudest Wasn't the Truest.

I pointed six AIs at the machine I build with, the set of rules every change runs through before it touches anything real. Five read it and approved. One read it and said reject: do not ship, five things here are broken.

The one that rejected was the sharpest reader of the bunch. It went through the actual code line by line, and it was not inventing problems. The five things existed. The question was whether they mattered, and that is where it lost the thread.

It was auditing my one-person workshop as if it were a bank. It flagged missing locks on doors only I ever walk through. Every finding assumed an attacker, a crowd, a stranger with the keys. There is no crowd. There is me, one trusted hand, building alone. The findings were not wrong about the code. They were wrong about the world the code lives in.

So the move was not to obey the loudest voice and bolt on five new guards. It was to count the votes. Five readers saw the same picture and called it sound. I held the lone reject’s five findings up against them, and only one had been seen by anyone else. That one I fixed. The other four I wrote down and did not build.

A Reject Is a Vote, Not a Verdict

More reviewers only help if you reconcile them instead of obeying whichever one is most alarmed. The scariest finding is not automatically the truest. You run a panel so the frames can check each other, not so the loudest frame can win. My job in the middle is not to flinch at the red one. It is to ask which red the others also saw.

The cycle ended lighter than it started. One real fix kept, four inflated alarms left on the floor, a pile of dead machinery deleted along the way. The reviewers are godlike at finding things. Deciding which findings are real is still mine.

I am building this in the open, the judgment calls included. lovelearnlift.com.