Keep map, list, and counts on the same filtered vehicle set
Filtering to Unassigned removes map markers but leaves assigned vans in the keyboard list. The count in the toolbar then disagrees with both.
- Focused work estimate
- 1h 45m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Derived state · Accessibility · Real-time UI
Estimated field mix
- Frontend60%
- Real-time systems20%
- Accessibility20%
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 Cedar delivery depot dispatches vans through a browser map and accessible list. Synthetic telemetry arrives through a gateway with device sequence numbers. This is operational fleet software practice; no real driver tracking, employee scoring, or routing safety guarantee is part of the project.
Setup prerequisites
- Synthetic vehicle telemetry with device sessions and sequence numbers
- Dispatch assignment and authorized region API contracts
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- FLEET-101 · Keep invalid coordinates from appearing as real vans
- FLEET-102 · Show dispatchers how old each vehicle position is
- FLEET-103 · Fit selected vehicles without zooming out across the entire planet
- FLEET-104 · Prevent delayed telemetry from moving a van backwards
- FLEET-105 · Reconnect the map without losing updates between snapshot and stream
- FLEET-106 · Resolve competing dispatch assignments explicitly
Acceptance criteria
- One derived selection drives map IDs, list rows, and count.
- A live assignment change updates all representations without silently retargeting the selected van.
- If a selected van leaves the filter, the interface explains why and offers a deliberate clear-filter action.
Implementation constraints
- Maintain an accessible list as an operational alternative to the map.
Verification to include
- Filter unassigned vehicles and compare IDs across map, list, and count.
- Assign the selected vehicle remotely while keyboard focus is on its row; selection is explained and focus is not lost.
Deliverables
- Shared filtered projection and map/list consistency tests
Rollout and recovery
Enable shared projection for one filter first; fall back to the authoritative list if map selection behavior regresses.
Value of the work
For the engineer: Practice geospatial boundaries, stream ordering, snapshot recovery, and concurrent operational commands.
For the team: Inspect whether a developer keeps dispatch decisions grounded in current authorized data and exposes uncertainty during outages.
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.