Story Teller Docs / Consistency & Pre-Flight

Consistency & Pre-Flight

As a story grows, keeping every detail consistent gets harder — a character’s eye color, when something happened, a rule of your world. Story Teller checks your prose against the notes you have built and flags contradictions, so continuity errors surface while you write instead of in a review much later.

Inline consistency checking

When you save a fiction scene, Story Teller checks it against your story’s elements and marks any issues inline in the Document Editor — right in the margin, at the line where the issue occurs (in the default CodeMirror mode).

Each issue carries:

AttributeMeaning
SeverityWarning or Error
CategoryCharacter, Timeline, World, or Continuity
DescriptionWhat the problem is
SourceThe note or scene it conflicts with

For example: a character described here in a way that contradicts their character sheet ; an event placed out of order against your timeline ; prose that breaks one of your world rules .

The Pre-Flight check

You can also run a Pre-Flight check across your whole story from the Dashboard. Instead of a single scene, it examines the manuscript as a whole and surfaces the consistency issues it finds, so you can do a full continuity pass before you consider a draft done.

Consistency checking can be scoped — a single scene, one character, the timeline, your world, or the full story — so you can focus a review where you need it.

The Dashboard

The Dashboard gives you the state of your story at a glance:

  • Manuscript progress and word counts against your target
  • Characters, timeline, and worldbuilding summaries
  • Scene status — how many scenes are drafted, revised, or final
  • The Pre-Flight consistency results
  • Token usage — how much AI work your project has used, broken down by model, with an estimated cost

The Dashboard reflects the state as of when you open it; switch its time range to refresh the figures.

← PreviousThe Document Assistant