vp-s02-layer-architecture

To check clean architectural layering, analyze your repository structure to detect core layers like domain, application, adapters, and infrastructure. This process validates allowed dependencies and identifies potential violations to ensure layering principles are respected.

Detecting hexagonal architecture violations involves mapping layer boundaries and assessing conformance with architectural principles. It identifies where inner domain modules improperly depend on outer frameworks, generating a structured assessment for governance.

Yes, you can apply this architecture analysis to MVC-like and layered codebases. The detection mechanism supports clean, layered, and hexagonal architectural separations to map layers and evaluate their structural dependencies.

To generate an architecture review report, run an analysis on your repository to map layers with their purpose and allowed dependencies. It outputs a structured assessment identifying boundary violations ready for governance.

You do not strictly need codegraph for validating domain design layering, but it is optionally used for semantic checks. The analysis loads mental-model context to detect architectural layer patterns and assess dependency conformance.

Tight coupling in layered architectures occurs when inner modules depend on outer frameworks, creating brittle systems. It is identified by analyzing repository structure and mental-model context to detect dependency violations across architectural boundaries.