How to Build a Story Bible

Why a story bible matters for AI fiction

An AI model has no memory of your book between turns. Left to its own devices, it will invent a capital city, forget it named the capital something else last week, and present both as fact. A story bible ends that drift by making one document the arbiter of truth. Drafting consults it; revision audits against it.

The payoff is not just consistency. A good bible also makes the AI more creative within bounds — because it knows the rules, it can bend them deliberately instead of breaking them by accident. If you are new to long-form AI writing, pair this with our novel-with-AI workflow, which treats the bible as the spine of the whole process.

The 12 categories your story bible should hold

1. Metadata

Title, working subtitle, genre, target length, point of view, tense, and the one-sentence premise. This is the header that keeps every scene aimed at the same book. Include your narrative promise — what the reader is owed by the end.

2. World

The setting's hard facts: geography, technology level, magic or science system and its limits, politics, economy, and culture. Write rules, not flavor. "Magic requires a blood price" is bible-worthy; "it feels spooky" is not.

3. Characters

One entry per significant character: fixed traits, backstory, voice, motivation, and arc goal. Keep this distinct from their changing emotional state (see category 9). The character sheet is who they are; the state is how they feel right now.

4. Relationships

How every pair of characters regards each other, with a short note on history. Relationships are the connective tissue of a long book and the easiest thing for an AI to corrupt, so name them explicitly: rivals, secret half-siblings, betrayed friends.

5. Timeline

Absolute and relative dates of key events, both in-world and in the character's personal history. A timeline prevents the classic error of a character referencing an event that has not happened yet, or mourning someone still alive.

6. Plot threads

Each ongoing thread: its status (open, seeded, resolved), what it needs to pay off, and where it was last advanced. Threads are how you track subplots across a hundred chapters without losing any.

7. Foreshadowing

Every planted clue and its intended payoff chapter. Foreshadowing is worthless if you forget to land it; the bible is where you promise yourself the payoff and check it off when written.

8. Chapter summaries

A one- or two-line summary of each finished chapter: who was there, what changed, and the exit state. These are the context you hand the model when drafting the next scene, far cheaper than re-feeding the whole manuscript.

9. Character states

The current 0–100 values for each character's trust, love, anger, fear, and any story-specific axes. Update these every chapter. They are the numerical heartbeat that keeps relationships evolving for reasons, not at random. See our character consistency guide for the full method.

10. Style guide

Your prose rules: POV tightness, banned words, sentence-length rhythm, tone, and any voice notes ("protagonist thinks in short, bitter sentences"). The style guide is what stops each chapter from sounding like a different author.

11. Forbidden facts

The hard "never" list: facts that must never be contradicted. Examples: the queen is sterile, the north gate burned in year three, the protagonist is allergic to shellfish. When in doubt, put it here — forbidden facts are the cheapest insurance against a continuity disaster.

12. Open questions

Unresolved threads and decisions still pending, so nothing silently drops. This is your parking lot for "did we ever explain the crypt?" — answer it or plant it, but never lose it.

A JSON story bible template

A structured file beats a wall of prose because you can paste exact sections into a prompt. Here is a minimal, copy-paste starting point:

{
  "metadata": {
    "title": "The Tideward Crown",
    "genre": "gaslamp fantasy",
    "pov": "third-limited",
    "premise": "A cartographer must map a coast that rewrites itself each tide."
  },
  "world": {
    "magic": "Tide-craft requires a physical map and a blood mark.",
    "limits": "No spell crosses the salt line at full moon."
  },
  "characters": {
    "mara": {
      "role": "protagonist",
      "traits": ["precise", "grieving", "stubborn"],
      "motivation": "find her brother lost to a rewriting cove"
    }
  },
  "forbidden_facts": [
    "Mara's brother vanished in year 9, not year 8.",
    "The salt line cannot be crossed at full moon."
  ],
  "character_states": {
    "mara": { "trust": 40, "love": 55, "anger": 30, "fear": 70 }
  },
  "open_questions": [
    "Who maintains the lighthouse that never goes dark?"
  ]
}

You can expand each section as the book grows. The point is not the format — it is that the truth lives in one place you actually open.

How to keep the bible alive

A bible is a living document, not a pre-writing chore. Update it at the end of every writing session: new facts go in, resolved threads move to done, character states get their new numbers. If you only write the bible once and never touch it, it rots and the AI ignores it. A practical habit is to keep the bible file open in a second window beside your draft, so recording a new fact takes seconds and never gets deferred to "later" — which in practice means never. The writers who benefit most are the ones who treat the bible as part of the writing itself, not a separate administrative task they owe their future self.

Tools like Glint's AI story generator can ingest a bible and keep relevant slices in context as you draft, which removes the manual copy-paste tax. The broader landscape of AI tools for fiction writers in 2026 is worth a scan if you want to automate more of the memory work.

Common bible mistakes

Mistake	Consequence	Fix
Writing it once and abandoning it	Rotting reference nobody trusts	Update at end of every session
Storing flavor instead of facts	Nothing enforceable	Record rules and fixed data, not mood
Feeding the whole bible every prompt	Model loses focus	Send only the relevant slices per scene
No forbidden-facts list	Canon contradictions slip through	Maintain an explicit "never" list
Keeping it in your head	Drift by chapter ten	Externalize it to a file you open

Auditing against the bible in revision

The bible earns its keep during revision. With a draft complete, read it scene by scene with the bible open beside you and check four things: did any character act against a forbidden fact, did any world rule get quietly broken, did every foreshadowed clue reach its payoff, and do the chapter-exit states match the next chapter's entry states? Most long-book inconsistencies are caught here in an afternoon, whereas finding them after publication costs readers' trust.

Keep a running "continuity log" during this pass: each discrepancy, where it appeared, and the fix. If the same type of error repeats — say, the model keeps forgetting a character's injury — add it to the forbidden-facts list so future drafts avoid it automatically. The bible is not static reference data; it is a feedback loop that gets stricter the more you write.

Scaling the bible to a series

A single novel bible is manageable; a five-book series is where the system proves itself. For a series, add a layer above the book-level bible: cross-book timeline, unresolved threads that deliberately carry over, and character states that persist across volumes. The same 0–100 model works, but now a character can enter book three still angry about book one — and the bible remembers why when the model does not. Authors who plan a series from the start save themselves the painful retrofitting of continuity that late planners face.

Frequently asked questions

What is a story bible used for? It is the single source of truth for your book — world rules, characters, timeline, and forbidden facts. You consult it while drafting and audit against it in revision so the AI stops inventing contradictions.

How is a story bible different from an outline? An outline is the sequence of events; a story bible is the reference data those events must obey. The outline says what happens, the bible says what is true.

Do I need a story bible for a short story? Not really. The bible pays off once a story is long enough that you cannot hold every fact in your head — novels, serials, and series benefit most.

Should the AI see the whole bible every time? No. Feed the model only the categories relevant to the scene you are drafting — the character sheet, the relevant world rules, the active plot thread. Smaller, relevant context beats one giant dump.

What format should a story bible be in? Anything you will actually maintain. A structured JSON or Markdown file is ideal because tools can parse it and you can paste exact sections into prompts without retyping.