Every serious creative project eventually produces a canon: a reference document defining what is true within the story. Character details, timeline, world rules, established facts. Canon is useful, necessary even, and creative teams are right to maintain it carefully.
It is also frequently confused with something else: continuity of reasoning. The two are related but not the same, and the confusion causes real problems in long-running creative work.
What Canon Actually Captures
Canon captures state: what is currently true. A character's age, a city's geography, the sequence of events established so far. A well-maintained canon document answers what happened and what is consistent with what happened reliably. That is genuinely valuable. Consistency errors, a character's eye color changing between books, a timeline that contradicts itself, are exactly the kind of mistake a canon document exists to prevent.
What Canon Does Not Capture
Canon rarely captures reasoning: why a decision was made, what alternatives were considered and rejected, whether the original logic still holds given how the story has since evolved. A canon document can tell a writer that a character does not trust the protagonist. It usually cannot tell them why that distrust was designed the way it was, or whether the reason still applies several books later, after the story around it has shifted.
This gap rarely shows up as an obvious continuity error. It shows up as something subtler: a creative decision that is technically consistent with canon but quietly at odds with the story's original logic, in a way that only becomes visible much further down the line, often after real cost has already been sunk into it.
Why This Distinction Matters More as Projects Grow
The gap between canon and reasoning scales with project size and duration. A short story does not need this distinction; the writer holds the whole reasoning chain in their head. A multi-book series, a long-running writers' room, or a franchise developed across years and multiple creative leads is a different problem entirely. The volume of decisions eventually exceeds what any single memory, or any static reference document, can reliably hold.
Building for Reasoning, Not Just State
This is the specific gap Norra, Aeon Bloc's creative intelligence platform, is built to address. Rather than treating canon as a static list of facts to check against, Norra is designed to preserve the reasoning and context behind creative decisions as they are made, so that logic remains available later, not just the state it produced.
Norra remains in active development, and this is one of the harder problems it is working through: reasoning is messier to capture than state, and doing it well without becoming a burden on the creative process itself is the real design challenge. But the distinction between canon and continuity is the reason the effort seems worth making. A story can be perfectly consistent and still have quietly lost the thread of why it was built the way it was.