It’s 2029, and Ruben approves about eleven hundred routing decisions a shift. Cargo, mostly. Which container goes on which vessel, which load gets bumped when a port slows down, which customer waits. His title is Operations Controller and his badge opens a door on the fourth floor, and he is, on paper, the person who decides.

His first year, he read them. All of them, at first, then most, then the ones the system marked as unusual. He caught two real errors that year. One was a duplicate booking and the other was a temperature-sensitive load routed through a transfer that would have taken nine hours in the sun. He still tells that story at dinners. It’s a good story, and it’s six years old.

The volume went from three hundred a shift to eleven hundred over four years, and the error rate went the other way. He hasn’t found anything in nineteen months. Not because he stopped looking, exactly. Because there stopped being things to find, and a person can only hold a posture of suspicion for so long against a thing that’s right every time. Vigilance isn’t a virtue you can decide to have. It’s a resource, and his ran out the way water runs out, gradually and then not at all.

There’s a dashboard. Of course there’s a dashboard. It shows average review time per controller, and Ruben’s is 1.8 seconds, and he is aware, without ever having been told, that 1.8 is good and that the woman two desks down who runs at 4.1 has been asked about it twice. Nobody has ever instructed him to be fast. The number simply exists, in a color, on a screen his manager looks at on Mondays.

He held one back last spring. Something about a consolidation looked off, and he flagged it, and it went to review, and review took eleven hours, and the shipment missed its window, and the client complained, and the system had been right. Nobody was unkind about it. His manager said good instinct, wrong call, that’s the job. Ruben agreed and went back to work, and he has not flagged anything since, and if you asked him whether that experience changed his behavior he would tell you honestly that it didn’t. He’d believe it, too.

On a Tuesday in October, decision 4,417 of his shift is unusual. A chemical load takes a routing through an inland hub that hasn’t handled that class before, on paper for a cost reason that’s real, under a permit that’s technically valid. It’s the kind of thing that would have made twenty-five-year-old Ruben pick up a phone. He approves it in 1.7 seconds, along with the four hundred before it and the six hundred after.

Nothing catches fire. That’s important, and it’s the part people get wrong about this kind of story. There’s a delay, a fine, and an insurance conversation, and the total cost lands somewhere between annoying and forgettable. An incident report gets written the following month, and it’s thorough, and it identifies the process gap, and it contains one sentence that Ruben reads four times before closing the file.

Human approval was obtained.

That’s the sentence. It’s true. It cost 1.7 seconds and it satisfied every governance requirement the company has, and it will appear in the audit as a control that functioned. And sitting at his desk at the end of the shift, Ruben works out what his job has actually been for the last three years, which is not to catch errors, because he doesn’t, and not to add judgment, because there’s no time for judgment at 1.7 seconds. His job is to be a name. The process requires a human to have approved, so a human approves, eleven hundred times a shift, and the requirement is met, and the requirement was never really about him.

There is no Ruben, and I made up the containers and the fourth floor. I didn’t make up the rest. Approval interfaces with volume beyond any possibility of review exist right now, in banks and hospitals and warehouses. Dashboards that time the reviewer exist. The rule that a decision must have human sign-off exists in a great deal of regulation, and it is satisfied, today, by clicks that take less time than reading the first line. The phrase human approval was obtained is doing enormous work in a lot of places, and almost nowhere does anyone check what it means.

So tonight’s exercise. Find the place in your own organization where a person is required to approve something at a volume no person could actually review. Every organization has one. Now ask what that requirement is protecting: the outcome, or the paperwork after the outcome. Then ask which one it was designed to protect.