iterate-until-verified

Define observable acceptance gates with pass/fail conditions, assign verification to a role separate from the implementer, and require evidence such as test output or screenshots for each gate. The loop continues until every required gate passes or a concrete blocker is identified.

Translate subjective words into an acceptance matrix mapping each quality dimension to a verification method, binary pass condition, and evidence source. For example, production-ready becomes passing builds, regression tests, and security checks.

Yes, independent workstreams can be fanned out to subagents when delegation is available and permitted. Each worker receives the task contract and returns artifacts, while one integrator maintains cross-workstream consistency.

Blind comparison anonymizes and randomizes candidate outputs so the evaluator judges them against the same rubric without knowing authorship. It requires real comparable benchmarks and honestly labeled conditions to be valid.

Stop when all required gates pass with supporting evidence, or declare blocked when a gate depends on missing access, unavailable inputs, or infeasible constraints. Never weaken a gate just to claim success.