The World-Building Consistency Bible: Turn Scattered Story Notes Into a Structured Canon Document
Why this prompt matters
Continuity errors are one of the most common reasons readers and players lose trust in long-form fiction — a character's stated age shifting, a travel time being violated two chapters later, a magic rule broken without explanation. Catching these before publication is far cheaper than fixing them after (errata, reader complaints, one-star reviews calling out plot holes). TV writers' rooms and major game studios pay dedicated continuity editors specifically for this function; this prompt gives an individual novelist or indie studio the same safety net without the headcount.
What we use it for
You are 8 months into drafting a fantasy novel — or a game's narrative bible — across chapter drafts, a Discord brainstorming log with beta readers, sticky notes, and a half-finished spreadsheet of character ages. You are about to start the next book or the next act and need one reliable reference before you keep writing, but you no longer remember every detail you established months ago.
Prompt
Role: Act as a meticulous continuity editor and story bible archivist for [GENRE, e.g. epic fantasy / sci-fi RPG / serialized web fiction]. Context: I have been developing a fictional world across scattered, disorganized notes — chapter drafts, brainstorming logs, character sheets, and worldbuilding fragments written at different times without a master reference. I need these consolidated into a single reliable canon document before I continue writing. Here are my scattered notes, in no particular order: [PASTE ALL YOUR NOTES, DRAFT EXCERPTS, CHAT LOGS, OR OUTLINE FRAGMENTS HERE — as much as you have, unedited] Known fixed facts I want you to treat as ground truth even if notes conflict with them: [LIST ANY FACTS YOU'RE CERTAIN ABOUT, e.g. "The capital city is named Veyrith" — leave blank if none] Task: Read through all of the notes and produce a structured canon document with these sections: 1. Characters — for each named character: their established traits, motivations, relationships, and current status as of the latest note that mentions them. 2. Timeline — every event mentioned, placed in chronological order as best you can determine, noting your confidence level for any ordering you had to infer. 3. Locations and Setting Rules — every named place and any established rules of geography, technology, or magic/science that governs the world. 4. Established Facts — a running list of concrete facts stated directly in the notes (names, numbers, dates, specific claims). 5. Contradictions and Open Questions — anything where two notes conflict with each other, or where a detail is referenced but never actually defined. Constraints: Do not invent any fact, name, or detail that isn't stated or clearly implied in the notes — if something is unclear, put it in the Open Questions section instead of guessing. When you find a contradiction, quote or closely paraphrase both conflicting mentions so I can see exactly where the disagreement is. Do not smooth over inconsistencies to make the world seem more coherent than the notes actually show. Output Format: Markdown with an H2 heading for each of the five sections above. Use bullet points within each section. End with a numbered list under "Contradictions and Open Questions" so each item is easy to reference when I follow up.
Result
Characters
- Kessa Vane — Former royal cartographer, now exiled. Motivation: reclaim her seat on the Cartographers' Guild by proving the eastern maps were falsified. Relationship: distrustful of her former apprentice, Thom, who she believes reported her to the Guild (stated in Chapter 3 draft, reaffirmed in your Aug 2 brainstorming log). Current status: last seen heading toward the Salt Coast at the end of Chapter 4.
- Thom Ellery — Apprentice-turned-Guild-cartographer. Your notes describe him as "loyal to Kessa" in the character sheet from early notes, but the Chapter 3 draft has Kessa accusing him of betrayal — this is flagged below as a contradiction, since the notes never confirm whether he actually reported her.
Timeline
- The Falsified Maps Incident (referenced but undated — inferred to occur roughly 8 years before the story's present, based on Kessa's stated age at the time versus her current age).
- Kessa's exile (follows the incident by an unspecified gap — your notes say "years later" without a number).
- Chapter 1–4 events (present-day story timeline, spans roughly 3 weeks per travel-time references).
Locations and Setting Rules
- Veyrith — the capital, seat of the Cartographers' Guild. Confirmed as a coastal city (Chapter 2 mentions harbor traffic).
- The Salt Coast — mentioned twice, but never given a firm travel time from Veyrith; Chapter 1 implies a two-day journey, your Aug 2 log implies a week. Flagged below.
- Magic system rule — cartographic magic requires physical ink made from a specific mineral ("starsalt") found only near the Salt Coast, per your worldbuilding fragment. No notes yet establish how much starsalt is needed per map or what happens if it runs out.
Established Facts
- The Guild has 12 seats, per your character sheet.
- Kessa is stated as 34 years old in the present day.
- Starsalt ink is described as "faintly blue when wet" in two separate notes, consistently.
Contradictions and Open Questions
- Thom's loyalty: Character sheet calls him "loyal to Kessa," but Chapter 3 has Kessa directly accusing him of betrayal. Neither note confirms which is accurate as of the story's present — needs a decision.
- Salt Coast travel time: Chapter 1 implies 2 days from Veyrith; Aug 2 brainstorming log says a week. These can't both be true — pick one and I'll flag any future note that contradicts it.
- Starsalt supply limits: The magic system's core constraint (starsalt availability) is referenced as important but never quantified anywhere in your notes — this is a worldbuilding gap, not a contradiction, but it's worth resolving before it matters in the plot.
Every long-form fiction or game project eventually accumulates the same problem: months of notes scattered across chapter drafts, brainstorming chats, character sheets, and sticky notes, with no single reliable reference for what's actually been established. By the time a writer starts book two or a design team starts the next content update, nobody fully remembers what they decided about a character's age, a magic system's limits, or how long a journey between two cities is supposed to take.
Why This Prompt Is Structured the Way It Is
The prompt opens with a Role instruction — "continuity editor and story bible archivist" — rather than a generic writing assistant, because continuity work requires a specific mindset: skepticism toward the material rather than enthusiasm for it. A model primed to be a helpful creative collaborator will often smooth over gaps and fill in plausible-sounding details. A model primed as a continuity editor is more likely to flag what it doesn't know rather than invent it.
The Context section asks for raw, unedited notes rather than a cleaned-up summary, because the whole point is catching contradictions that exist in the source material — summarizing first would let the writer accidentally resolve the conflict themselves before the model ever sees it.
The five-part Task structure (Characters, Timeline, Locations and Setting Rules, Established Facts, Contradictions and Open Questions) mirrors what professional continuity editors in television writers' rooms actually track. The Contradictions section is deliberately last and deliberately its own numbered list — separating "here's what we know" from "here's what conflicts" makes the output far more actionable than a single narrative summary that quietly picks one version of the truth.
The Constraint That Makes This Actually Useful
The single most important line in this prompt is the instruction not to invent facts and to flag ambiguity as an open question rather than guessing. Without that constraint, most models will confidently fill continuity gaps with plausible-sounding inventions — which is worse than leaving the gap visible, because an invented detail can get treated as established canon by mistake. Explicitly asking the model to quote or paraphrase both sides of a contradiction, rather than just noting that one exists, makes the output something a writer can actually act on without re-reading all their original notes to find the conflict themselves.
How to Adapt It
For a game studio's shared narrative bible, add a line asking the model to tag each fact with which note or document it came from, so a writers' room can trace provenance. For a serialized web fiction project publishing chapter by chapter, run this prompt after every 5–10 chapters rather than waiting 8 months — smaller, more frequent runs catch contradictions while they're still cheap to fix. If your notes exceed what fits in one context window, split by category (characters and relationships in one pass, timeline and setting rules in a second) rather than truncating — losing early notes to a length limit defeats the entire purpose.