Events describe something that happened. Keep that distinction clear so consumers do not mistake an event notification for a command that can be applied without context.
Name the fact.
Record its identifying fields.
Explain how duplicates are handled.
Choose a useful next step.
Make event-driven work visible from trigger to consequence. Event Stream connects event meaning, consumer expectations and replay decisions so teams can reason about asynchronous behavior.