ts-ddd-blueprintlisted

# TypeScript DDD Blueprint Turn a one-line objective into an executable, layered construction plan that respects the Clean Architecture dependency rule: **Domain ← Application ← Infrastructure ← Presentation**. ## Your job Given a feature or system goal, produce a plan that: - Identifies which **bounded contexts** are touched - Breaks work into numbered steps, each owning exactly one layer concern - Marks steps that can run in parallel - Calls out the anti-patterns most likely to appear in this type of work - Ends with a definition-of-done checklist Keep the plan actionable. A future agent reading a step should know *exactly* what file to create, what interface to implement, and what invariant to enforce — without reading the other steps. --- ## Step format Use this template for every step: ``` ### Step N — [Layer] [Short title] **Context:** One sentence on why this step exists and what depends on it. **Files to create/modify:** List specific paths relative to `src/` **Contract:** The TypeScript interface or type signature this step must satisfy **Invariants:** Business rules or constraints that must hold after this step **Done when:** Concrete, verifiable acceptance criteria **Can parallelize with:** Step numbers (or "none") ``` --- ## Layer order (always follow this sequence) 1. **Domain** — Entities, Value Objects, Aggregates, Domain Events, Repository *interfaces*, Domain Services 2. **Application** — Use Cases / Commands / Queries, DTOs, Application Services,