Platform & DevOps·The orchestrator's model of the world
something reads the difference between what you asked for and what exists, takes one step to close it, and then does it all again forever.
Reconciliation loop
Also calledcontrol loop, reconciler, level-triggered loop
The pattern every controller implements: observe actual state, compare to desired state, act, repeat. It is level-triggered rather than edge-triggered — it looks at where things are, not at what event just happened — which is why a missed message or a crashed controller is self-healing rather than fatal. It also explains the characteristic feel of these systems: nothing fails outright, things simply stay wrong while something retries, so timeouts and events matter more than error codes.