AI Story Bible — Facts That Build Themselves

An AI story bible is a story bible drafted from your own text: the AI reads your manuscript, extracts characters, locations, events, and world rules, and organizes them so you can review them as the draft evolves. PlotLens is an AI story bible that never generates prose — it extracts your Story Bible from what you actually wrote, cites the source sentence for the facts it records when a clean span is available, and checks new writing against the facts you accept.

Your Story Bible is the set of facts your story has established — what readers call canon.

Most “AI writing tools” want to write for you. PlotLens is different — it reads what you’ve written and builds intelligence around it. Your story bible is generated from your actual manuscript, not from templates or prompts. The AI extracts what matters and keeps it organized as your story evolves.

What “AI story bible” should actually mean

The phrase gets used two different ways and the difference matters. One interpretation is “an AI tool that helps you write the story bible” — a chat interface where you describe your characters and the model fleshes them out. The other is “a story bible that builds itself from the text you’ve already written.” The first one is a more elaborate version of the form-builder bibles that have existed for a decade; you’re still typing the Story Bible into a tool, just with a chatbot in the loop. The second one is a category shift: the manuscript is the source of truth and the bible is a derived view over it.

PlotLens is the second kind. We don’t have a chat-with-your-bible interface where you tell the model “make Anna more brooding” and the model decides what that means. The AI work happens in extraction and validation — reading your manuscript, recognizing entities, mapping relationships, comparing new content against your Story Bible. Your prose is the input. The bible is the output. Facts in the output link to the sentence in the input that established them when a clean span is available.

Why this matters for the writer

A bible you type into a tool is wrong the moment your manuscript diverges from it. You wrote that scene where Anna’s hair color shifted from black to dark brown? The bible still says black until you remember to go update it. You retconned the entire backstory of the antagonist in draft three? The bible still has the draft-one version. The maintenance burden compounds. Most writers stop updating their bibles around month two and then don’t quite trust the bible they have, which means the tool stopped being useful and started being a chore.

A bible that’s regenerated from the manuscript doesn’t have this problem. Change the scene, re-run extraction, and review the facts proposed from the new text. The trust posture is also cleaner: when the bible says Anna’s eyes are hazel, you can click through to the sentence in chapter four where you wrote it when a clean span is available. Items without a clean span are not shown as cited, and extraction can still miss or misread a passage, so review what it proposes.

How PlotLens uses AI

The AI work in PlotLens is constrained on purpose. Three jobs:

1. Extraction. Recognize the entities in your manuscript — characters, locations, events, objects, factions, world rules — and map their attributes, aliases, and relationships. This is the heavy lift. The model needs to understand fiction in particular: that “the captain” and “Halloran” are the same character three scenes apart, that “the ridge” and “Briarscar Ridge” are the same location, that a character’s dialogue is a different evidence type than a narrator’s description.
2. Manuscript Check. Compare new content against your Story Bible and flag sentences that contradict it. A character’s eyes are described as green in chapter eighteen when chapter four said hazel. A passage appears to reverse an event order you recorded as a fact. A character knows something they haven’t been told.
3. Surfacing. Build the queryable bible — search by character, by location, by event, by relationship; jump from a cited fact to its source sentence; export reports for editors, agents, or co-writers.

What the AI doesn’t do: write your prose, suggest scenes, generate dialogue, or produce paraphrased summaries of your work. Extraction is designed to record only what the manuscript states, and you review each proposed fact. The category boundary is precise — analysis, not generation. The category page defines narrative intelligence, and the longer explainer is What is Narrative Intelligence?. If you want the category without the “AI” framing, our story bible software page covers the same product from that angle.

What you do with the AI bible

A novelist drafting book three reads the bible like a reference document. “What did I establish about the magic system in book one chapter eleven?” Search the bible, click a cited fact, land on the passage. “Has Anna ever met Lewis?” Query the relationship graph. “Which scenes mention the Hollow?” Filter by location. The bible is not a thing you maintain. It’s a thing you query.

The validation flow is the other half. When you write a new chapter — in Word through the add-in, in Scrivener through the Companion app (beta), or in Google Docs or Final Draft by exporting to .docx, .fdx, or .fountain and uploading directly (the Google Docs add-on is not yet in the Google Workspace Marketplace, and Companion watching for Final Draft is coming soon) — a check you run compares the new sentences against the facts you accepted and flags possible inconsistencies. “Chapter eighteen describes Anna’s eyes as green; chapter four said hazel.” You decide what to do: fix the contradiction, accept the new fact, or make the change deliberate (sometimes a character is supposed to lie about an eye color in dialogue, and PlotLens can separate character belief from narrative fact when the text gives enough evidence, which helps reduce false alarms on intentional misdirection).

For writers’ rooms on team plans the same flow works at team scale: writers check drafts against the shared Story Bible, changes are attributed to the writer who made them, and possible contradictions can be surfaced before scripts hit the table read.

Is this the same as ChatGPT plus my manuscript in the context window?

No. A chat interface with your manuscript loaded into the context window can answer questions about your story, but it can’t build the structured bible — it can paraphrase from the text, but it doesn’t leave you a stored bible whose entries carry sentence-level citations, it doesn’t model relationships as typed edges in a graph, and it can’t validate a new chapter against the rest of the manuscript with inline annotations. A chat is a conversation; PlotLens is infrastructure. They serve different jobs.

Will the AI hallucinate facts about my story?

This is the right question. The main guard is provenance: facts in your bible point to a sentence in your manuscript when a clean span is available. If the model thinks Anna grew up in Edinburgh but no sentence in the text supports that, the fact is not shown as cited. That guard does not make extraction error-free, so read each proposed fact against the passage before you accept it. The mechanism details are in our continuity checker writeup and on the provenance page.

What about my data — does the AI train on my manuscript?

No. Your manuscript is not used to train models. The processing happens against the deployed models for extraction and validation; we don’t keep your text in a training dataset. The trust posture matters here as much as the analytical posture — many writers (and their agents and editors) need to know their work isn’t being absorbed into a generative model, and PlotLens is built for that audience specifically.

What if I haven’t written the book yet?

The tool is most useful once you have at least a draft to extract from — that’s the source the bible is derived from. If you’re starting from a blank page, a chat-style brainstorming tool is more appropriate. Many writers use a generation tool to draft, then run PlotLens on the resulting manuscript for continuity validation. Compare PlotLens vs Sudowrite for that two-tool workflow.

Try the AI story bible on a manuscript you’ve already drafted — the free tier covers a single project so you can run extraction without committing. If you write novels, screenplays, or serialized game narrative, the same pattern applies: manuscript in, structured bible proposed, checks you run on the next chapter. See pricing for tier details, or compare us to Novelcrafter and World Anvil for the two closest adjacent options in the market today.