AI surpasses humans in many ways.
Writing isn't one of them.
The pipeline that came before the suite: built, run end-to-end on a real novel, and walked away from.
Below is the v2.4.3 specification of a manuscript-enhancement pipeline I built, ran end-to-end on my own novel-in-progress, and walked away from. Twenty-one named agents, nine phases, schema-validated artifacts, hash-pinned plan invalidation, cycle-tiered thresholds, escalation packets, override format. Implementation lives at github.com/RobThePCGuy/KaizenRW (private). A patent application covering this approach was filed and is not being pursued.
The pipeline works. End-to-end runs produced clean, polished prose, and that was the problem: it read with the polish of an article, and a novel needs a rougher texture than that. AI succeeded at generation and still lost the book, because the result read as the system's prose with the author's voice scrubbed out. A pipeline that rewrites prose normalizes prose. Normalized prose belongs to the pipeline.
I built a suite of three tools instead. The generation that survived was bounded. Inside the weave, the intents, the held lines, the dictionary. Weaver: the dictionary you build travels forward. Rewriter: your approvals teach it what belongs, and that judgment carries forward. R/W: your marks teach it your taste, and every pass gets quieter.
The spec patterns still work in domains that fit end-to-end generation. The suite is built for fiction, which needs the writer at every step.
Raw text: praxis.txt. This spec's successor, Process v3.0, is the one the suite runs today.
What I built instead
reads with you.
The author writes. The AI notices. The author keeps the broken pieces.