audit-docs

Documentation drift is detected by comparing SPEC, RULES, and STRATEGY content against the implemented codebase to flag inconsistencies. This validates terminology, checks cross-references, and generates an audit report with archival recommendations for outdated docs.

Auditing knowledge-base consistency before a release involves running a periodic check that validates alignment between documentation and code. It flags contradictions and generates a report with archival recommendations to clean the docs root.

To archive outdated docs, run a documentation audit to identify drift and generate archival recommendations. This hygiene process moves outdated knowledge-base content to an archive, ensuring the docs root remains clean without losing historical reference material.

Yes, documentation drift detection specifically validates SPEC-, RULES-, and STRATEGY-based docs. It compares these knowledge-base contents against the implemented codebase to ensure terminology and cross-references remain aligned across periodic audits and releases.

Contradictions occur due to documentation drift when knowledge-base content is not updated alongside code changes. Running an audit detects these inconsistencies by comparing SPECs, RULES, and STRATEGY against the codebase and flags them in a report.