What it was for
Nothing with this exact shape — but it has a clear lineage. Loop engineering is the practitioner's name for the discipline the engine's outer loop implies: once agents can run for many turns, the leverage stops being how well you prompt and becomes how well you design the system that prompts itself. As Addy Osmani puts it, "loop engineering is replacing yourself as the person who prompts the agent. You design the system that does it instead."
The verdict
EMERGES — and it is the operational floor under much of the rest of this ledger. The move is from directing a single agent, turn by turn, to building a loop with a written stop condition. Osmani's /goal "keeps going until a condition you wrote is actually true, and after every turn a separate small model checks whether you are done, so the agent that wrote the code isn't the one grading it." That separation — writer and grader as different models — is evaluation engineering made concrete, and it is genuinely new craft.
What changes
The ceiling moves from the tool to you: "your review bandwidth decides how many you can actually run, not the tool." The work becomes designing loops that are legible — that surface what they did fast enough to verify — and resisting the debts a smooth loop accrues: intent debt (the agent fills any gap in your intent with a confident guess), comprehension debt (the loop runs faster than you read), and cognitive surrender (taking whatever it returns without an opinion). The job, in Osmani's words, is still to "ship code you confirmed works."
The strongest objection
That this is just "an agent in a for-loop" dressed up. Contested: the distance between babysitting an agent and engineering a loop is the same distance the charter draws everywhere — between doing the work and specifying and verifying it. The loop is the artifact; judgment is what you build into its stop condition.
Falsification: downgrade to TRANSFORMS if loop engineering turns out to be ordinary automation and CI rescaled, rather than a new authoring discipline with its own verifier-separation and legibility constraints.