Convergence Loop

Overview

A crash-safe orchestration engine for work too big for one pass: run rounds of small auditor+skeptic micro-batches over a rotating decomposition axis, persist every verified finding to an on-disk ledger immediately, and stop only when consecutive rounds produce zero new findings at the severity that matters. High signal beats high count; durable state on disk beats heroic context.

When to use / when NOT

Use when:

• Whole-repo or multi-surface audit/review/migration. The sibling skills release-audit, handoff-readiness, docs-deploy-readiness, security-surface-audit, and jargon-leak all run on this engine.
• The run will outlive one session or usage-limit window.
• A single pass already found real issues — more probably remain.
• Findings need an auditable, resumable trail a human can inspect mid-run.

A single pass is enough when:

• One file, one diff, or one PR — use one auditor + one skeptic, no loop.
• The property is objectively checkable (types, tests, lint, build) — run the checker instead.
• The user asked for a time-boxed quick look.
• The task is generative (build a feature) — this is an audit substrate, not a build planner.