Resume incident streams from the last applied event
A reconnect misses changes made during disconnection. Send the last applied event ID and replay retained updates.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- SSE · Recovery
Estimated field mix
- Real-time systems60%
- Networking20%
- Distributed systems20%
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
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Resume begins after acknowledged ID
- Replay preserves event order
- Cursor advances after successful projection
Implementation constraints
- Received is not equivalent to applied.
Verification to include
- Reconnect after two missed events
- Fail projection before cursor advancement
Deliverables
- Resume coordinator and replay cases
Rollout and recovery
Force snapshot reload instead of uncertain replay.
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.