How to write a book with AI without it reading like AI

You do not ask a model for a book. You build a spine first, a premise, a cast and a beat sheet, then generate against that spine one scene at a time, and edit every pass by hand. The models are good at prose and bad at memory, so the structure has to live outside the model in a document you control.

1. Build the spine before generating a word

   Premise, cast sheet with locked details, and a beat sheet. Every later prompt references this. Skipping it is why AI books drift and contradict themselves by chapter nine.

2. Generate one scene at a time, never a chapter

   A scene is small enough that the model holds the whole thing in view. Chapters are where continuity breaks appear.

3. Keep a facts ledger and update it after every scene

   Eye colour, who knows what, what time of day it is. The model will not remember, so the ledger is the memory and it goes into every prompt.

4. Edit for rhythm, not grammar

   AI prose is grammatically clean and rhythmically flat. Sentence length variance is what makes it read human, and it is the one thing you cannot delegate.

This is the workflow behind the books published under Kevin Gabeci, including Dead Internet and the Shadows of Ravenshore series. The toolkit is the same pipeline, written down.