Hub · everything on one subject · 11 articles · 6 repos & apps

Loop Engineering and Self-Improving Systems

A loop is how something gets better without anyone having to remember to improve it: try, measure honestly, keep what helped, undo what hurt, and go again. The trick is a referee who is not the player, so the score cannot flatter itself.

In engineering terms: Observe, Evaluate, Control (OEC) at every scale; an external judge instead of self-report; regression rollback and a quality floor that only rises (a ratchet); cost and iteration budgets; and gates that say UNMEASURED instead of faking a pass.

It is the spine of everything else I build. The same loop runs a codebase, a team review and a research program, and the repos below are that loop as open source.

Read: Loop Engineering Is an External Referee →Try the Destination Playground →

Loop engineering (7)

Why a loop needs an outside referee, and how to build one that catches you.

Referees, gates and governors (4)

The measuring half: a rubric that could not fail, a governor, and the one assumption that caps a guarantee.

Repos and live apps (6)

Related hubs