The Codex
Characters, locations, factions, items, and lore — held as interconnected dossiers that your manuscript, your maps, and your AI companions all read from. One truth, everywhere.
Every entry carries structured fields the whole application understands: traits and stat bars, biography, voice samples the Editor checks prose against, portraits from the built-in gallery, and the chapters the entity appears in.
Locations nest inside locations — the Highpass Inn sits in Highpass village, in the Northern Reach — and factions hold members, allies, and enemies. The Coach builds all of it on request, citing your own worldbook as its source.
Relationship Maps
Every tie — blood, rivalry, debt, secret alliance — renders as a living graph of glowing nodes and filament lines. Walk it to find the connection you forgot you wrote.
Relationships are polymorphic: characters to factions, factions to locations, items to their keepers. The map is read straight from the dossiers — never maintained by hand.
The Weaver — Elara Vance
Bound to the Manuscript
Three ways the world-bible and the manuscript stay one thing.
Read
Type [@ and autocomplete offers your whole cast. The pill resolves live from the dossier.
…said [@ElaraVance], setting down the crucible.
Write
One-shot writes from the editor: close the bracket and the value lands in the Codex.
[@Arakasha.prowess="+1"]
Reflect
Canonize a new detail in prose and the Editor notices — and stages the Codex update for your approval.
Template-Aware Lore
A Victorian romance needs stations and scandals; a d20 campaign needs heritage, class, and equipment. Tell the Coach — "I'm using D&D 5e, build a character template" — or let it infer one by reading the characters you already have. The Codex reshapes its fields to match, and the Game Table rolls against them.
See the Game Table →Fourteen days free, every feature. The Codex starts remembering on page one.
Mythos has not been released yet. Stay tuned — it is coming soon.