Quick definition
A story-world bible is a maintained development document that defines a property's creative promise, governing rules, social systems, factions, resources, locations, character roles, canon, and recurring conflict engine so multiple stories and collaborators can operate inside the same coherent sandbox.
In one line: document the rules and pressures that generate stories—not every fact that could exist.
A bible is an operating system, not an encyclopedia
Worldbuilding often begins with pleasure: maps, histories, technologies, family trees, costumes, currencies, languages, artifacts, and lore. Those materials can deepen a world. They do not automatically make it dramatic. A thousand years of fictional history may produce less usable story than one rule that forces two people to compete for the same resource.
The world bible has a practical job. It should help a writer or collaborator answer four questions:
- What experience does this property reliably promise?
- What can and cannot happen here?
- What recurring pressures force people to choose?
- How can a new story expand the world without breaking its identity?
If a section cannot clarify a choice, inspire a conflict, prevent a contradiction, or open a useful story possibility, it may belong in the archive rather than the working bible.
World bible, series bible, pitch deck, and lore archive
| Document | Primary audience | Primary job |
|---|---|---|
| Story-world bible | Writers, designers, producers, and creative partners | Define the world's operating rules and reusable dramatic possibilities. |
| Series bible | Buyers, producers, and a television team | Explain the show, characters, pilot, season engine, and future episode potential. |
| Pitch deck | A specific decision-maker | Create fast emotional, visual, and market understanding. |
| Lore archive | Continuity keepers and deep collaborators | Store exhaustive facts, sources, versions, timelines, and references. |
One project may use all four. Do not force one document to perform every job. The pitch deck should invite. The working bible should guide. The archive should remember.
The story-world system at a glance
| Layer | What it captures | What it should generate |
|---|---|---|
| Creative promise | Genre, tone, audience experience, theme, and distinction | A shared standard for what belongs |
| Rules and costs | Capabilities, limits, prohibitions, consequences, and exceptions | Hard choices instead of convenient solutions |
| Systems and factions | Institutions, beliefs, hierarchies, alliances, and rivalries | Conflict larger than one villain |
| Resources and scarcity | What people need, control, exchange, steal, protect, or worship | Competition, leverage, and moral compromise |
| Places and routes | Dramatic locations, borders, distances, access, and hazards | Movement, collision, and geographic consequence |
| Character roles | Who thrives, suffers, enforces, rebels, translates, or profits | People shaped differently by the same world |
| Information design | Common knowledge, secrets, mysteries, lies, and forbidden truths | Discovery, suspense, and rolling reveals |
| Story engine | The repeatable pursuit, pressure, and reset or progression pattern | Episodes, missions, sequels, campaigns, or expansions |
| Canon and boundaries | What is fixed, flexible, disputed, provisional, or deliberately unknown | Coherent collaboration without creative paralysis |
1. State the creative promise first
Before documenting the machinery, define the experience the machinery exists to create. Include:
- Format and genre: what kind of story container is this?
- Audience experience: what should people repeatedly feel or do?
- Tonal range: what emotional frequencies belong, and what would break the pact?
- Thematic tension: which opposing values will the world keep testing?
- Stand-out factor: what makes this sandbox different from adjacent properties?
A usable promise is active. “A science-fiction universe about memory” names a subject. “Every story forces someone to trade a memory for access, power, or survival” begins to define a dramatic system.
2. Write rules as pressure, cost, and consequence
A rule becomes dramatically useful when it has three parts:
Capability + Limitation + Cost
If people can read minds, ask what blocks the ability, what using it damages, who regulates it, and what people do to conceal themselves. If clean energy becomes abundant, ask which old industries collapse, who controls distribution, what new scarcity replaces fuel, and which communities refuse the system.
For every major rule, record:
- What it permits
- What it forbids
- Who understands it
- Who benefits from it
- Who pays for it
- What happens when it is broken
- Whether any exception is established, rumored, or impossible
Limits generate ingenuity. Costs generate character. Consequences generate the next story.
3. Build systems and factions around incompatible wants
A world feels alive when its institutions and communities want different futures. Do not define a faction only by costume, territory, or moral label. Give it an operating position:
- What does it want to preserve or change?
- What resource or authority does it control?
- What story does it tell about itself?
- What contradiction does it refuse to see?
- What tactic does it consider legitimate that another faction rejects?
The strongest faction map produces conflict without requiring anyone to wake up evil. A bureaucracy can sincerely protect safety while destroying freedom. A rebel movement can pursue justice while making daily life less stable. The disagreement becomes structural and renewable.
4. Track resources, scarcity, and exchange
Ask what the world treats as scarce. The answer may be water, fuel, land, time, memory, magical ability, legal status, privacy, attention, safety, belonging, or reliable information. Then map the flow:
- Who produces or discovers it?
- Who controls access?
- Who distributes it?
- Who is excluded?
- What is the legal price?
- What is the hidden human cost?
- What black market or alternative system emerges?
Scarcity turns abstract lore into behavior. It explains why borders matter, why factions collide, what professions exist, what crimes are profitable, and what an ordinary person must do before breakfast.
5. Define places by what they make people do
For each important location, document more than appearance. Record access, authority, danger, ritual, information, social expectation, and the behavior the place rewards. A palace, hospital, starship, school, neighborhood, or virtual lobby should change the tactics available to a character.
Connect locations through routes and thresholds. Who can cross? What must be paid, hidden, proven, or surrendered? Travel time and access rules create consequence. When every location is instantly available, geography becomes decoration.
6. Create character roles before filling the cast
A world bible need not invent every future character. It should identify the kinds of people the system produces:
- The person who enforces the rule
- The person excluded by it
- The person who profits from the loophole
- The believer who treats the system as sacred
- The translator who moves between factions
- The ordinary worker who absorbs the hidden cost
- The newcomer whose confusion gives the audience an on-ramp
Then make individual characters specific through WANT, voice, fear, relationships, and contradiction. The role connects a person to the world; it should never replace personality.
7. Design the information architecture
Separate what exists in the world from what the audience knows. Label information as:
- Common knowledge: facts ordinary people use without explanation
- Specialist knowledge: information controlled by a profession, class, or faction
- Secret: a known truth someone actively conceals
- Mystery: a question whose answer has not yet been established or revealed
- Lie: false information circulated for a purpose
- Unknown: deliberate negative space that preserves future possibility
This prevents two common failures: characters explaining facts everyone should already know, and writers confusing an unanswered question with a secret that has a designed answer. Reveal the world through consequence, need, and discovery instead of frontloading a lecture.
8. Write the repeatable story engine as a sentence
A story engine describes how the world repeatedly turns pressure into narrative. A practical form is:
Role + Recurring Task + Source of Opposition + Cost of Success + Change Across Cycles
For example: “A team of memory couriers enters protected minds to recover evidence, while the institutions hiring them erase the couriers' own pasts; every mission solves a case and makes the team less certain who they were.”
The sentence identifies episodic motion and cumulative change. Test it by generating ten one-line stories. If the examples differ only in cosmetic details, the engine is too narrow. If they share no recognizable dramatic pleasure, it is too loose.
9. Manage canon in tiers
Not every note deserves equal authority. Use clear states:
| Canon state | Meaning | Creative treatment |
|---|---|---|
| Fixed | Established on-screen, published, or contractually essential | Do not contradict without an explicit story event or authorized retcon. |
| Working | The current room answer | Use for development; update when stronger choices replace it. |
| Disputed | Different in-world accounts or conflicting legacy material | Preserve the disagreement and define who believes what. |
| Provisional | A possibility under exploration | Do not let collaborators treat it as a locked dependency. |
| Open | Intentionally unanswered | Protect the negative space until a story earns the answer. |
Record the source and date of consequential decisions. When a rule changes, note what downstream characters, plots, assets, departments, or platforms it affects. The goal is not lore policing for its own sake. It is preventing one team's clever addition from silently breaking another team's story.
Build the minimum viable bible first
Before producing a beautiful hundred-page document, make a version small enough to test. A minimum viable story-world bible can contain:
- One-page creative promise
- Ten governing rules with costs and consequences
- A faction map with opposing wants and controlled resources
- Five story-generating locations and their thresholds
- Six character roles the system naturally produces
- A knowledge map: common, specialist, secret, mystery, lie, and open
- One story-engine sentence plus ten example stories
- A canon ledger showing fixed, working, disputed, provisional, and open material
Give this version to a collaborator with one instruction: pitch three stories you did not already discuss. Their questions and inventions are the test. If they can only repeat your examples, the sandbox is underpowered or overcontrolled. If their ideas immediately violate the promise, the guardrails are unclear.
Adapt the bible to the form
- Feature: prioritize the world rules, pressures, and details required for one complete dramatic experience. Preserve expansion space without weakening the ending.
- Television: make the weekly or serialized engine, character collision pattern, season escalation, and episode variety explicit.
- Game: distinguish authored lore from player action. Document verbs, progression, repeatable loops, systemic consequences, and where player freedom outranks a predetermined character arc.
- Transmedia property: define what each platform does uniquely, which canon crosses between them, how audiences enter, and whether participation creates recognition or consequence.
- Collaborative franchise: add ownership, approval paths, version history, source links, and a change-impact process so the document remains operational.
Common world-bible failures
- Lore before promise: the document contains history but no repeatable audience experience.
- Rules without costs: capabilities solve problems without creating new ones.
- Factions as costumes: groups look different but want nothing incompatible.
- No ordinary life: mythology is detailed, but nobody knows how work, food, status, law, or family function.
- Every mystery answered: exhaustive canon removes the space future stories need.
- Examples mistaken for limits: collaborators imitate existing stories instead of using the underlying engine.
- A frozen PDF: decisions change, but the official document does not.
- Continuity as control: protecting facts becomes more important than improving the story.
The story-world bible workflow
- State the creative promise, tonal range, and audience experience.
- Define capabilities through limitations, costs, and consequences.
- Map factions by wants, resources, self-image, and contradiction.
- Identify scarcity, exchange, access, and hidden cost.
- Build locations around behavior, authority, thresholds, and danger.
- List character roles the system naturally produces.
- Separate common knowledge, specialist knowledge, secrets, mysteries, lies, and unknowns.
- Write the story-engine sentence and generate ten distinct examples.
- Assign canon states and record consequential sources and changes.
- Hand the minimum viable bible to collaborators and revise from what they try to build.
The world-bible diagnostic
- What recurring experience does this world promise?
- Which rule creates the most difficult choices?
- What does power cost here?
- Which factions want incompatible futures, and why do both believe they are right?
- What scarce resource organizes behavior?
- Which locations change the tactics available to a character?
- What does an ordinary person know, fear, need, and misunderstand?
- Can the engine generate ten different stories without abandoning the promise?
- Which facts are fixed, flexible, disputed, or intentionally open?
- Can a collaborator invent something surprising that still unmistakably belongs?
Diagnose the character who opens the door
Scribbler’s Character Doctor
A world becomes emotionally legible through a person. Use Character Doctor to test whether the anchor character has a playable WANT, meaningful opposition, a distinct voice, a worldview shaped by the setting, and a dramatic function inside the larger engine.
Diagnose the anchor character →
Source note
This maintained reference page synthesizes ideas first developed in “I Am Nerd! Creator of Worlds!” on November 6, 2023, “World Building Bureaucracies!” on April 25, 2024, “Scribblers Pipeline” on April 7, 2025, “Could AI Tools Keep the Multiverse From Breaking Canon?” on October 31, 2025, and “The Forever IP Test” on January 29, 2026. This version organizes those archive ideas into a working story-world bible method.
Related pages
- IP & Worldbuilding Learning Path — place the bible between the story-generating location and the enduring characters who inhabit it.
- Build a Story Location That Generates Its Own Drama — develop rules, atmosphere, politics, and information at the location scale.
- Create Characters That Endure — give the world durable figures with mythic cores, rituals, and genre flexibility.
- The Forever IP Test — test whether the system creates trust, repeatable pleasure, depth, community, and memory.
- Create Dramatic Conflict Without Simple Villains — generate opposition from environments, systems, internal struggle, and collaborative competition.
- A Screenwriter's Development Pipeline — connect the bible to concept, characters, outline, draft, feedback, and market materials.
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.