architecture

Enforce a strict layered architecture by defining a 3-layer structure (cli → flows → data) with inner dependencies only. This blueprint guides module organization, naming conventions, and import changes to maintain clear boundaries and prevent cycles.

The correct dependency direction for a cli, flows, and data architecture is strictly inward. The cli layer depends on flows, and flows depends on core or data layers, ensuring dependencies never point outward to prevent structural leakage and cyclic imports.

Use dependency injection to decouple modules in a layered architecture by establishing explicit injection points. This promotes testability and prevents leakage across cli, flows, and data boundaries by injecting dependencies rather than hardcoding imports.

Yes, this layered architecture approach applies to existing code reviews and import changes. It provides practical rules to check module boundaries, verify naming conventions, and ensure proper layering and dependency direction during ongoing development.

The best way to prevent cyclic imports in a 3-layer architecture is to enforce inward-only dependencies and clear module boundaries. Specifying naming conventions and using dependency injection eliminates circular references between the cli, flows, and data layers.