How to Build a Story Bible That AI Models Actually Follow
Large language models do not remember your novel. They predict the next token from what is in the prompt right now. A story bible is not worldbuilding cosplay—it is the minimum context you re-inject so chapter forty matches chapter four.
Keep it short and scannable
Target 800–1,200 words total for a mid-length novel. Longer bibles get truncated or ignored. Use bullets, not prose essays.
Character cards (3–5 lines each)
- Name + role — "Mira Voss, protagonist, disgraced cartographer"
- Want / fear — "Wants redemption; fears being forgotten"
- Voice — "Short sentences, avoids metaphors, swears when stressed"
- Secrets — "Forged the map that caused the border war"
World rules (hard constraints)
List facts the model must not violate: magic costs blood; FTL takes three weeks; the king is alive until act three. AI will invent convenient exceptions unless you forbid them explicitly.
Timeline anchor
One paragraph: where we are in the story when generating. "Day 12 of the expedition. Mira knows about the forged map; Jalen does not."
Paste strategy
Put the bible in system context or the first user message every session. In Entangled Text, use project story settings so it travels with each chapter job—do not rely on chat history.
STORY BIBLE (do not contradict):
[paste cards + rules]
CURRENT CHAPTER: 14 — "The Flood Gate"
SCENE GOAL: Mira confesses to Jalen; he refuses to believe her.
POV: Mira, close third, past tense.
DO NOT: introduce new named characters; resolve the confession in this scene.
Write the scene (~1,400 words).After generation, diff against the bible manually for the first few chapters until you trust the model.
Update the bible when the story changes
When a secret is revealed, move it from "Secrets" to "Known facts." Stale bibles cause more drift than no bible at all.
Related: character consistency workflow and the free series bible worksheet tool.
Try it yourself
Write your own book with AI — free, no credit card required.
Free · No credit card