Continuity Guard

Workflow

1. Extract the non-drift fields from the task and current state.
2. Identify the highest-risk continuity items before writing.
3. Convert those items into short writer guardrails.
4. If a draft already exists, compare the draft against those guardrails.
5. Prefer blocking drift over inventing patch explanations.

Output contract

Produce a short structured checklist, not freeform lore. Keep it to the fields the writer must actively preserve.

Recommended shape:

{
  "skill": "continuity-guard",
  "mode": "scene-canon",
  "must_check": [
    "current book time",
    "investigation stage",
    "artifact holder and location"
  ],
  "high_risk_conflicts": [
    "Do not move a hidden item back into storage if tracker says it is carried on body."
  ],
  "non_drift_fields": [
    "risk level",
    "relationship status",
    "last locked scene consequence"
  ]
}

Hard rules

• Do not create new canon to cover a continuity mistake.
• Do not explain away conflicts with vague narration.
• If canon and task conflict, surface the conflict explicitly and preserve canon unless the user changed it.
• Prefer short, testable statements over interpretive summaries.

Modes

• scene-canon: general scene writing continuity
• artifact-state: object holder, location, visibility
• timeline-check: current time, relative order, scene bridge
• repair-check: high-risk items for revise/rewrite rounds

Reference map

Read only what you need:

• references/checklist.md for the standard continuity checklist
• references/conflicts.md for typical drift patterns and what to do