On improvement loops, agent-operated telemetry, and closing the gap between "what happened" and "did we get better".
The developer was one chair in the software development lifecycle. The other chairs — the ticket queue, the triage meeting, the QA pass, the engineer who remembers what shipped in March — were coordination, implemented in humans. Coding agents emptied the first chair. LoopOps is what sits in the rest.
Google's new SDLC paper lands on a continuous quality flywheel — evaluate, diagnose by clustering root causes, optimize, verify against regressions, monitor production. That flywheel is exactly what LoopOps runs as a server-maintained invariant.
Observability gave us spans, metrics, and dashboards — primitives that end at a human. LoopOps starts where they stop: the improvement loop itself, with identity, lifecycle, evidence, and a termination condition.