2a-layer-boundary-gate

The gate performs AST-based import analysis on Python source files to detect prohibited dependencies, such as use_cases importing infrastructure or presenters importing controllers, ensuring your Clean Architecture layers remain decoupled.

The gate performs AST-based import analysis on Python source files to detect prohibited dependencies, such as use_cases importing infrastructure or presenters importing controllers, ensuring your Clean Architecture layers remain decoupled.

Yes, the gate supports CI integration by automatically checking Python imports, writing findings to a docs/todo.md report, and returning a non-zero exit code when critical layer-boundary violations are detected.

The gate applies to Python projects organized under Clean Architecture, requiring standard directories for entities, use_cases, gateways, controllers, presenters, and infrastructure to accurately map and validate dependencies.

The gate generates or updates a docs/todo.md file with detailed findings of prohibited imports, providing a persistent report of layer-boundary violations while returning a non-zero exit code to prompt immediate repair.

The gate returns a non-zero exit code when it detects critical layer-boundary violations, such as forbidden imports between entities, use_cases, gateways, and infrastructure, to halt pipelines and prompt code repair.