So I built a loop. Here is what it told me.
First, how you check something like this. You set a dial. That is all an instruction is here: a number the output has to land near. Then you let the system write, and read the result back to see where it actually landed. Ask for a five and get roughly a five, the dial works. Ask for a five and get whatever the model felt like, the dial is decoration.
Everything in the five posts before this one rests on that. If the dials are decoration, there is nothing to check, nothing to tighten, and no loop.
So I checked, and got the worst possible result. No connection at all between what I asked for and what came out. Not a weak connection. None.
I published that before I had a fix. A null result you have written down is hard to explain away later, and it sends you looking for the cause instead of for a kinder description of the outcome.
The cause was dull. The target was reaching the model as advice, sitting among other advice, rather than as something the output had to satisfy. Once it arrived as a requirement, the dials started working.
Not all of them, and not equally. Some move the output reliably. Some barely move it at all, and no amount of rephrasing changes that.
And twice, when a dial looked broken, the fault was in how I was reading the result rather than in the writing. I was about to blame the model.
That is the honest shape of it. Most of the dials work, a few do not, and the ones that do not are where a person stays in the loop by design rather than by caution. But that person’s verdicts teach the thing. Next time it lands closer, and the time after closer still. The gap narrows. It does not close.
And here is what is left in the gap.
Take forty of these dials, every one of them a matter of judgement, and let them move against each other. That is not a checklist. It is a landscape. A creative person walks around in it all day and could not draw you a map of it, because there is no map. There is only the accumulated sense of where the ground is firm.
It is the same sense a pilot uses to put a half-loaded aircraft down on a short runway at full power with a force seven crosswind. Nothing in the manual covers that exact combination. Nobody flies it from a chart. They feel where the aircraft is in a space with too many dimensions to draw, and they act before they could explain.
That feeling is the last thing to be delegated, and possibly the last thing that ever will be.
Six posts, and this is the whole of it. Nobody made flying safe by making pilots more careful. They made it safe by knowing exactly where the edges were.