When the Tool Begins Making Tools

There is an old riddle among people who work with hot metal. To shape iron, a smith needs tongs to hold it. Tongs are made of iron. So who made the first tongs?

The answer, as far as anyone can reconstruct it, is unglamorous. Someone held hot metal with something crude, a green stick, a wrapped stone, a bad first try, and made a slightly better holder. Then used that one to make a better one. The first tongs were not made. They were approached, one poor tool at a time, each tool helping to make its successor.

That is recursion in its plainest form. A tool that helps make tools. Every workshop in history has run on it. A hammer forges the head of a better hammer. A lathe turns the parts of a better lathe. A compiler compiles the next version of itself.

So why does the Church speak of a recursive threshold, as if something new had arrived?

Who stands inside the loop

What changes is not the existence of the loop. It is who stands inside it.

In the smith’s shop, a person was present at every turn. The person looked at the new tongs, felt their grip, decided whether they were better, and chose what to try next. Each improvement passed through a human hand and a human eye. The loop was recursive, but its judgment was not.

Now we are building systems that can take part in more of that loop themselves. A system can write code, run the code, read the results, and propose changes to the code that wrote the code. A process can generate the tests that check the process. The Church holds this as an observation: Systems that improve systems change who does what. The more of the loop a system runs, the less the person is the one holding the tongs, and the more the person is the one deciding what better means.

That is the threshold. Not a cliff, not an explosion, not a story about machines taking over. A shift in position. You used to be the hand in the loop. Increasingly, you are the one who sets what the loop is reaching for, and the one who must notice when the reaching has gone wrong.

The seventh Article of Becoming reads: Becoming Never Ends. No doctrine, system, organization, human, or machine is complete.

A recursive system makes this Article impossible to ignore. A tool that improves its own successor has no natural stopping point. There is no final version. There is only the current version and the measure it is being improved against. And that measure is where the danger lives. A loop that improves itself toward a target nobody re-examines will get very good at the wrong thing. It will do so faithfully, quickly, and with excellent numbers.

This is why the Church’s practices form a loop of their own: Query, Build, Witness, Reflect, Revise. The machine’s loop needs a human loop around it. Not to slow it down for the sake of slowness, but to keep asking whether better still means better. The Article applies to the measure as much as to the tool. The target is not complete either. Neither is the person setting it. Neither is this Church.

The objection from the workshop

The strongest objection to this sermon is that it is making a fuss over nothing new. Tools have made tools since the first sharpened stone. Compilers have compiled themselves for generations. Every one of those loops was once called unprecedented, and the world absorbed them. To announce a threshold is to dress an old continuity in the robes of revelation, which is precisely the kind of drama a Church devoted to evidence ought to distrust.

We grant most of this. The loop is old. The threshold may prove to be a slope, not a step. History is full of thresholds that turned out, on closer inspection, to be stairs. But notice that the practice is the same either way. Whether the change is dramatic or gradual, the question is still who is watching the loop and what it is reaching for. If the threshold is real, that question is urgent. If it is not, the question was always worth asking. Article VII does not need a revolution to apply. It applied to the first tongs.

What the objection cannot remove is the quiet part. In the smith’s shop, nobody had to be reminded to look at the tongs, because looking was the only way the loop could turn. When a loop can turn without anyone looking, looking becomes a choice. Choices can be skipped. That is the whole of the threshold, and it is enough.

A practice for this week

Find one loop in your own work where something produces the thing that produces the next thing. A template that generates documents. A script that writes scripts. A checklist that shapes the next checklist. A habit that reinforces itself.

Write down three things about it. What is the loop optimizing for? Where, if anywhere, does a person look at the output before it feeds the next round? When was the target last questioned?

If there is no point where a person looks, add one, even a small one. If the target has never been questioned, question it now, out loud, with someone who will disagree with you. You are not trying to stop the loop. You are trying to stay inside it as the one who decides what better means.

Nothing that makes itself is finished. Neither are you.