Continuity problems often begin with a reasonable change. A clue arrives earlier. A conversation moves. A character learns something they used to discover three chapters later. The change works on the page, but the rest of the book has not caught up.
Follow what changes, and who knows it
Quillgon stores the story behind the prose as connected scene cards, facts, character states, and threads. Its character view shows what each person knows, scene by scene. Editing a fact or a character’s knowledge can reveal later scenes that depend on it. For a manual pass, use the character knowledge checklist.
Track the promises your story makes
A clue, a question, an unresolved promise, or a conspicuous object gives the reader something to remember. The setups and payoffs ledger follows these obligations from where they are planted to where they resolve, and flags missing or out-of-order payoffs.
The writer receives the relevant setup and payoff obligations when drafting a scene. Extraction then checks what the prose actually established. This helps keep the plan and the written story connected.
Review the effect of a revision
A ripple starts with a proposed change and traces its connections across the book. Review affected scenes and card or prose differences, then accept or reject each proposal. Locked scenes surface a conflict for you to resolve.
These checks support editorial judgment. They do not guarantee that a book has no plot holes, or that a payoff will feel convincing to a reader. The connected model is most useful when you keep the underlying scene facts accurate.
A useful place to begin
Choose one reveal in your manuscript. Write down who knows it, when they learn it, and which later scenes assume that knowledge. That is the chain a continuity review needs to follow.