build-loop:architecture-review

A cross-layer architecture review validates system flow, component communication, and documentation drift by tracing connections across the codebase. It requires a well-defined architecture data model and codebase access to ensure system integrity before merging large refactors.

Documentation drift occurs when project documentation no longer reflects the actual codebase implementation. Architecture validation detects this by comparing documented component connections and system flow against the actual code to ensure consistency across all layers.

Yes, system flow analysis requires a well-defined architecture data model to accurately trace component connections and assess data movement. The model provides the structural baseline needed to perform impact analysis and validate API contracts across the codebase.

To validate API contracts and component communication, run a comprehensive architectural review using the command `build-loop:architecture-review --all`. This assesses how components interact, checks connection patterns, and ensures system flow remains consistent across all layers.

The best way to check codebase integrity is executing a comprehensive architectural review that analyzes cross-layer system flow and component communication. This validates that data moves correctly from input to output and confirms adherence to structural best practices.