narrative-continuity-critic

To check narrative continuity after inserting a new story beat, evaluate each downstream node against the upstream insertion to determine if it remains coherent, returning a strict JSON verdict per node without rewriting the content.

A reharmonize sweep in storytelling is a process where a single upstream narrative insertion affects multiple downstream nodes, requiring a per-node evaluation to ensure the overall story remains coherent and compatible.

Yes, you can get a JSON output for narrative continuity errors by evaluating downstream beats against an upstream insertion, which returns a JSON object containing a verdict, reason, and severity for each node.

No, the continuity audit does not rewrite broken story beats; it performs a read-only check that identifies mismatches and returns a surgical JSON verdict to guide subsequent manual editing or deletion.

You identify downstream narrative beats needing editing by comparing each one against the latest upstream insertion, categorizing compatibility issues by severity to salvage beats with minimal edits or flag them for deletion.