continuity-guardian

To check character consistency and timeline breaks in a manuscript, run a continuity audit that reads foundation documents and relevant chapters to build tracking databases and produce evidence-backed findings. This detects reader-breaking contradictions across independently produced chapters.

Manuscript continuity validation handles unresolved entity conflicts by reading an ENTITY_STATE.yaml file when present, prioritizing those structured conflicts, and then executing standard character, timeline, and plot thread audits to resolve them.

You need to run a plot thread tracking audit after generating a batch of 3-5 chapters to check the newly written content against all prior chapters. This batch processing mode identifies plot thread continuity errors early in the drafting pipeline.

The best way to audit information flow and world rules across a long-form book is performing an end-to-end continuity audit that verifies knowledge transmission and world-rule integrity, outputting an evaluation report with chapter-referenced quotes and severity classifications.

Yes, you can use an adversarial review for post-revision manuscript continuity checks. The audit operates in post-revision mode to find character, timeline, information-flow, world-rule, and plot-thread errors introduced during editing.