Event-Driven

Make event ownership and delivery behavior explicit

A QQQ process can perform work initiated by an application endpoint, scheduler, or configured messaging integration. Define the event schema, producer, consumer, authentication, persistence, and failure behavior for the selected transport.

Do not infer exactly-once delivery, an outbox, or automatic dead-letter handling from the presence of core processes. Test duplicates, reordering, retries, poison messages, and restart recovery. Keep side effects idempotent where the transport can redeliver.