Move outputs forward through pipeline stages (Draft → Review → Polish → Deliver) — no skipping, no backward oscillation without explicit regression decisions

Why This Is a Rule

Output production has natural stages: Draft (generate content), Review (evaluate structure and argument), Polish (refine language and formatting), Deliver (distribute to audience). Each stage requires a different cognitive mode, and mixing stages produces the same interference as mixing creation and editing (Separate creation and editing into different calendar blocks with 30+ minute gaps — defamiliarization enables fresh-eyes error detection). Oscillating between stages — drafting, then reviewing, then back to drafting, then polishing, then back to reviewing — multiplies context-switching costs and prevents any stage from being completed.

The forward-only constraint ensures each stage fully completes before the next begins. This mirrors the manufacturing pipeline principle: parts move forward through stations, never backward. Backward movement (rework) is expensive and signals a problem at a prior stage that should be addressed systemically, not through per-item regression.

The "explicit, documented regression" exception acknowledges that sometimes review reveals a fundamental draft problem that requires returning to the draft stage. But this regression must be conscious and documented ("Returning to Draft because the core argument is flawed — need to restructure before proceeding"), not habitual oscillation ("I'm not happy with this paragraph, let me redraft the whole section for the third time"). The documentation requirement creates friction that discourages casual regression while permitting genuine course corrections.

When This Fires

• When producing any multi-stage output (articles, reports, proposals, presentations)
• When you notice oscillating between drafting and editing without making forward progress
• When outputs stay in "in progress" indefinitely because they never advance through stages
• Complements Separate creation and editing into different calendar blocks with 30+ minute gaps — defamiliarization enables fresh-eyes error detection (creation-editing separation) and Three sequential editing passes for high-polish outputs: structural (organization) → line (clarity) → copy (mechanics) — never optimize all simultaneously (three-pass editing) with the pipeline discipline

Common Failure Mode

Perpetual redrafting: the output oscillates between Draft and Review endlessly. You draft, review, find problems, redraft, review again, find new problems, redraft again. Each cycle feels productive but the output never reaches Polish or Deliver. The constraint violation is the regression from Review back to Draft without an explicit decision.

The Protocol

(1) Define your pipeline stages: Draft → Review → Polish → Deliver (or your variant). (2) When working on an output, identify which stage it's in. Work only on activities appropriate to that stage (One cognitive mode per stage: draft = generate, review = evaluate structure, polish = refine language — never mix activities from different stages). (3) Advance to the next stage only when the current stage's gate criteria are met (Check 3-5 yes/no gate criteria at each pipeline stage transition — any "no" keeps the output in its current stage until addressed). (4) If review reveals a problem requiring regression to a prior stage, make it explicit: "I'm moving this back to Draft because [specific reason]." Document the reason. (5) Track regressions: if the same output regresses more than twice, the problem is likely upstream (unclear scope, missing input, wrong template) rather than in the current stage. Fix the root cause rather than continuing to oscillate.