arc-audit

To check campaign continuity and drift, you audit the campaign spine against its current state, surfacing orphan seeds, missing foreshadowing, and hint drift. The audit reads session logs and seed-tracker files to produce a detailed report with PASS, WARNING, and VIOLATION statuses.

Run a campaign spine audit before adventure design, during play, and before finales to verify seeds, foreshadowing, hints, and artifact coverage. This timing ensures drift and continuity violations are caught early before they compound across sessions.

A campaign audit report includes PASS, WARNING, and VIOLATION statuses for orphan seeds, missing foreshadowing, hint drift, PC-spotlight balance, and artifact-slot coverage. The report is written to a dated markdown file and does not modify any existing files unless explicitly asked.

Yes, the audit writes a report only and does not modify files unless explicitly asked. It reads the campaign spine, seed-tracker, session logs, and guidelines to produce a standalone report, leaving all source documents untouched.

Before running a campaign continuity audit, you need a campaign spine document, a seed-tracker file, session logs, and CLAUDE.md guidelines in place. The audit reads these files to compare the planned spine against the current campaign state and generate its report.

The best way to detect orphan seeds and missing foreshadowing is to audit the campaign spine against session logs and the seed-tracker. This comparison surfaces seeds that were never resolved and foreshadowing elements that lack proper setup or payoff.