Writing bible / codex

Definition

The codex is the author's external memory: everything the text demands remembering but the brain forgets between writing sessions. It can be a wiki, spreadsheet, notebook, Notion folder, or relationship graph — the tool matters less than systematic updating after each narrative decision. Unlike published lore (fan wikis, appendices), the writing bible also holds private notes: planned arcs, unrevealed secrets, contradictions to resolve.

What it's for

It guarantees Internal coherence over time — especially in series, collaboration, or after a months-long pause. Each character sheet, magic rule, and recorded date becomes a checkpoint during Active rereading. A well-kept codex also feeds Narrative knowledge graph tools: entities named in text attach to verifiable sheets. The test: if you write book 4 tomorrow, can you find the protagonist's age in book 1 within five minutes?

Variants by genre

• Fantasy: magic bible (costs, limits, exceptions), genealogies, maps, languages; often the core of Worldbuilding.
• SF: technology bible and future timeline; strict distinction between established novum and working hypothesis.
• Crime: factual bible (procedures, investigation calendar, alibis, crime chronology) to avoid Plot hole.
• Multi-author IP: normative bible imposed on all contributors; versioning mandatory.
• Standalone: minimal codex — main character sheets, story timeline, frame rules.

Common pitfalls

• Writing an encyclopedic bible before the first scene: procrastination in disguise.
• Never updating: the bible becomes false and dangerous.
• Over-confidence: the codex doesn't replace rereading — it guides the coherence pass.
• Too much formality: an unusable daily bible is abandoned in two weeks.
• Duplicating the full novel text in the codex: note stable essentials, not every sentence.
• Forgetting to date entries: impossible to know which lore version is authoritative.

Examples

• Brandon Sanderson — Cosmere managed by a living cross-series bible (magic, planets, crossovers).
• Patrick Rothfuss — incomplete bible cited as factor in Wise Man's Fear delays.
• Tolkien — appendices and Silmarillion as externalized Middle-earth codex.
• Marvel / DC — IP bibles imposed on comics and film writers.
• George R. R. Martin — character sheets and timelines for A Song of Ice and Fire.
• Television (Breaking Bad, The Wire) — standard series bibles in writers' rooms.

Writing tips

• Write the bible after the first draft, except for structural essentials. A pre-manuscript bible tends to become a parallel project that delays actual writing.
• Cap each sheet at one page: name, role, want, wound, arc, 3 hard facts. Beyond that, sheets become unreadable and never consulted on revision.
• Split locked canon from unstable zones: locked facts (birth dates, magic, geography) on one side; working hypotheses clearly flagged on the other.
• Update the bible at the end of each chapter rather than at the end of the book. Massive retroactive updates always let contradictions through.

Learn more: Complete guide to novel coherence at 100,000 words and The end of manual codex configuration.

Revision checklist

• Does each major rule (magic, tech, law) have a sheet with limits and costs?
• Are story dates aligned with internal chronology?
• Was the bible updated after the last structural revision?
• Are unrevealed secrets flagged so they don't leak by mistake?
• Could a new reader (beta or co-author) orient themselves in under ten minutes?