architecture-review

You can verify architecture documentation against source code by systematically cross-referencing markdown files with the project's directory structure and module definitions to identify technical inconsistencies and code-doc drift.

Documentation drift detection works by parsing architecture markdown files and validating concrete claims against actual source code implementations, automatically flagging stale line numbers, incorrect counts, missing fields, and phantom types.

The best way to find stale architecture content is to run systematic verification across all defined batches using parallel subagent execution, which produces structured reports highlighting discrepancies between your guides and implementation.

Yes, you can check if architecture module tables reflect the codebase by executing an architecture review process that validates concrete claims against module definitions and reports technical inconsistencies.

Architecture documentation develops phantom types and incorrect counts due to documentation drift, where guides become outdated as the codebase evolves, leading to confusion and technical debt over time.

Yes, the architecture review process supports Rust projects by parsing architecture markdown files and verifying concrete claims against the project's directory structure and module definitions to identify code-doc drift.