Producer ownership
The team that owns the state transition owns the event meaning and compatibility decision.
The event backbone separates business meaning from delivery behaviour. Producers own typed facts; consumers own routing, processing state, retry and replay.
The producer owns the event schema. Consumers own offsets, retries, idempotency and dead letters without redefining what the event means.
A broker cannot create exactly-once business meaning. Transactional publication at the producer and idempotent effects at the consumer do that work.
A durable envelope lets a consumer reject incompatibility, deduplicate delivery, reconstruct causality and choose the correct interpretation during replay.
The team that owns the state transition owns the event meaning and compatibility decision.
Compatibility fixtures distinguish additive change, supported version transition and breaking meaning change.
Publish and consume grants are scoped by resource and identity; a topic name is not an authorisation system.
Consumers own subscriptions and filters. Producers do not encode a list of downstream workflows.
A replay names range, schema interpretation, destination and deduplication policy before it starts.
The original evidence, failure reason and redrive decision remain inspectable rather than disappearing into logs.
At-least-once delivery is handled deliberately. A consumer records the stable event identity with its effect, or uses an equivalent atomic boundary, so a retried delivery is observable but harmless.