Canon Facts
Canon Facts are your story’s rules — short, unambiguous statements of what is true and what is forbidden in your world. Unlike the entity blocks (which describe your cast and setting), canon facts are constraints the writing must obey: they are fed into the pipeline and the prose is written to never break them. It’s the last sub-step of the World step (sub-step 6 of 6), and it’s optional — but it’s the strongest lever you have for keeping a long book consistent.

What’s on this page
- A list of facts, each a single rule with a category, a severity (hard / soft), scope tags, and an on/off toggle.
- Category filters — All · Characters · Timeline · Locations · Technology · Society · Language · Forbidden.
- “+ Add Fact” to write one by hand, and “AI: Generate canon facts” to draft a set from your story.
- A quality-tier selector (Bronze · Silver · Gold) for the AI drafting, with its coin cost shown.
How to use it
- 1Add the rules that matter — the hard limits (what can’t happen) and the world truths that must hold across chapters.
- 2Give each fact a scope: @GLOBAL for a world rule, @CHAR:Name for a character-specific one, so it reaches the right scenes.
- 3Keep hard facts absolute and few; use soft for guidelines. Too many @GLOBAL facts crowd the context — tag them to scope.
Where this fits
Canon Facts is the last World sub-step (sub-step 6 of 6), and the only one that isn’t about describing your world — it’s about constraining it. Your characters, locations and world blocks tell the writing what things are like; canon facts tell it the rules that must never bend. It’s optional, but on a long book it’s the single strongest lever for keeping the story consistent from chapter 1 to the end.
A canon fact’s fields

fact_text · textareaNo character can use magic to raise the dead; death is permanent in this world.severity · selecthardan absolute rule — the writing must never break itsofta guideline — a strong preference the writing should follow
tags · tags@GLOBAL · @CHAR:Serra, @TOPIC:map_magicenabled · togglesource · textCategories

category · selectCharacterswho people are and what they can/can’t doTimelinechronology, order of events, what has/hasn’t happened yetLocationsplaces and their propertiesTechnologytech level, science, magic-system mechanicsSocietydaily life, customs, social structureLanguagehow people speak, naming, registerForbiddenhard prohibitions — what must never appear
Scope tags — where a fact applies
A fact’s tags decide which scenes it reaches. This is what lets you keep a hundred rules without drowning every scene in all of them — each fact only travels where it belongs.
@GLOBAL — a true world rule; injected into every scene. @CHAR:Name — reaches only scenes with that character. @TOPIC:theme — reaches only scenes about that theme. Facts you leave untagged behave like local notes and may not reach the prompt, so give each one a scope.
AI: Generate canon facts
AI: Generate canon facts drafts a set of rules from your story — it reads your synopsis and cast so the facts anchor to your world, not generic genre tropes, and it tags them with scopes (@GLOBAL / @CHAR / @TOPIC) for you. The pill row picks the quality tier(Bronze · Silver · Gold, higher being more capable) and shows the coin cost before you commit. Generated facts are written in your project’s language, and each is marked as AI-drafted — review them, then keep, edit or delete.
Keeping it focused
Canon is powerful because it’s injected verbatim — which also means it costs context. A short set of sharp rules beats a long list of vague ones. Past about 50 facts the editor nudges you to tag them, so the pipeline can prioritise the ones a given scene actually needs. Reserve hard for real invariants, scope everything with tags, and turn a rule off rather than deleting it when you just want to test its effect.