What a story bible is actually for

Before the final revision of Dreamscape Code we stopped writing and built a story bible: every character, rule, place and date, each one with the page number where the book states it. The rule was that nothing could go in unless it was on the page. Where the manuscript was silent, the document said so. Where it contradicted itself, the document said that too.

That second half is the useful part. A story bible that quietly fills in gaps flatters the draft. One that records them gives you a list you can work from.

What the list looked like

Twelve promises the book made and had not kept. Six places where the geography moved between chapters. A character amazed by something she had already watched happen. A protagonist described as "the one" and "our anchor" by people who never explain what either phrase means.

None of that is a disaster. Every draft has a version of it, and most of it is invisible to the writer, who has been holding the whole book in their head for a year and can no longer tell what is on the page from what is in their intention.

Why it changes the revision

Once the gaps are written down with page numbers beside them, revision stops being a matter of taste and becomes a matter of bookkeeping. You are no longer asking whether the book feels right. You are working through a list of specific, checkable claims, deciding for each one whether to pay it off, cut the setup, or leave it deliberately open.

It also settles arguments. When a new scene has to be written, the question "would she do that?" has an address: page 47, where she already did something like it, or nowhere, in which case the scene is inventing a character trait and everyone should know that is what is happening.

We build one for every book we take on, and we hand it over at the end. It outlives the edit: the next book in a series starts from it, and so does the person who has to write the jacket copy.