The Loop, Not the Leap, Why We Name It That Way

The brand rule here is one word: LOOP. Not leap. Every workshop, every post, every internal note holds to it, and people ask why often enough that it is worth writing down.

A leap is a single motion between two points. You commit before you can see whether the ground on the other side holds. If it does not, all that is left is another leap, in some new direction, hoping again. Nothing in a leap teaches you what went wrong, because a leap does not have a return path built into it.

A loop is different. A loop is a cycle: observe, act, observe again, adjust. The return is not an afterthought, it is the whole shape of the motion. You go around, you see what changed, you go around again with a slightly better model of what you are working with. Repair is possible because you never left the circuit.

This is not a metaphor we invented. It is how any adaptive system that persists actually works, from a thermostat correcting toward a setpoint to a nervous system predicting and revising (Class E). The active inference literature calls this the perception-action loop, and treats a mind as a system that keeps its model close to its world by iterating (Parr, Pezzulo, and Friston, 2022) (Class E). The technical vocabulary is not the point of this post. The naming discipline is.

The word "leap" shows up in a specific kind of marketing: the leap of faith, the quantum leap, the great leap forward. In each case, the word is doing the same job. It is asking you to skip the part where you check, and to commit before the evidence is in. That is exactly the posture we refuse. Our public work is a working hypothesis on an attainable path toward General Natural Intelligence, natural not artificial. Evidence is growing, evidence-classed, and tested in the open. Do not take the claim on faith. Test the build, inspect the gates, and help us find where it fails (Class F).

You cannot say "test the build" and "take the leap" in the same breath. One of them has to give. We picked the loop.

There is a practical reason too. In our configuration, every workshop is structured as a loop the group runs together (Class C). We name the observation. We propose the smallest possible action. We run it. We come back to the same table and read the result out loud. If the result is different from what we predicted, that is not a failure. That is the update. The loop closes, and the next loop starts one degree wiser. A leap has no closing step, which is why leap-shaped projects so often end in a shrug: it did not work, we do not fully know why, moving on.

The naming also protects the people in the room. When the frame is a leap, the person who committed first carries the whole risk. When the frame is a loop, the risk is distributed across turns of the cycle, and any one turn can be adjusted without anyone losing face. That is what human-in-the-loop actually means when you take it seriously: the human is not a rubber stamp at the end of an automated process, the human is one of the observation points on every pass.

We also use the word for a reason that is harder to defend and easier to feel. Leaps are dramatic. Loops are patient. A lot of what people call "innovation" is drama dressed up as progress: a launch, a pivot, another launch, another pivot, and no one ever sits still long enough to notice that the ground under the last leap was never checked. Loops make you sit still long enough. They are less flattering to the ego of the person leading, and much better for the people the work is supposed to serve.

So when you see us name a session, a cadence, or a whole program with the word LOOP, it is doing three jobs at once. It is a promise that observation happens on every pass. It is a fence against the "just trust it" reflex that leap-language invites. And it is a small, honest bit of grammar we hold to, because if we cannot keep the discipline in a single word we will not keep it anywhere else.

One more note, plainly: we do not always know what a loop will produce (Class U). The loop is a shape for finding out, not a promise of a specific result. If a given cycle returns something we did not expect, the shape is doing its job. That is the whole point.