Part 3 · Operate
The revision loop
What happens between a rejected draft and one you see. This is why the queue is short.
01What it is
A rejected draft goes back with its specific violations and is rewritten against them, then re-checked. The cycle repeats until it passes or the attempts run out.
02Why it exists
Without the loop you are the filter. Every gate failure would arrive in your queue as a bad draft for you to reject by hand, and reviewing forty bad drafts to find four good ones is worse than writing four yourself.
The loop is why the gates can be strict. A strict gate with no loop produces an empty queue; a strict gate with a loop produces a short queue of things that passed.
03How to use it
- 01Nothing to do. The loop runs before anything reaches you.
- 02Read the gate report on a draft that reached you after several attempts. It shows what it fought with.
- 03If a whole batch fails, look at your context rather than the drafts.
04What good looks like
- You give it
- A draft that fails the voice judge with "you opened with a rhetorical question and they never do".
- You get
- The rewrite opens on a specific number instead, and passes.
- Why
- The judge returns instructions naming the specific mismatch, and those go to the writer verbatim.
Derived from the rules in the code
05What weak looks like, and what it costs
- You give it
- A judge that returned only a score.
- You get
- The rewrite changes something at random and fails again.
- Why
- A number tells the writer nothing it can act on. Both judges return fixes rather than scores for exactly this reason.
Derived from the rules in the code