autonomous-review-looplisted

# Autonomous Review Loop Use this procedure for unattended implementation delivery in any repository. The default maximum is **10 correction/review iterations per unit**. A project may deliberately configure a lower cap; the configured value is carried through continuation and reviewer lineage and never silently replaced by a new default. An iteration is one implementation attempt followed by one fresh independent review of the resulting commit. A BLOCK starts a correction cycle. A PASS is usable only when it is machine-readable, produced by an independent fresh context, and bound to the exact current PR head. A timeout, missing verdict, stale verdict, forged or same-lineage identity, or missing local gate is a blocker—not a successful iteration. ## Durable loop contract At unit start, resolve the cap once and persist it with the unit ledger. Persist the attempt count, implementation/reviewer task ids, reviewed head, verdict, findings, and blocker reason. Continuation tasks must copy this envelope rather than reinitializing the counter. On restart, reload the envelope and reconcile the current branch/PR head before doing work. A changed head invalidates the previous PASS and requires a fresh review; it does not reset the count. The loop may merge only when all of these facts are true: - the latest independent reviewer is outside the implementer lineage; - the verdict is PASS and names the exact current head; - every required local/check gate is green; - the PR is mergea