invest-doctrine

To audit project documentation for consistency, run a doctrine audit that checks VECTOR.md, CLAUDE.md, and ARCHITECTURE.md for completeness, cross-document alignment, and design drift against the actual codebase. This produces a structured report with severity levels and recommended actions.

Architecture drift detection identifies gaps between declared architecture documentation and the actual repository code. You need it when missing, incomplete, or conflicting doctrine files threaten to cause downstream failures in architecture validation or workflow automation.

To check if missing doctrine files are blocking architecture checks, audit your foundational files to identify incomplete or conflicting documentation and flag downstream checks that cannot run without them. This unblocks subsequent validation steps by surfacing actionable gaps.

Yes, you can use a doctrine audit report for workflow automation because it outputs structured findings with severity levels and recommended actions. This format allows automated pipelines to parse the results and gate downstream processes based on the detected documentation completeness.

The best way to validate cross-document consistency is to audit VECTOR.md, CLAUDE.md, and ARCHITECTURE.md simultaneously to detect drift and surface alignment issues. This ensures all essential doctrine files are up-to-date and aligned before executing deeper architecture validations.

Architecture validation fails when doctrine files are out of sync because missing, incomplete, or conflicting foundational files cause downstream checks to error. Auditing these files beforehand surfaces the exact inconsistencies blocking the validation pipeline.