web-content-audit

Cross-file data drift is identified by reading local content, course data, and deployed artifacts to detect inconsistencies across materials, assets, and routing references. It surfaces misalignments like missing illustrations and mismatched IDs for human review.

Three-place sync checking compares the filesystem, data model, and router references to detect missing illustrations, mismatched IDs, and content drift. It ensures source materials, course data, and deployed assets remain aligned before releases.

You generate Markdown audit reports by running the audit suite in the scripts directory, which outputs human-readable reports to data/audit-*.md. These reports surface cross-file inconsistencies without blocking your deployment pipeline.

Yes, you can run a content audit without blocking your deployment pipeline because the process outputs Markdown reports to surface drift and never blocks releases. It leaves remediation entirely to human reviewers.

You need to check for misalignments between course data and source materials before major releases or corporate handoffs. Running a cross-file audit ensures deployed assets are aligned and prevents content drift during critical updates.