What a Lore Graph Should Actually Store

Editorial wall of entity cards, relationship threads, and rule notes arranged like a story-focused lore graph.

A lore graph is a story bible stored as linked records, where characters, places, groups, things and rules are joined by named links and each fact is tied to the scene that set it. The Wheel of Time shows why that tie to a scene matters.

Robert Jordan first planned the series as a trilogy, and it grew to 14 books plus a prequel novel. Before he died on September 16, 2007, he wrote a large set of notes so that a new writer could finish the final book. Brandon Sanderson finished the story across three books from 2009 to 2013, and the last one carried Jordan's title, A Memory of Light. If your own series runs long, the person reading your notes years from now may well be you, without the memory that wrote them.

A rule needs a scope and a point where it changes

The One Power has a male half, saidin, and a female half, saidar, and because the Dark One tainted saidin, men who channel go mad and only women can channel safely. Written as one line, "male channelers go mad" looks finished. It leaves out a lot, though, because in Winter's Heart, book 9, Rand al'Thor and Nynaeve al'Meara cleanse saidin of the taint at Shadar Logoth. The rule holds up to a known point in the story and not after it.

In a story bible database, a record for that rule could look like this:

  • Rule: saidin is tainted; men who channel go mad
  • Applies to: men who channel saidin
  • Source: link to the first scene that shows it
  • Status: changed by an event
  • Changed by: cleansing at Shadar Logoth (Winter's Heart, book 9)
  • Breaks if ignored: a man channels before the cleansing and the draft treats it as safe

The status line can say a rule holds everywhere, holds in one place, belongs to the past, is in doubt, or was changed by an event, and it's worth picking one for every rule you keep. The "breaks if ignored" line does the most work when you revise. Say your villain can't cross running water. Write down which rivers count and which scene first showed it, then what goes wrong if he wades across a stream in chapter 30, and you have something you can check a draft against.

Events belong in their own records

The cleansing is its own record in that graph, linked to the rule it changed. If you kept only a summary note and rewrote it after book 9, the old rule would be gone, and nothing would tell you what was true in book 5. When a city falls or a treaty breaks, give that event a record and link it to every fact it touches. That's the heart of knowledge graph worldbuilding, and it's how you make continuity easy to explain to yourself or a co-writer.

At AxiomStory, our Wiki reads a book and writes pages from it, and along the way it pulls out claims, single facts from the chapters, each kept with where in the book it came from. We save the full output of real Wiki runs, including a full-book run in October 2026, with every finished page and every claim in their own files. When we change a check, such as the one that looks for facts that clash over time, we run it again on those saved runs and compare what it flags before and after, without paying for new writing. That check needs the claims, and finished pages alone wouldn't be enough to run it. For your own notes, it means the source line should sit next to each fact.

Keep your story together.

A manuscript studio with source-linked Wiki review.

Try AxiomStory free

People, links and what to leave out

Useful fiction entity relationships include loyalty, family ties, who owns what, rivalry, who gives orders and who needs whom, plus which scene or place a person is tied to right now, with the passage that shows why the link exists. A fact with a source you can see, the scene or note that brought it in, is easier to trust and easier to argue with when you're settling your narrative canon.

Our rough rule is that if a fact never changes a scene choice, a search result or a continuity check, it doesn't belong in the main layer, so the color of a minor innkeeper's door can go in a loose file. No setup like this will catch everything. You can still pick one rule your plot leans on today and write its record, with its scope, the scene that set it, and the event in your outline that could change it.