convergence-loop

convergence-loop — Universal Convergence Loop Gate Reinforcement

A single pass declaration is hard to trust. A fix exposes new FAILs, and round 2 catches what round 1 missed. convergence-loop assigns a "truly passed" criterion to any gate.

Triggers

• /convergence-loop
• "convergence-loop", "how many rounds do we need", "not sure if it really passed"
• "suspicious of single-pass", "run until it passes", "keep verifying until clean"
• "single pass isn't enough", "need another round", "the fix might have introduced new issues"
• Auto-proposed: when the same artifact receives a FAIL verdict 2+ times in the same session (observable: 2nd FAIL on identical scope)

---

Origin

Extracted from a recurring "single-pass gate is hard to trust" pattern observed across multiple hub workflows. The canonical reference is:

• harvest-loop extract→attack→synthesize cycle: pattern extraction → attack → synthesis → the repeating structure must run until convergence

When the same structure recurs across gates, it is a skill.

Applicable Targets

Applicable Gate	Example
Skill diagnostic gate	harness-doctor + apex-review
Session harvest loop	harvest-loop extract→attack→synthesize cycle
External asset audit	steel-quench Wave 1~N
Domain-specific quality gate	Plug in any project-defined FAIL→FIX checkpoint
Any FAIL→FIX repeating structure	User-defined gate

---

Pipeline Structure

[Input] gate name + pass criteria + max rounds N (default 3)
    │
    ▼
Round 1
    │  Execute gate
    │  → All items pass: ✅ Round 1 passed → Round 2 (verification)
    │  → FAIL occurs: List FAIL items → Execute FIX → Round 2
    │
    ▼
Round N (N ≥ 2)
    │  Re-execute same gate (with FIX applied + search for new FAILs)
    │  → All items pass AND no FIX was applied in response to THIS round:
    │        ✅ Declare truly passed  ← the only terminating exit
    │  → All items pass BUT you fixed something this round (any severity):
    │        the fix is unverified → Round N+1
    │  → New FAIL: List → FIX → Round N+1
    │
    ▼
    │  → FAILs remain after N rounds: "Structural redesign required" → Escalate
    │  → Rounds clean but each keeps producing fixes: the fixes are manufacturing the
    │    findings → REDUCE THE DESIGN, then re-run (steel-quench §Convergence Criteria 4)
    │
    ▼ (if not converged within N rounds)
Escalation
    → Classify root cause: ambiguous criteria / FIX capability limit / gate design flaw
    → Output recommended action