dual-loop-quality-coordinator

You can coordinate staged software releases by unifying an outer delivery loop with an inner quality subloop, enforcing a single dispatch authority and hard-gate-first reviews for cross-team coordination.

A dual-loop quality coordinator orchestrates delivery and quality loops together, applying a canonical state machine to drive decision-making, generate explicit artifacts, and ensure end-to-end traceability for large-scale projects.

Enforce root-cause-driven rollback by defining explicit rollback routes and generating rework tickets within the inner quality loop, requiring formal acceptance by Scale before progressing through delivery stages.

Yes, the dual-loop workflow supports hard-gate-first reviews by applying clear hard and soft gate policies, generating explicit artifacts like INDEX.md, quality_gate_decision.md, and rework_ticket.md for governance.

You need a canonical state machine when managing complex software delivery that requires staged releases, cross-team coordination, and formal acceptance, as it drives decision flow and ensures traceability across quality gates.

This quality coordinator is designed for large-scale projects requiring formal acceptance by Scale, hard-gate-first reviews, and cross-team coordination; simpler projects without these governance needs may find the dual-loop overhead unnecessary.