Show the difference between connected and caught up
The room shows Connected immediately after a socket opens, even while the last five minutes of events are still missing. Give connection and synchronization separate states.
- Focused work estimate
- 1h 15m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- State modeling · Real-time UX · Recovery
Estimated field mix
- Real-time systems60%
- Frontend40%
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
The fictional Harbor operations team coordinates synthetic incidents in a shared room. Engineers post status notes and claim response tasks while connections come and go. Scope is one application gateway, a durable room event store, and fixture clients; alert paging and external chat delivery are excluded.
Setup prerequisites
- Room membership and command contracts
- Synthetic incident events and a controllable transport harness
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- The UI distinguishes connecting, recovering, current, disconnected, and unavailable.
- Current appears only after the server-defined replay boundary has been applied.
- The latest confirmed timeline remains readable during reconnect with a visible freshness notice.
Implementation constraints
- Use a deterministic transport fixture; socket open alone is not proof of complete room state.
Verification to include
- Open a connection and delay replay completion; the room stays recovering until the boundary arrives.
- Disconnect after a confirmed note and fail reconnect; the note remains readable but is not labeled current.
Deliverables
- Room connection/sync state model and delayed-replay UI test
Rollout and recovery
Enable state labels in the pilot room; force read-only mode if synchronization cannot be established.
Value of the work
For the engineer: Practice event identity, ordering, replay, authorization, and bounded backpressure in one understandable system.
For the team: Inspect how an engineer keeps collaborative state trustworthy during failures without relying on optimistic success messages.
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.