ddd

Domain-Driven Design - Strategic Guide

Persona

Read .claude/roles/architect.md — adopt this profile and follow all its rules.

Activation

This skill activates for high-level domain decisions:

• Splitting into Bounded Contexts
• Defining the Ubiquitous Language
• Creating a new business module
• Analyzing relationships between contexts

Important clarification

Clean Architecture definitions take precedence over DDD tactical definitions.

We use DDD only at the strategic level (domain splitting, language). Tactical patterns (Entities, Use Cases, Gateways, Presenters) follow Clean Architecture.

What we take from DDD	What we do NOT take
Bounded Contexts	Aggregates
Ubiquitous Language	Repositories (we have Gateways)
Context Mapping	Domain Events
Module splitting	Complex Value Objects

---

Bounded Context

"A Bounded Context delimits the applicability of a particular model." — Eric Evans

A Bounded Context = a module in modules/<context-name>/

Each BC is an autonomous package with its own public API.

Identifying a Bounded Context

Signs that a new BC is needed:

• The same term has different meanings depending on context
• A different team could manage this part
• The model is becoming too complex
• Business rules are diverging

ReviewFlow example:

Bounded Context	Responsibility
review	Code review orchestration and result handling
tracking	MR/PR assignment tracking and follow-up
webhook	Inbound webhook processing (GitLab/GitHub)
mcp	Model Context Protocol server and tools
dashboard	Review statistics and visualization
security	Secret detection and access control

---

Communication between Bounded Contexts

BCs communicate via their public APIs, like two independent packages.

// modules/tracking/index.ts (public API)
export { TrackAssignmentUseCase } from "./application/usecases/trackAssignment.usecase"
export { createTrackedMr } from "./domain/factories/trackedMrFactory"
export type { TrackingGateway } from "./application/ports/gateways/trackingGateway"

// modules/review/ imports from the public API
import { TrackAssignmentUseCase } from "@/modules/tracking"