nw-ddd-event-modelinglisted

# Event Modeling Collaborative visual design technique created by Adam Dymitruk. The Event Model IS the specification -- it replaces traditional requirements documents with a single, living visual artifact. ## Key Properties - **Collaborative**: Everyone participates (devs, business, UX) - **Visual**: Colored elements on a timeline (physical or digital board) - **Timeline-based**: Events arranged chronologically, left to right - **Spec-generating**: Model directly produces testable Given/When/Then specifications - **Technology-agnostic**: Describes WHAT happens, not HOW it's implemented ## The Color System | Color | Element | Description | Example | |-------|---------|-------------|---------| | Orange | **Event** | Something that happened (past tense) | OrderPlaced, PaymentReceived | | Blue | **Command** | User intent/action (imperative) | PlaceOrder, ProcessPayment | | Green | **Read Model/View** | Data displayed to user | Order Summary, Shipping Dashboard | | White | **Screen/UI** | User interface wireframe | Order Form, Checkout Page | | Yellow | **Automation/Policy** | System reaction (saga/process manager) | "When PaymentReceived, then ConfirmOrder" | | Red | **External System** | Integration point | Payment Gateway, Email Service | ## Four Phases ### Phase 1: Event Brainstorming (10-20 min) Discover all meaningful things that happen in the system. **Process**: Everyone writes events on orange stickies (past tense, domain language) | Place on timeline (left = ea