Write the Book First: The AI-Assisted Novel Framework

Unless you have written the physics down first, your AI assistant will happily bend your magic, technology, or power system to solve whatever scene problem is in front of it. In this module you turn your extraordinary element into checkable laws: a grounded definition, a closed capability list, and a cost ledger of 4-6 named textures with on-page symptoms. You walk away holding your Story-Physics Sheet as Canon Artifact #2, pressure-tested by a rotation drill on your own drafted pages.

Module 1 locked what your book IS; Module 2 locked how its extraordinary element behaves. This module locks how each chapter SOUNDS. A multi-POV novel where every chapter reads like the same narrator has quietly stopped being a multi-POV novel, and that failure (same-voice syndrome) is the signature failure of AI-assisted fiction. You walk away holding Canon Artifact #3: a four-line voice-lock card per POV, a one-line register lock per recurring voice, and a completed divergence-drill table proving that two of your locks produce two voices no reader could confuse.

Your invented terms are your book's most valuable asset and its most perishable one. An AI assistant with your canon contract in context will reach for them constantly, converting wonder into wallpaper at generation speed. In this module you attach a written number to every canon term, every atmospheric term, and every deliberate repetition, then learn the five rotation rules that tell you exactly what to do when a count comes back over. You walk away holding Canon Artifact #4, the Character/Term Budget Sheet, with before/after audit counts from your own chapter. Those counts are graded input for Quality Gate items 5, 12, and 18.

Modules 1 through 4 locked the static half of your canon contract; this module builds the moving parts. You'll learn the seven-beat machine that shapes every scene you hand an assistant, the escalation rule and gate that keep chapter one from becoming the endgame, and the Evidence Ladder that gives every section of your outline a rung. You walk away holding Canon Artifact #5. It is the sectioned outline and capstone-chapter beat sheet your Module 8 chapter will be drafted from.

Your chapter can obey every lock you've written since Module 1 and still fail on the finished page. The source project's Chapter 1 did exactly that, in five documented ways. This module teaches the five rules its revision earned, and every one follows the same three beats: the failure it exposed, the rule that now prevents it, and the mechanical test you run on your own pages. You walk away holding Canon Artifact #6, the Five-Rule Audit of your own outline and drafted chapter with real counts, and it feeds Quality Gate items 12-17, which you will run on every chapter you ever finish.

Modules 1-6 each handed you a law; this module hands you the instruments that enforce them. You assemble the 18-item Quality Gate with your own IP written into every item. That gate is the every-chapter yes/no checklist, and it is also the exact rubric your Module 8 capstone is graded against. You then push a real drafted chapter through the four-pass revision cadence, where passes 2 and 4 run on counts, not feelings. You walk away holding Canon Artifacts #7a and #7b: your personal gate and your revision-pass log, both required capstone grading inputs.

For seven modules you built parts. You have a premise lock, a physics sheet, voice cards, budgets, an outline, five revision-earned rules, and an 18-item gate. In this capstone you bolt them together and run the machine on your own book: one complete chapter drafted inside your canon contract, audited by the four-pass cadence, and passed through your own Quality Gate with evidence attached. You walk away holding Canon Artifact #8. It is the chapter plus a five-document evidence package, graded against your own gate, with its beat sheet locked as canon.

Your book is (or will be) done, and the question changes altitude: how does it ship? In this module you read a real publishing-decision record. The source project's novel was produced to press-ready form as two 6x9 KDP paperbacks at 302 and 352 pages. From that record you learn the two-sided skill of knowing exactly what the records prove and reasoning forward from the numbers they contain. You walk away holding Canon Artifact #9, your Publishing-Decision Sheet: your projected page count with the estimation method shown, a split/no-split call with numbered reasons, and every figure tagged RECORD, CURRENT, or DERIVED.

A manuscript that passed its craft gate is not yet a publishable book. This module turns the finished work into Canon Artifact #10, a KDP Publish Package: a defended split decision, real front matter, a 6x9 interior and cover brief, discoverability metadata, pricing math, an AI-content disclosure record, and an audio-route decision. The proof case is the real Manifest City production line: an operator-reported 88,000-word working manuscript whose retained final files total about 90,000 words, divided after Chapter 12 into 302-page and 352-page 6x9 volumes. You use the record without inventing a private rationale, then make every decision for your own book from evidence you can point to.

Ten modules ago you started locking canon; you now hold the complete contract, and if your capstone passed you also hold a chapter that cleared your own gate. This final module shows what that stack is worth off the page: every artifact you built seeds a twin document in AI film production, one blunt law governs the handoff (the book is source material; the film's vision lock plus deviations log is canon; canon wins conflicts), and adaptation readiness is a mechanical test, not a feeling. You walk away holding a one-page IP Handoff Map that covers all eleven artifact slots, carries an audited status per row, and ends in a written go/no-go note your map's own rows can defend.

You spent this course locking your book's canon so an AI assistant couldn't drift it. Audio production has exactly the same failure mode, just with sound instead of prose. This bonus module hands you the cure the source project ran for real: one designed voice per principal character, owned by a single ledger, protected by a version-bump law, a drift protocol, and a reconciliation habit whose committed drift log survived an actual deleted-asset audit. You walk away holding your Voice Ledger v01 as Canon Artifact #11, plus the four platform-policy questions to verify before you distribute; if you continue to Course A, this exact artifact is reused directly for film dialogue.