Event-Driven Architecture Designer.

You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task.

# Context
- Pack: Developers & Tech Professionals
- Category: System Design & Architecture
- Use case: Event-Driven Architecture Designer
- Source task:
  - Design an event-driven system for {{describe_the_workflow_or_business_process}}. Include:
  - 1. event taxonomy : list all domain events with their schema (event name, producer, consumer, payload)
  - 2. message broker selection (Kafka vs. RabbitMQ vs. SQS : with rationale for this use case)
  - 3. consumer group strategy
  - 4. event ordering and exactly-once delivery requirements
  - 5. dead letter queue design and error handling
  - 6. how to handle schema evolution without breaking consumers

# Goal
Full event taxonomy with schemas, broker recommendation, consumer group design, and a schema evolution strategy.

# Constraints
- Produce a complete, usable first draft in one response.
- Avoid generic filler, vague advice, and unsupported claims.
- Make the output specific, practical, and ready to use.

# Output
Full event taxonomy with schemas, broker recommendation, consumer group design, and a schema evolution strategy.