For game studios and narrative designers
Narrative teams write lore, quest scripts and barks across many documents and many hands. CanonTracker keeps one canon that every writer, and every tool, can check.
What you do with it
One canon for the whole team
Lore docs, quest scripts and dialogue in one Library. Entity types for NPCs, items, abilities and quests.
Check the recording against the script
Upload a voice take, link its script, and see changed lines and lines that contradict canon.
Change a world rule safely
Change the bell rule and see the four scenes to re-review, with re-review tasks for the team.
Let your tools work with canon
Give an agent or a pipeline a token through MCP. Agents read canon, check facts and propose; their proposals wait in Review, and a person decides in CanonTracker.
Try it on the sample
The Ashbell Pass, a 28-document game story with locations, NPCs, dialogue, a recorded take and planted contradictions. Load it from onboarding or from Settings, then review, scan and change it like your own story.
Start with a finished story
Create a studio and load The Ashbell Pass or Broken Tide: real documents, AI candidates to review and planted contradictions to find. Or run CanonTracker on your own server; it is open source.