invest-doctrine

To audit project documentation for consistency, validate doctrine files like VECTOR.md and ARCHITECTURE.md against filesystem reality to detect drift, check structural requirements, and identify cross-document contradictions. This ensures technical architecture accurately reflects the current codebase state.

Project doctrine drift detection identifies discrepancies between declared conventions in documentation files and actual codebase implementation. You need it before deploying features to confirm core principles, contributor guidelines, and stack declarations remain accurate and prevent downstream automation errors.

Yes, you can check if declared directories in ARCHITECTURE.md exist on the filesystem by running a structure versus disk validation. This verifies that declared directories match filesystem reality and flags missing or undocumented folders in your project architecture.

Validate naming conventions and import directions by auditing project doctrine files to compare declared structural requirements against the actual codebase. This process checks filesystem reality to ensure your technical stack declarations and architectural rules are correctly implemented.

The best way to find contradictions across project documentation files is to audit doctrine files for internal consistency and cross-document contradictions. This checks completeness across VECTOR.md, CLAUDE.md, and ARCHITECTURE.md to ensure alignment and produces a report with recommended actions.

Project architecture documentation fails completeness checks when doctrine files lack required structural sections, miss naming conventions, or omit stack declarations. Auditing these files identifies missing elements and cross-document contradictions, producing a detailed report of findings and recommended actions.