No canon-aware codex: flexible note tools store lore as scattered pages with no entity or relationship tracking, so worldbuilders hand-build fragile setups that decay

Summary

Fantasy writers, TTRPG game masters, and worldbuilders store their universes (heroes, factions, relics, timelines, relationships) inside general-purpose tools like Obsidian or Notion. Because those tools are generic, the user must personally engineer the structure: plugins and custom workflows for linking, manual conventions for naming, and manual discipline for keeping facts consistent across dozens or hundreds of pages. Users report exactly this failure mode — 'the customization took more work than I expected with plug-ins needed for a lot of the workflow,' setups so complex they doubt 'how much they are used,' and the moment of giving up: 'I thought I would be so productive once I got this Notion or Obsidian setup perfect and realized I lived a whole life before it and gave up on it.' When the setup is abandoned, the lore does not disappear — it fragments: contradictory character details, forgotten factions, broken cross-references, and no reliable way to answer 'what is actually canon?' Syncing across devices makes it worse, so the codex exists in multiple divergent versions. This is fundamentally unsolved: existing note tools sell flexibility, not canon integrity; existing worldbuilding wikis (World Anvil, Campfire, Kanka) are heavyweight article databases that require manual linking and don't check or surface contradictions; and no AI-assisted codex presents an original, internally consistent universe of heroes, factions and relics with relationships the writer can navigate and extend. The result is a project that quietly dies, forcing creators to rebuild from scratch or abandon the universe entirely — a severe, recurring, and highly paid-for pain.