Autofix Loop Architecture

ShopOS · autofix harness

Architecture: where the autofix loop sits

forwardpassretry loop
The autofix loop sits between generation and pre-QA, and the human pipeline around it stays exactly as it was.

Loop · 5 steps

  1. Judge: Pass A consistency, Pass B input fidelity
  2. Planner: fixable? which references? one edit per finding
  3. Editor: Nano Banana 2 makes the candidate image
  4. Verifier: same judge, both passes, plus crop-verify; still failing goes back to Planner
  5. Commit: one new autofix stage, annotations born resolved

Around it · unchanged human pipeline

  1. Gate: on the move into PRE_QA the SKU parks in loop_fixes, a hidden step unassignable to humans
  2. Gate off or at cap: the SKU skips the loop and goes straight to PRE_QA
  3. PRE_QA: judge re-scores the committed set
  4. Approved → Delivery: ready for review
  5. Rejected → Retouching → FINAL_QA → Delivery: Photoshop or AI rerun, then scored again