governance-audit

Documentation drift in repository governance files is detected by performing a side-by-side reading of operating docs like ROUTER.md and AGENTS.md to identify broken cross-references, undocumented environment variables, and conflicting rules.

Auditing project governance documents for compliance requires executing the pdda.sh governance script followed by a comparative analysis to evaluate doc-to-code drift and identify mechanical or semantic inconsistencies.

A consistency audit on project documentation is needed before a major project milestone or when onboarding new contributors to ensure internal guidelines are perfectly aligned with the actual codebase and current standards.

Checking for conflicting prose and stale claims across AGENTS.md and ROUTER.md is possible through a semantic consistency review that flags duplicated ownership assertions and outdated operating procedures.

The governance audit does not require external dependencies; it relies on executing the built-in pdda.sh governance script to perform deterministic drift detection and comparative analysis.

Project guidelines and agent instructions become contradictory due to documentation drift, where operating procedures and project guidelines become outdated or conflict as a repository evolves over time.