clean-architecture

Enforce layered architecture by verifying dependencies follow permitted paths: Domain has none, Application depends on Domain, Infrastructure on both, and Api on all lower layers. This prevents cross-layer coupling during feature development and code placement.

Clean architecture dependency rules state the Domain layer has zero dependencies, while the Application layer depends solely on the Domain layer. This ensures handlers, validators, and DTOs remain decoupled from infrastructure frameworks.

To ensure features are implemented within correct layer boundaries, apply governance rules during feature development to verify dependencies follow permitted paths and match layer responsibilities like rich domain models or repository implementations.

Clean architecture does not allow the domain layer to depend on infrastructure frameworks. The domain layer must contain a rich domain model with no framework dependencies, keeping infrastructure concerns isolated in external clients and DI modules.

The best way to structure service layers is using Solution Spec Writer and Execution Planner to load governance rules. This verifies new features follow the Domain, Application, Infrastructure, and Api dependency sequence to prevent leakage.

Avoid strict layered architecture when features require direct cross-layer access outside permitted dependency paths, or when application complexity does not justify separate Domain, Application, Infrastructure, and Api boundary enforcement overhead.