fort-knox-component-architecture

Domain-driven design separates business logic into bounded contexts, while clean architecture layers enforce dependency rules between domain use cases, repositories, and external adapters. This separation prevents domain logic leakage and keeps business rules isolated from technical plumbing.

Place use cases in domain/use_cases for business flow orchestration, strategies in domain/strategies for interchangeable logic, and repositories in domain/repositories for data access. Adapters and external calls go in the adapters layer, while services handle technical plumbing.

Separate concerns when creating new components or adding use cases, repositories, adapters, or services. Defining clear public, domain, adapters, and services boundaries prevents logic mixing and enforces consistent architectural rules across the codebase.

A use case orchestrates business flows, whereas a strategy provides interchangeable logic. Both belong in the domain layer but serve distinct purposes within the component architecture.

Yes, this architecture guidance applies when adding new use cases, repositories, adapters, or services to an existing codebase. It enforces a consistent folder layout and boundary rules across both new and existing modular components.