Story state tracking means writing down what is true right now at a given point in your story, and which change made it true, not just a loose summary of your world. River Song shows why. In "Silence in the Library" and "Forest of the Dead," written by Steven Moffat in 2008, she knows the Doctor well, but the Tenth Doctor has never met her. The same fact, "River knows the Doctor," is true for her and false for him.
A note would say "River and the Doctor are close." It can't tell you whose scene you are in, or when.
Give every fact a point in the story
River finds out in those episodes that he hasn't met her yet in his own timeline. Their adventures run out of order, so his first meeting with her is apparently her last. If characters in your world learn things at different times, then a fact needs a "who knows it" and a "when" attached to it.
Say your villain is the hero's half-sister. The note "villain is related to hero" will not stop you from writing chapter four as if the hero knows. State says the villain knows from chapter one, the hero learns in chapter nine, and the town never learns. Before you draft a scene, ask what each person in it believes at that exact moment, and write the answer down.
River also carries a diary of her adventures. Think of it as a log of events in her own order. You can keep the same kind of log for your world: one line per change, with what changed, which chapter it happened in, and what caused it. This is the idea behind an event sourced story bible.
Keep the reason, not just the result
Take a note that says the city is unstable, the queen is missing, and the gate is damaged. State goes further. It says whether the gate can be used tonight, whether the queen is thought dead or secretly locked up, and which groups know the truth.
When you overwrite a summary each time something changes, you lose the reason the world is different. That makes arguments between co-writers harder to settle and makes continuity slips harder to trace. If two of you disagree about whether the gate works, you can point to the line that broke it instead of trading memories.
Write the order down on purpose. AxiomStory's Wiki saves its work as it builds pages from a book, so when you add or change a chapter it can keep its earlier plan instead of starting over. In October 2026 we found that every rebuild was throwing the plan away. We first guessed that each run kept its own cache, but a test showed one run could read what an earlier run had saved, so that was wrong. The real cause was that our database hands back a record's keys in sorted order, not the order we wrote them, and our code read chapter order from that. We fixed it by storing the order as a list. Our rule since then: never trust the order something happens to come back in. In your own files, that means numbering chapters and events yourself instead of relying on alphabetical order or the order a folder shows them.
A manuscript studio with source-linked Wiki review.
Make warnings point somewhere
A good continuity system does more than say "this looks wrong." A useful warning names the record it clashes with, what the current state seems to be, and the event or passage that set it. In a shared world, that lets people disagree about a scene without guessing where a fact came from. Our rough rule is that a flag with no source is only an opinion. It won't catch everything, since a tool can only compare what has been written down.
If you feed an AI model a mix of old summaries and recent changes, it has to guess which version applies to the scene. Give it the current truth for that moment instead.
AxiomStory builds a wiki of every character, place and rule from your chapters and flags lines that disagree across chapters. It works in any browser, and it's free to start with no card. It needs an internet connection.
Good narrative continuity comes from this habit more than from any tool. Try it on one character today: write what they know, what they believe, and which chapter taught them, then check your next scene against it.
