ts-ddd-bounded-contextlisted

# Bounded Context Mapper — TypeScript DDD Produce a structured domain map that gives the team a shared understanding of where responsibilities live, how contexts relate, and what language each context owns. ## Process (follow in order) ### 1. Extract domain concepts From the user's description, identify and list: - **Nouns** → candidate Entities and Value Objects - **Verbs** → candidate Domain Events and Commands - **Business rules** → candidate invariants for Aggregates ### 2. Group into bounded contexts Cluster concepts that share a ubiquitous language and a clear owner. Each bounded context should: - Have a single team or module owning it - Have a name that domain experts recognize - Be cohesive — the language inside it doesn't leak to other contexts ### 3. Define relationships For each pair of interacting contexts, name the relationship pattern: | Pattern | When to use | |---------|-------------| | **Shared Kernel** | Two contexts share a small, stable subset of the model | | **Customer/Supplier** | One context consumes another's output; upstream is the supplier | | **Conformist** | Downstream adapts entirely to upstream's model | | **Anti-Corruption Layer (ACL)** | Downstream translates upstream's model to protect its own language | | **Open Host Service** | Upstream publishes a stable, versioned API for many consumers | | **Published Language** | Shared data format (e.g. events on a bus) both sides agree on | | **Partnership** | Two contexts evolve together wit