Final assembly

When the chapters are all stacked, the last step is assembly. It’s the spot for gathering verified chapters into one file to complete the manuscript. book-studio does only this much. Submission and ebook upload are done by you.

1) Call for assembly

Once every chapter is marked finished, call for assembly. Assembly isn’t an automated step in the pipeline; it’s where you have the AI gather the chapters that passed into one file.

make the final assembly of this book

It stitches the chapters/ch{NN}_draft.md files that passed verification into one file, in the order of 04_chapter_outline.json. You can give the result a name like final/manuscript.md.

Normal screen: the assembled file path shows, and every chapter gathers into one file. Assembly only stitches the passing bodies together rather than rewriting chapters, so nothing changes content at this step.

2) Pre-assembly check

Before assembling, look at two things.

Missing chapters — whether the outline’s chapter list matches the finished chapters. If a chapter is missing, finish writing it before assembling.
The continuity review — if there are unresolved items left in a chapter’s chapters/ch{NN}_review.md, go back to Tier 3 and clean them up before assembling.

Assembly gathers chapters that cleared verification; it isn’t a substitute for verification. Assembling with unresolved items leaves them in the manuscript as is.

3) It doesn’t auto-publish

Even after a manuscript is assembled, it doesn’t go up to an external platform automatically. Submission sites, ebook platforms, and print intake are decided and run by you.

A book is expensive to undo once published. Publishing involves human judgment — contracts, copyright, editor discussions — so the principle blocks the AI from putting a finished version out on its own. Assembly is as far as the base goes, and beyond that is your domain.

4) Version backups

Remaking the assembly backs up the prior assembly. The prior version doesn’t disappear when you fix a chapter and reassemble. Together with per-chapter commit, the manuscript can be rolled back at both the chapter level and the assembled level.

5) On to the next book

Once you finish a book, its status is set to completed in books.json. Start the next book with “new book — with slug X.” The environment is already set up, so you skip step 1 and go straight to the book-identity spot of /start.

The spot for bringing base updates into your work is in staying-up-to-date.