invest-doctrine

The audit detects missing files, contradictions, and drift by cross-checking VECTOR.md, CLAUDE.md, and ARCHITECTURE.md against each other and the actual codebase. It enforces structure rules and reports findings to guide downstream architecture investments.

Documentation contradictions happen when doctrine files drift from the actual codebase and lose cross-document coherence. Running a doctrine audit surfaces these gaps, validates terminology boundaries, and identifies ambiguous requirements to prevent downstream audit failures.

Yes, a consistency audit requires all three doctrine files—VECTOR.md, CLAUDE.md, and ARCHITECTURE.md—to exist. The audit enforces structure and cross-check rules across the complete set to accurately validate content quality and detect drift.

The best way to track open questions in governance documents is to audit doctrine files for completeness and cross-document consistency. This surfaces ambiguous requirements and gaps, reporting findings to guide architecture investments.

Yes, you can check if architecture documentation matches the actual codebase by running a doctrine audit. It validates presence, content quality, and cross-document coherence across VECTOR.md, CLAUDE.md, and ARCHITECTURE.md to detect drift.