verify-diag

To verify an architecture diagram against a codebase, cross-check that all named components exist in the repository and that indicated connections reflect real data flows. This process identifies missing components and incorrect read/write directions to ensure diagram accuracy.

Architecture diagram verification is the process of identifying discrepancies between a named diagram and the actual codebase, including missing components and incorrect data flows. You need it during architecture reviews to ensure documentation accurately reflects repository structures.

To check read/write directions in a codebase diagram, analyze the actual data flow between connected components in the repository. This directionality analysis classifies whether each connection accurately represents read or write operations.

Yes, diagram verification applies to codebases of varying sizes and architectures. It performs component existence checks, connection verification, and directionality analysis to validate mermaid diagrams regardless of the underlying architectural complexity.

The best way to find missing components is to run a discrepancy report comparing the named architecture diagram against the actual codebase. This structured reporting identifies missing components, verifies connections, and provides actionable fixes to improve accuracy.

Your mermaid architecture diagram shows incorrect data flows when indicated connections fail to reflect real read/write directions in the repository. Connection verification identifies these discrepancies and provides structured findings to correct the data flow representation.