Process v2.4.3

AI surpasses humans in many ways. Writing isn't one of them.

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. Too polished. The output reads with the polish of an article. Novels need a rougher texture. It is too polished to feel like mine. That is the actual problem. AI succeeded at generation. The result read as the system's prose, with the author's voice scrubbed out. A pipeline that rewrites prose normalizes prose, and 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: your choices teach it your taste, and that taste carries 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.