Tip: Roll Out Autonomous Loops in Three Stages — Report, Assisted, Unattended

GitHub·medium signalXBlueskyLinkedInCopy link

The loop-engineering guidance formalizes a phased autonomy ladder: L1 the loop only reports what it found, L2 it proposes changes a human applies, L3 it runs unattended. It pairs this with 'intent debt' — the comprehension gap that accumulates as loops grow and nobody remembers why a given gate exists — as the reason to keep a written LOOP.md/STATE.md pair and run drift detection between them. The seven shipped starters (pr-babysitter at 5–15m, ci-sweeper, dependency-sweeper at 6h–1d, changelog-drafter, post-merge-cleanup, issue-triage, minimal-loop) each name their intended cadence, which is the parameter most people get wrong first.