loop-goal

{
  "name": "loop-goal",
  "description": "Turn \"fix it until it's OK\" into a stopping condition a machine can decide — for DOCUMENT verification loops. Put the exit criterion into a deterministic detector's exit code, gate on a SET of detectors (never one), keep a monotonicity floor so deletion can't satisfy the gate, and enforce the generator/grader boundary mechanically rather than by instruction. Ships 11 dependency-free detectors (63-120 lines, meant to be edited), a template that wires the conventions into code, a test runner, and a fixed document format that collapses the per-document setup to a single yes/no. Deliberately narrow, and measured: the gate certifies TRACEABILITY, not correctness — in trials, a version that added five verbatim-checked quotes and a version that added none both passed the same gate. Says so in every output. Scope is prose; code has off-the-shelf checkers and different economics. Trials also surfaced that the detectors' own edit points become escape hatches — a skip-mark, a section name on the skip list, a zero declaration — and that under a tight turn limit the model stops iterating and reads the verifier source to solve it analytically. Both are documented rather than papered over: what cannot be closed is stated in the output. Pre-1.0.",
  "version": "0.3.1",
  "author": {
    "name": "dobachi"
  }
}