Implementation
Implementation Notes for Replay-Safe Event Identifiers
Event identifiers that stay stable across retries and replays let deduplication, auditing, and recovery agree on what actually happened once.
A retry with a fresh identifier is indistinguishable from a new request. Identifier discipline is what lets the system tell one intent from two.
Identifier rules
- Derive ids from intent content, not from send time.
- Preserve the original id in every retry envelope.
- Make consumers idempotent on id, not on payload equality.
Use the audit schema, blackboard schema, and examples to keep one identifier per intent across every retry and replay.