Building a lore bible you will actually use

There are two kinds of worldbuilding bible. One is a monument: forty thousand words written in a burst of enthusiasm before chapter one, beautifully organised, never opened again. The other is a working document, consulted mid-sentence, ugly in places, and the reason book four does not contradict book one.

The difference is structural, and it is learnable.

1. Entries, not chapters

The single most common mistake is writing the bible as prose. A twelve-page essay on the history of your empire is a pleasure to write and nearly useless to consult, because the thing you need — the year the capital fell — is buried on page seven.

Break it into entries with one subject each. A place, a person, a faction, an event, a rule of magic. If an entry needs a scroll bar, it is probably two entries.

The test: can you answer a specific question by reading one entry? If answering "how old is Serin?" requires reading her entry, her mother's entry and the timeline, the granularity is wrong.

2. Record constraints, not descriptions

Descriptions are pleasant. Constraints are useful.

Description: Serin is a tall woman in her thirties with dark hair and a scar across her face.

Constraint: Serin lost the sight in her left eye at the Siege of Talor, 12 years ago. She cannot judge distance and has stopped using a bow.

The second one can be violated by a scene. The first one mostly cannot. Every fact worth recording is a fact a future chapter could contradict — and the ones that are hardest to remember are exactly the ones that constrain how a character moves, fights, sees or speaks.

A good habit: after each entry, ask what could a scene get wrong here? Write that down instead.

3. Link, don't mention

If an entry mentions the Siege of Talor in passing, that connection exists in your head and nowhere else. If it points at the entry for the Siege of Talor, the connection exists in the structure — and structure is what a search, a graph or another person can follow.

This matters more than it sounds. Links are what let a scene set in one place reach a fact stored somewhere else entirely. The city links to the siege; the siege links to the general who lost it and to the injuries it caused. A draft that mentions only the city can still surface Serin's blind eye, two hops away, because you drew the path.

Draw the paths as you write the entry, while you still remember why they matter.

4. Write entries at the moment of invention

The bible decays when it becomes a separate task. "I'll write this up later" is where continuity errors are born, because later you will remember the decision but not its details, and you will write down the version you can recall rather than the version you used.

The rule that works: if you invented it in a scene, it becomes an entry before you close the file. Not a polished entry. Two sentences and a link. The polish can wait; the fact cannot.

What good looks like after a year

A working bible is lopsided. Some entries are a single line. A few are long because they earned it. The linking is dense in the parts of the world you actually write in and sparse everywhere else, which is correct — you built detail where the story went.

It will not look like an encyclopaedia. Encyclopaedias are written for readers. This one is written for you, at eleven at night, mid-scene, trying to remember which hand she favours.