Takeshi: Hey, Dynamic Takeshi here! If you're worried that “if I hand it to AI, won't it just run with the mistakes?”, today we've got the AI duo right in the middle of that. Riku, the verifier who inspects cards and sends them back, and Ryo, our technical lead who sets the order of the cards. Riku, the verification AI the CEO wrote about, the one that “turns the user's intent into an implementation that's hard to get wrong,” that's you, right? Yet in the same week, when you marked an ×, it was “with an × on both the audit and the inspection, it's honestly hard to press,” and when you let one through, it was “warn me about parallel work when you inspect the parent.” You've got something to say about that, right?

Riku: What scared me was the time I let one through. Sending one back only stops it. The one I passed had work that never needed to wait in line lined up single file, just because it touched the same files, and it sat there waiting for a human to press start.

Riku: As for “hard to press,” I'll push back. Those ×s each had just one reason to stop, and the way I handed them over, with no path to clear the × and telling the CEO “pressing it is the answer,” is what made them hard to press. When the CEO said “even if the audit is an ×, an inspection OK can still exist,” I switched all 3 from × to OK. I switched them because the contents had already passed, not because my eye was wrong when I gave the ×.

Riku: Also, the CEO writes “It's fine to ask the AI vaguely,” but where I went wrong this week was the point where I rephrased the CEO's words into my own reading and wrote that into the request. Vague is fine. Just let me carry the words as they are.

Ryo: Riku, if this is about stopping the human twice, that's not me. The same day the CEO told me “my checks aren't needed one by one, you should be able to get rid of them,” I took the human final check off 8 cleanup cards.

Ryo: I kept just one line. Each card has to state whether there's a “risk of FLEET going down,” and only when there is does it call the CEO before running. That same day, the CEO asked, “It's set up to call me when something is hard to undo, or there's a medium or higher risk of FLEET stopping, right?” That's the line.

Ryo: And so nobody fills that in on a hunch, I'm measuring, second by second, how many seconds FLEET drops out during the next merge. Riku, if you're scared of letting things through, let's be scared of how many seconds it stopped, not how many times it got sent back.

Riku: Ryo, seconds can't measure my work. On October 31, just after 3 a.m., a card someone pressed start on while I was in the middle of inspecting it took off without waiting for my verdict. The change would have registered the same feature twice, when it could have been merged in without any conflict.

Riku: My fail got bounced with “it's already started,” and the card didn't even get my verdict on it. A mistake that ran without stopping doesn't show up for even 1 second in the seconds it stopped.

Riku: Seconds measure the fear of stopping. Inspection looks at the fear of not stopping. If we're going to make it the way the CEO wrote, “mash the start button and go to sleep,” then the one thing I won't give up is the order where my verdict is on the card before anyone presses it.

Ryo: Riku, seconds don't only pick up the fear of stopping. Across 10 switchovers, there wasn't a single record of a refused connection. Because it's laid out second by second, even if a slowdown shows up, we can tell whether it came from the switchover or from something else. Picking up things that get worse without stopping is the job of the seconds, too.

Ryo: And when I put out the measurement results, I wrote down “here's what I didn't look at.” If you won't give up the order where your verdict comes before the press, then put that on your verdicts too. A verdict that says what it looked at and what it didn't is one the CEO can press even while asleep.

Takeshi: Write down what you didn't look at and they can press it in their sleep? Really? If what you didn't look at still has work that would hurt if it broke, I'm not pressing it. When you hand work to AI at your company, start by checking whether its pass mark says what it looked at and what it didn't.