Loop Orchestration

The orchestrator's job in a quality loop is traffic control: routing artifacts from producer to critic, routing feedback from critic to producer, tracking round counts, monitoring convergence velocity, and making the stop/continue decision.

The stop/continue decision tree has three branches. Branch 1: all dimension scores meet threshold — approve and deliver. Branch 2: convergence velocity above 0.50 and round count below 3 — continue iteration. Branch 3: convergence velocity below 0.50 or round count at 3 — take best result, flag unresolved issues, and deliver with caveats. The orchestrator must never default to "one more round" without checking the convergence math. Gut feel is not a quality methodology.

1. Route Artifact to Critic The producer delivers. The orchestrator passes the artifact plus the scoring rubric plus any context from previous rounds to the critic. Include the previous round's scores so the critic can evaluate whether specific issues were addressed.
2. Evaluate Convergence Compare the new scores to the previous round. Calculate convergence velocity (delta per round). If velocity is below 0.50 or round count is at 3, proceed to delivery. Otherwise, route feedback to producer for another pass.
3. Deliver with Metadata Final delivery includes the artifact, the scoring history across all rounds, any unresolved issues flagged by the critic, and the convergence profile. The recipient knows exactly what quality level they are getting and what trade-offs were made.