The autonomy-loop builder-reviewer loop

An autonomy-loop workflow in which a builder and adversarial reviewer pass a git baton between worktrees and prove each new test can catch its fix.

Use when

Use autonomy-loop when a repository has deterministic test, build, and lint gates plus a task suited to repeated builder-reviewer handoffs.

The loop

Use autonomy-loop for [repository task] after the test, build, and lint gates pass. Run /autonomy-loop:autonomy-init, then start builder and reviewer in separate worktrees. The builder reads LOOP-STATE.md, makes one bounded change, and adds a red-before, green-after test. The reviewer reruns the gates and proves the test by reverting or mutating the fix. Accept only on both passes; park protected or repeated-failure work for a human. Finish with the commit, gate evidence, test proof, trust tier, and risks.

Steps

• Initialize autonomy-loop, configure deterministic gates and protected paths, and create separate builder and reviewer worktrees.
• Have the builder read LOOP-STATE.md, implement one bounded change, add a red-before, green-after test, and hand off.
• Have the reviewer rerun every gate and use revert-or-mutate proof to show the test catches the change.
• Accept only on both passes; otherwise return findings or park the wave for a human when a circuit breaker fires.

Verification

Every accepted wave passes autonomy-loop's proof-of-test gate. The new test fails without the change, passes with it, every configured gate passes, and protected production changes remain human-gated.

Why it works

Separate worktrees and a git-backed LOOP-STATE.md baton keep the roles independent and resumable. The revert-or-mutate check catches tests that execute code without proving the fix.