narrative-judge

To validate narrative continuity after rewriting a story beat, you need an adjudication step that evaluates the rewritten beat against the original and the insert-trigger. This process checks whether the rewrite resolves contradictions while preserving the original beat's dramaturgical function.

A reharmonize workflow in interactive fiction is a narrative pipeline process that resolves contradictions introduced by new story inserts. It uses a final-approval gate to ensure rewritten beats maintain canonization and dramaturgical integrity without introducing new continuity errors.

You can get a structured JSON verdict for automated narrative approvals by evaluating insert, original, and rewritten beats in a single pass. The output contains an approved boolean, a numeric score between 0 and 1, and a one-sentence justification reason.

Yes, you can use this narrative adjudication approach within Hermes pipelines. It functions specifically as a final-approval gate to evaluate rewrites, ensuring that contradictions are fully resolved before canonization occurs within the narrative pipeline.

A limitation of automated narrative rewrite evaluation is that it provides a strict binary approval flag and a single numeric score, which may not capture nuanced dramaturgical contexts. It strictly evaluates whether the insert's contradiction is resolved without introducing new ones.