Your story,
fully remembered.
AxiomStory reads your draft as you write and keeps an evidence-linked wiki of every character, place, and faction, so book three remembers what chapter one promised.
No setup, no story bible homework. The wiki builds itself as you write.
Built from your words
Wiki pages are extracted from the manuscript itself, not from forms you fill in.
Evidence on every fact
Each claim links back to the chapters and lines that establish it.
One studio, end to end
Plan, write, and wiki in the same draft with no exports and no copy-paste.
Every name in your draft knows its own story.
As you write, the manuscript quietly links names to their wiki pages. Click one to see who they are, what’s been established, and the exact lines that prove it, then push that canon into your assistant’s context without leaving the page.
- Inline wiki matches, resolved by name and alias
- Evidence refs back to chapters and lines
- Insert into draft context for grounded AI help
She thought of the archive, of her mother’s steady hands…
Live demo: click the underlined name.
Dawn found Aria Voss where the envoy least expected her: on the wall, not behind it.
“You quote the Accord at me,” she said, “but I learned its terms in the archive,
and I heard what it cost when the bells of Kestrel Bay rang twice.”
Live demo: toggle the reference chips, or replay the generation.
The AI writes with your wiki open.
When you ask for a scene, a rewrite, or an expansion, the assistant pulls the relevant wiki pages first: who knows what, where things stand, what the rules are. The prose it returns is grounded in your established canon, and every suggestion waits for your accept or reject.
- References resolved automatically from your prompt
- Generated prose linked back to the pages it used
- Accept or reject. Nothing lands without you
The wiki remembers how your story looks, too.
Wiki pages track how characters change as the chapters move: coats, scars, titles, allegiances. And when you want to see your cast, approved reference views keep Aria looking like Aria.
Tracked from the manuscript as Aria changes, chapter by chapter.
Approved views stay pinned to the wiki page, so Aria looks like Aria in chapter one and chapter forty, wherever she shows up.
One continuous take rendered from Aria’s approved views with the same braid, coat, and harbor the wiki keeps in canon.
Thinking in public about story memory.
Why Story Teams Need State, Not Just Notes
A practical case for tracking derived current truth from events instead of relying on static notes and overwritten summaries.
What a Lore Graph Should Actually Store
A practical model for deciding which entities, relationships, rules, events, and source passages belong in a story-first lore graph.
How to Keep Character Canon Stable Across Model-Assisted Drafts
A practical system for keeping voice, appearance, motivation, and scene-level state aligned when models help draft recurring characters.
Answers for writers deciding whether to draft here.
You click Build wiki inside the draft studio. An agentic run reads your manuscript (or a quick plan), finds the story elements, writes structured pages, and checks every reference. You review the result and publish the pages you trust.
Give your story a memory that keeps up with you.
Join the waitlist and be first in line when AxiomStory opens. Bring a manuscript, press Build wiki, and watch your world organize itself.