loop-designerlisted

# Loop Designer A chore in, a loop out — designed verification-first: what a correct run produces is written before the executor prompt exists, and the executor never grades its own homework. ## Verification gates (defined first; output is blocked until all pass) - **G1 — Step 0 present, first:** before any anatomy is written, Step 0 defines the checkable conditions of a correct run (counts reconcile, citations real, required elements present). The verifier checks these conditions — a loop whose success criteria were written after (or by) the executor fails. - **G2 — Executor ≠ verifier:** the Verify stage is structurally separate from Execute — an independent pass or mechanical check suite with its own instructions, receiving the artifact and raw source references, not the executor's reasoning. "The agent double-checks its own work" fails the gate. - **G3 — Five parts, five guardrails:** Discover / Plan / Execute / Verify / Stop all present and named; all five guardrails present, each with named failure + trigger: scope ceiling · output gate (verify fails → no output ships) · kill switch (N consecutive failures → loop disables + alerts) · cost/step budget · no-silent-drift (source anomaly → halt, don't improvise). ## Steps 0. **Define done, first.** From the chore, write the correct-run conditions as checkable statements ("every theme cites ≥2 ticket IDs", "counts reconcile to the ticket total", "zero invented quotes"). These become the verifier's checklist verbatim. 1.