Give live incident events stable opaque identifiers
Reconnecting clients cannot distinguish replay from new events because IDs change on delivery. Persist event identity.
- Focused work estimate
- 1h 15m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Event modeling · Identity
Estimated field mix
- Real-time systems60%
- Data engineering40%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
Fictional internal status team Harbor updates operational incident cards. Build a local event log and SSE adapter; incidents and service names are invented.
Setup prerequisites
- Create synthetic incident revisions and a local append-only event stub.
- Provide controllable disconnect, replay and retention fixtures.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Replay preserves IDs
- Distinct events have unique IDs
- IDs contain no incident text
Implementation constraints
- Delivery attempts must not mint new event IDs.
Verification to include
- Replay one event twice
- Append two equal payloads as distinct events
Deliverables
- Event identity contract
Rollout and recovery
Disable replay until stable IDs exist.
Value of the work
For the engineer: Practice event projection, replay and freshness communication.
For the team: Inspect whether dashboards remain trustworthy through network interruptions.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.