Process v3.0

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

The successor to Praxis (Process v2.4.3). That page recorded the pipeline I built, ran on my own novel, and walked away from. This page records what I built instead. Implementation lives in a private repository. The claims below describe behavior a writer can watch happen; the machinery stays ours.

I proved that to myself the expensive way, with the pipeline described on the Praxis page. I built a pipeline that could revise an entire manuscript end to end, and it worked. The prose came back clean, coherent, polished. Too polished. It read the way an article reads, and my novel came back wearing someone else's suit.

The lesson survived the machine. AI belongs on the side of the line where it outclasses us. It can hold a hundred thousand words in attention at once and notice the pattern on page 412 that echoes page 38. It can remember every promise a draft makes and check whether the draft keeps it. Writing stays on our side. Every feature in this suite passes one test before it ships: is this asking AI to do something it surpasses humans at? A no kills the feature, however clever.

The shape of the work

Real writers rarely start at a blank page. They start buried: fragments, variants, scenes in four versions, notes that contradict each other, a draft and a half across three folders. Kaizen starts there. The suite turns a writer's scattered material into a coherent manuscript, then helps revise it while learning the author's taste.

Three stages, one taste.

Weaver works in threads. It takes the scraps you bring and works the threads into a weave you can read. It gathers what belongs together and sets the variants of the same scene side by side, so the strongest line is yours to take. When it suggests two fragments are related and you dismiss the suggestion, it remembers the dismissal, and it lets that dismissal lapse on its own once the writing underneath changes enough to deserve a fresh look.

Rewriter works in seams. It mends the weave into a full draft, chapter by chapter, inside the boundaries you set: your vision, your intents, your dictionary, your held lines. Lines you hold stay word for word. Every chapter's rewrite has to earn its place; a supervisor reads each result against your intents and passes it or sends it back, and when your original was already the stronger text, the original is what stays. The draft it cannot beat, it does not touch. When a rewrite you accept changes something earlier chapters depended on, the system carries that consequence forward into the plans it has yet to execute and backward into work you already approved, and tells you which chapters deserve another look.

R/W works in marks. It reads the draft beside you and marks the passages worth your attention, in six categories a writer would recognize: repetition, pacing, style, voice, continuity, interiority. Reads come first, always. Writes exist in one narrow form: a fix you invite on a span you choose, touching that span and nothing around it. Marks survive your edits the way a careful reader's sticky notes survive a shuffled manuscript, and when the text has changed so much that a mark's true home is uncertain, the mark stays put and says so. The system declines to guess about your book.

Taste, carried

The through line of the suite is a dictionary of your judgment. Explain why something works, in plain words, and the suite structures the explanation into a scoped rule: this quirk is deliberate everywhere, that one belongs to a single character's dialogue, this repetition is the point. Before a new rule takes hold, the suite tries it against everything you've already marked and shows you the blast radius, so one broad lesson never silently swallows a hundred honest findings. The dictionary travels: what you teach in Weaver, Rewriter honors, and R/W reads by.

The result over time is simple to describe and hard to build: every pass gets quieter. The suite converges toward your taste, and the marks that remain are the ones you'd have wanted a trusted reader to make.

The discipline underneath

Trust in this suite is engineered.

• Every promise has a check behind it. A rule the AI is told to follow is also enforced by plain code that reads the output afterward, so disobedience gets caught before it ships.
• The author's text is the floor. However a pass goes wrong, your original stands untouched, exactly as you left it.
• The machine explains itself. A suppressed mark can tell you which taught rule suppressed it. A kept original says so. Nothing important happens silently.
• You pay when the words land. Hosted work is charged on delivery; work that never lands costs nothing, and picking up where you left off is free.

Why kaizen

Kaizen means small, continuous improvement. The first draft is a sketch; the work happens on the second pass, and the third, and the one after that. I built this suite because I am its writer. My own manuscript goes through it, my own taste trains it, and every rough edge I hit becomes the next fix. The book is already in the mess. The suite exists to help it out, and to make sure that when it emerges, it is still, unmistakably, yours.

Process v3.0, July 2026. Weaver, Rewriter, and R/W are live at kaizenrw.com. The implementation, including the enforcement machinery named above, is private.

Raw text: process.txt. The pipeline this one replaced, in full: the Praxis page. Notes on the work as it happens: the workshop.