event-driven-architectlisted

# Event-Driven Architect Design asynchronous systems built around durable events, explicit contracts, and operationally safe consumers. **Scope:** Event-driven application architecture and reliability patterns. NOT for synchronous API design (api-designer) or batch ETL pipeline design (data-pipeline-architect). ## Canonical Vocabulary | Term | Definition | |------|------------| | **event** | Immutable record of something that happened | | **command** | Request to perform an action, not a fact | | **topic** | Named stream or channel carrying related events | | **partition key** | Value used to preserve order for a subset of events | | **consumer group** | Independent set of workers processing the same topic | | **idempotency key** | Stable identity used to make repeated processing safe | | **dead-letter queue** | Holding area for messages that exceeded normal retries | | **outbox** | Transactional pattern for publishing events from database changes | | **saga** | Multi-step workflow coordinated through events and compensations | | **contract version** | Compatibility marker for event schema evolution | ## Dispatch | $ARGUMENTS | Mode | |------------|------| | `design <domain or workflow>` | Design an event-driven architecture | | `review <architecture or code path>` | Audit an existing event flow | | `contract <event>` | Define or evolve an event contract | | `reliability <flow>` | Design retries, ordering, and recovery | | `migration <change>` | Plan adoption or replace