ddd-step1-strategic-design

To identify bounded contexts and aggregates from a business context, you can use strategic Domain-Driven Design analysis. This process maps business language boundaries into structured maps with aggregate roots and canonical artifacts ready for architectural work.

The canonical artifacts generated for system design include system.yaml, system-spec.md, system-diagram.mmd, and AGENTS.md. These files capture bounded contexts, aggregates, and integration contracts for IA agents.

You need strategic DDD for system architecture when designing a new system from scratch or restructuring an existing business description. It transforms business contexts into structured maps of bounded contexts and integration decisions.

Yes, you can use this to restructure an existing system design into bounded contexts. It analyzes the current business description and transforms it into aggregates, integration contracts, and canonical artifacts.

Strategic DDD captures design decisions and integration boundaries by generating a structured, auditable notes section alongside canonical artifacts. This includes specific notes on context, lifecycle, and integration decisions.

The best way to define integration contracts between bounded contexts is by applying strategic DDD to map natural language boundaries. This generates system.yaml and system-spec.md files documenting the contracts and architectural decisions.