Episode Details

Trim 2 was the bottleneck at Lansing Delta Township. Night shift, nine hours, and most nights it gave up fifty or sixty minutes of downtime. Supervisors had tried. Everyone above them had tried. I had tried.

Then Abdelhak Radjai came to run Trim 1 and Trim 2 on nights.

He had been one of the best team leaders on that floor, and he never stopped acting like one. He would jump on any job on his line so someone could take a bathroom break, which is the highest-value currency on a factory floor. And he watched. He saw a new team leader drowning in repairs before she had mastered the six jobs on her own team, so he had another team leader cover them and sent her back to build her footing. He saw team leaders who never left their zone to chase a repair, and he parked them off the line, inspecting and fixing the defects coming out of his team and the four others in Trim 2.

Within a month the shift was closing under ten minutes.

Look at what he did. He observed the system, changed it, tested the change, and kept what worked. And the thing he improved was the people who improve the line. The improver improved the improvers.

Then Abdelhak moved on. One of the team leaders who had pulled for him went out on sick leave. Another left for the pilot team. The people who came in behind them held the line anyway, because Abdelhak had set the standard.

Now look for that standard in the plant’s books. The downtime number moved. The capability that moved it, and kept it moved after he was gone, appears nowhere.

That loop now has a name and a funding round. On August 5, Jeff Dean, Sanjay Ghemawat, Oriol Vinyals, and Quoc Le founded Discovery Loop to automate the experimental loop of research, including using AI to build more powerful AI. The field calls it recursive self-improvement. Another firm, Recursive Superintelligence, raised some $650 million within months of its founding.

We are ready to afford that loop to machines, in both senses of the word. We will pay for it and we will permit it. The people who already run it, in the frontlines of six industries across the United States and India, get neither. That’s the argument.

What the machine is given

Look at what a self-improving system requires, and what its builders gladly provide.

It gets its own performance data, in full, in real time. It gets permission to change itself; the whole design assumes it will propose changes and some will be adopted. It gets a protected budget for experiments, and the failed runs are understood as the cost of learning. It gets a memory that keeps the gains, in the weights and the next version. And it gets an evaluation it can trust, a test that tells it honestly whether it got better.

Data, permission, budget, memory, evaluation. We build all five for a model before we ask it to improve.

What the operator is given

Now check the same five against a machine operator, a maintenance tech, a line lead.

Her performance data goes up the chain. The Pareto charts and downtime codes are analyzed in a conference room she is not in.

Her permission to change the work is nil. Standard work belongs to engineering. She learns early to run it the way it’s written and keep the better way to herself.

Her experiment budget is zero. Every hour she spends learning lands as labor variance, and the Monday call asks why the number is red.

Her memory isn’t kept by the enterprise at all. Her capability appears on no ledger. When she leaves, it walks out the gate with her, and the accounting never registers the loss, because it never registered the asset. At best it is folded silently into goodwill on the day someone buys the company.

Her evaluation is a review written by someone who watched her work