Quick definition
A story bible written for a single delivery format usually has its format's assumptions baked invisibly into its canon — and those assumptions are exactly what breaks the moment the same IP needs to become a second format. The fix isn't writing two bibles. It's building one narrative engine and documenting, explicitly, what has to stay fixed for the world to hold and what's actually free to flex when the format changes.
In one line: Figure out what must stay fixed for a story to succeed, and what can flex without breaking — that's the whole job.
Fixed layer vs. flexible layer
| Fixed — travels unchanged | Flexible — adapts per format |
|---|---|
| Canon events and their consequences | The order and method the audience learns about them |
| Character cores — want, fear, the lie they carry | How much of that arc is scripted versus generated through player choice |
| Tone and the emotional target | Pacing — a scripted beat's timing versus a player-paced discovery |
| The central conflict and what's actually at stake | Degree of agency — full script, guided choice, or open emergence |
| World logic and faction rules | Delivery mechanism — dialogue, environmental detail, mechanics, or UI |
Run every entry in the bible through one test: does this depend on the audience experiencing it in a fixed order, or through a specific medium? If yes, it belongs in the fixed layer and needs to be format-agnostic in how it's written. If no, it's genuinely flexible, and the bible should document the range it's allowed to flex within — not just leave it undefined.
This is a cross-disciplinary document, not a solo one
A bible built to survive format changes has to be usable by people who aren't writers — designers building the systems that carry the flexible layer, audio specialists shaping tone through sound instead of dialogue, technical teams implementing the world logic as actual rules. The bible's job is protecting narrative intent across all of those disciplines without requiring every contributor to be a narrative expert themselves. If only the writer can correctly interpret an entry, that entry isn't finished yet.
The real stress test
A working world bible is the one collaborators actually open and use, not the one that reads well and gets ignored. Building the same IP into a second format is one of the most honest tests of that distinction available: a fixed-layer entry that turns out to secretly depend on a scripted cutscene, or a flexible-layer entry with no defined range, will surface immediately the moment someone else has to build the second format from the document alone, without asking the original writer to clarify it in person.
A checklist before calling the bible format-ready
- Can someone outside the writers' room build the flexible layer correctly using only this document?
- Does every fixed-layer entry avoid assuming a specific delivery mechanism?
- Is the acceptable range of the flexible layer actually written down, not just implied?
- Would the central conflict and character cores survive being learned in a completely different order?
- If this had to become a third format tomorrow, is it obvious which parts would need to change?
Source note
This reference page is adapted from Jesse Alexander's teaching statement for narrative design and interactive storytelling coursework — a professional teaching document rather than a dated Substack essay. It's presented here in the same durable, citeable format as the site's other craft references.
Related pages
- How to Build a Story-World Bible That Generates Stories — the single-format version of this same working-document discipline.
- Environmental Storytelling and World Logic: Narrative Without a Script — the fixed-layer world logic this bible has to document clearly enough for a design team to build from.
- A Screenwriter's Development Pipeline: From Concept to Market-Ready Draft — where a format-ready bible fits inside the larger path from concept to a sellable package.
About the author
Jesse Alexander is a screenwriter, showrunner, and narrative designer whose work spans film, television, games, and transmedia storytelling. Scribbler’s Toolbox collects practical frameworks developed from professional story development and production.