Takes an existing article and improves it through sequential editorial passes without destroying the author voice.
OVERVIEW
The editorial pipeline takes an existing article and runs it through five sequential passes -- rewrite, flow review, red team, consistency check, and final polish. Each reviewer builds on previous work, not competing alternatives. The key insight: parallel-then-merge creates bland average prose. Sequential passes preserve the author's voice while improving clarity and rigor.
ARCHITECTURE
Structural improvements, clarity, and flow. Reorganizes sections, tightens language, and strengthens the argument -- while preserving the original voice and intent.
Checks transitions, pacing, and narrative arc. Ensures each section leads naturally to the next. Identifies jarring shifts or momentum drops.
Adversarial review for claims, tone, and backlash risk. Challenges assertions, checks for overstatement, and flags content that could be misread or misquoted.
Ensures edits across phases do not contradict each other. Catches when the rewrite says one thing and the red-team fix says another.
Last pass for readability and voice. Smooths rough edges from the editorial process. Ensures the final output reads like it was written by one person, not assembled by a committee.
DESIGN
v2.5 lesson: parallel-then-merge creates bland average. Sequential preserves voice. Each reviewer builds on previous work, not competing alternatives.
Went from 8 parallel phases to 5 sequential. The architectural shift was significant enough to bump to v2.0.0. Fewer phases, better output.
Each reviewer builds on previous work. No competing alternatives. No merge conflicts between editorial opinions. One document, improving over five passes.
RESULTS