Books, developed

A book is not a long article. It has an arc, a cast, facts it has already committed to, and a voice that has to hold for three hundred pages. Asking a chat window for "chapter four" ignores all of that. The manuscript workspace is built around it.

An outline the book is written against

Work starts with an outline: the shape of the book, chapter by chapter, with what each one has to accomplish. Every later step is written against that outline rather than against the previous paragraph, which is what keeps a long manuscript from drifting into a different book by the middle.

Chapters, drafts and review as separate things

Each chapter holds drafts, and each draft can be reviewed before anything replaces the working text. A narrator persona writes; an editor persona reads it back critically and records what needs work. You can refine a chapter repeatedly, and the earlier drafts remain — so a revision that made things worse is recoverable rather than final.

Continuity is tracked, not remembered

The details a book must not contradict — who knows what, when something happened, what a room looks like, which name a character actually goes by — are recorded as continuity notes attached to the manuscript. They are written as the book is written, so later chapters are drafted against established facts instead of a model's recollection of them.

The cast is explicit too. Characters are assigned, with motivations and points of view, so a chapter written from one character's perspective stays in that perspective.

A finished book can be opened again

Most tooling treats a completed manuscript as an output. This one can package a finished book back into the development workspace, where the developer persona reads the actual chapters — the prose, not a summary of it — and works through the next pass with you.

What it proposes comes back as a list of specific changes: this outline, that character's motivation, the house style. Nothing reaches the manuscript until you tick the ones you want. The prose itself is never rewritten from the plan — changing the words is a separate, deliberate re-draft, and only the chapters whose plan actually moved are redrafted. Every earlier version is kept, so a second pass is comparable against the first rather than replacing it.

From draft to something you can ship

When the manuscript is done it can be assembled and exported — the text together with the material a release needs, rather than a folder of chapter files you then have to stitch together yourself.

The point is not to generate a book in one pass. It is to make the hundred small passes tractable, and to keep the whole thing coherent while you do them.

Where this fits

Non-fiction built from your own research archive. Serial fiction with a consistent cast. Technical books where the facts must match the sources. Any long-form work where the difficulty is not producing words but keeping several hundred pages honest with each other.