One entity, every name.
Names, aliases, and grammatical forms can point back to the same Codex entry.
03 / Story world
A story bible.Built to evolve with the story.
Keep characters, places, lore, chronology, relationships, and visual references close to the manuscript—including the moments when facts change.
A world with memory
Names shift. Alliances break. Characters become different people.
Keep structured facts and long-form lore connected without flattening the whole story into one timeless profile.
Library structureOne world. Several books.
Book 01
Book 02
Book 03
Track change through the story.
Keep time-based mutations instead of flattening every character into one profile.
See chronology and relationships.
Use chronology, graphs, families, diplomacy, and maps around the same work.
Move from one book to a universe.
Place supported knowledge at book, series, or universe scope where it belongs.
- Codex
- Compendium
- Atlas
- Timeline
- Graph
- Genealogy
- Diplomacy
- Moodboard
Book · Series · Universe
Different knowledge, different homes
A reference system, not one endless notes file.
Use the surface that matches the kind of knowledge you need to retrieve.
Structured entities the manuscript can recognize.
Keep characters, places, factions, items, aliases, forms, relations, sources, images, and evolving states in structured entries.
Long-form lore with scope and provenance.
Store explanatory world knowledge with book, series, or universe scope where supported.
See where events happen and when facts apply.
Use Atlas and Timeline to keep geography and chronology inspectable.
Follow families, alliances, and connected entities.
Use Graph, Genealogy, and Diplomacy when a flat list hides the important relationship.
Scope deliberately
Keep a book specific. Share a world when it truly belongs.
01BookKnowledge specific to one manuscript.
02SeriesSupported knowledge shared by connected volumes.
03UniverseSupported knowledge that belongs to the wider world.
Build once, retrieve deliberately