Continuity checks

The eleven deterministic continuity checks of Author, what each one looks at, severity, how to dismiss an issue, and what the checks cannot see.

Updated 17 October 2026 · View as Markdown

The checks are rules over your data. No model runs. Every issue names the rule, the scenes, events and characters that break it, and a scene to jump to.

CodeRuleLooks atSeverity
C1In two places at onceA character in two overlapping scenes at different placeserror
C2Travelled too fastFrom A to B faster than the route allowswarning
C3The dead reappearIn a present-mode scene after their deatherror
C4Before they existedIn a scene before their birth or foundingerror
C5Age driftA scene says an age the birth date contradictswarning
C6Date and weatherA stated weekday against the calendar; two weathers at one place and timewarning
C7Order of timeRelative times in a circle; an anchored event timed outside its sceneerror
C8Point of view not presentThe point-of-view character is not in the scenewarning
C9Knows too earlyA scene says they know something before they learn itwarning
C10One object, two placesA unique object in two places at onceerror
C12Beat off its markA structure beat far from its targetinfo

Flashback, dream and memory scenes are exempt from the presence rules.

Using the checks#

  • Run them from the Story view or ask your AI to run them. The result is stored.
  • Open an issue to jump to the scene.
  • Dismiss an issue that is intended. Dismissals are remembered by fingerprint, and undo brings an issue back.

What they need#

The checks work on what you entered. For travel (C2) they need places and routes with distances on a map. For knowledge (C9) they need events of the kind learns or effects on knows. For age (C5) they need birth dates in the profile.

What they cannot see#

  • A fact that is only in your prose and nowhere in your data.
  • Style, grammar or whether a scene works.
  • Statements about age in prose are low confidence and show as information only.