ad-audit

Documentation drift between docs and code can go unnoticed during development. Auditing AGENTS.md, ARCHITECTURE.md, and ADR statuses surfaces these inconsistencies by producing a read-only drift list, ensuring alignment across documentation and implementation without modifying files.

Auditing ADR statuses and architecture docs involves read-only checks comparing AGENTS.md, ARCHITECTURE.md, and ADRs against the codebase. It generates a drift list of discrepancies for reporting, ensuring documentation validation and governance consistency during code reviews without writing files.

Yes, you can perform a read-only drift audit of AGENTS.md and ARCHITECTURE.md against the codebase. This process identifies inconsistencies and produces a drift list for reporting without modifying any files, ensuring safe documentation validation during governance checks.

A read-only drift audit is the best way to validate repository documentation against implementation. By checking AGENTS.md, ARCHITECTURE.md, and ADR statuses, it generates a drift list of discrepancies for review, ensuring consistency across docs and code without modifying files.

The limitation of a read-only drift audit is that it never writes files or fixes detected inconsistencies. It only produces a drift list identifying discrepancies between AGENTS.md, ARCHITECTURE.md, ADRs, and code, requiring manual intervention to resolve the drift.