reality

To check for architecture drift, you can analyze a codebase to validate architecture and documentation alignment. This process auto-detects the project type and synthesizes a comprehensive drift report highlighting misalignments.

Codebase documentation drift occurs when documented architecture no longer matches the implemented code. A health score quantifies this alignment severity, providing actionable findings to guide remediation and prevent misinformed decisions.

You can run a quick architecture scan on a large codebase using mode-based scans. By invoking a --quick scan mode, the analysis rapidly auto-detects the project language and generates a baseline drift report.

Yes, you can analyze specific areas of a project for documentation drift using the --focus scan mode. This targets particular sections of the codebase, providing a tailored architecture-drift score and structured health report.

The best way to generate an architecture health report is to run a deep codebase analysis that compares code against references. This approach produces a structured report with a comprehensive health score and actionable drift findings.

You should run a deep codebase analysis using --deep mode when you need a comprehensive drift report for final validation. Use --quick for fast baseline checks and --focus for targeted architecture-drift scoring.