Lore bible examples from published fantasy

The question is rarely "should I keep a bible?" — by the time a series has drifted, the writer already has notes. The useful question is what a working reference looks like at scale. Four published cases, four different shapes, and a common core.

Tolkien: the bible outlives the author

The clearest published example of a world kept as a document. Tolkien worked on the legendarium for decades, and the two published novels are a slice of a much larger body of notes — histories, genealogies, maps, languages — later collected as The History of Middle-earth. He kept revising: names, dates and lineages changed between drafts, because the world was being written and rewritten at the same time.

The lesson is not "write more notes". It is that a world's history is a living document. Even its author treated it as something maintained, not something finished — and the frame of the books themselves, a history copied and recopied by characters inside the story, is a fictional version of the same device.

Jordan: the glossary becomes public infrastructure

The Wheel of Time ran to fourteen books, and each one ships with a glossary of names and terms — a lore reference printed in the back of the volume, for readers and for the record. When the author died mid-series, the remaining books were completed from his detailed outlines and notes, and the fan-maintained glossary became the community's working reference for the world.

The lesson: at series scale, the reference document stops being private. It becomes the thing the next writer, the editors and the readers all depend on — which is a strong argument for keeping it structured and current from book one, rather than reconstructing it at book ten.

Sanderson: constraints before prose

The most documented modern case. Sanderson has described designing the magic system before the prose — Allomancy's metals, each with a defined rule — and keeping world documents for the connected Cosmere. His "Sanderson's Laws of Magic" are a public distillation of what he checks: a system's limitations are where the story's conflict lives, and every power has a cost.

Notice the shape of that. A magic system is recorded as a set of rules a scene can violate — which is exactly what an entry should own. Not "magic is dangerous" but "this metal does this, at this cost", specific enough that a draft can get it wrong.

Martin: notes are necessary, not sufficient

The honest counterweight. Martin has talked about the scale of the worldbuilding behind the series — the companion volume World of Ice and Fire collects histories and family trees that do not fit in the novels themselves — and a series of that scale still ships with the occasional slip, the kind readers catalogue.

The lesson is not that notes fail. It is that notes at the back of the process fail differently from notes in the middle of it. Facts recorded after the scene, or recorded somewhere the scene cannot reach, protect the archive but not the draft. The document has to be consulted at the moment of writing to do its job.

What the four have in common

Strip the scale away and the shapes agree:

• Entries, not essays. Even Tolkien's legendarium is organised as documents per subject — a history of a place, a lineage of a house — not as one continuous narrative.
• Constraints over descriptions. The recorded facts are the ones a scene can violate: a rule, a date, a cost, a distance.
• Maintained, not written once. Every one of these worlds was revised while the story was still being told.
• The world's facts are load-bearing. Treated that way, they hold. Treated as decoration, they drift.

None of this requires a wiki, a database or a tool. It requires the structure — entries, links, constraints — and the habit of recording at the moment of invention.

Related

• What is a lore bible? — the definition and an entry template
• Lore bible vs. character bible — when the smaller document is enough
• Building a lore bible you will actually use — the four structural habits

And when the test is specific — does this scene break a fact you have written down — the lore consistency checker checks a scene against your listed canon, free and without an account.