# noCV engineering task library Content version 5 Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs. Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence. ## FLEET — A dispatch map that does not invent certainty 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. **Field:** Real-time systems. **Suggested stack:** TypeScript, React, MapLibre, Node.js, PostgreSQL. **Engineer value:** Practice geospatial boundaries, stream ordering, snapshot recovery, and concurrent operational commands. **Company value:** Inspect whether a developer keeps dispatch decisions grounded in current authorized data and exposes uncertainty during outages. **Delivery agreement:** Use a fixed synthetic depot and replayable location traces. Each ticket is independently bounded by its declared prerequisites. ### Setup prerequisites - Synthetic vehicle telemetry with device sessions and sequence numbers - Dispatch assignment and authorized region API contracts ### Establish a truthful map Validate coordinates and show age and identity clearly. #### FLEET-101 — Keep invalid coordinates from appearing as real vans **Bug · High priority · Foundational** noCV practice brief v5 · FLEET-101 · A dispatch map that does not invent certainty Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Establish a truthful map. Depends on: No preceding ticket. Difficulty: Foundational. Estimated focused work: 75 minutes; setup and prerequisite tickets are additional. Estimated field mix: Data engineering 40% · Real-time systems 30% · Frontend 30%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. Missing coordinates are coerced to zero, placing a depot van in the ocean. Validate telemetry before rendering and explain vehicles with no usable position. Acceptance criteria - Latitude and longitude must be finite numeric values within documented geographic bounds. - Missing or rejected position data produces an unknown-location state in the list. - A valid zero coordinate remains valid and is not treated as a missing value. Implementation constraints - Keep vehicle identity separate from location availability; rejecting one fix must not delete the vehicle. Verification - Render valid zero latitude and a normal depot position correctly. - Send null, a numeric string, an out-of-range value, and non-finite coordinates; none becomes a plausible marker. Deliverables - Telemetry coordinate parser and invalid-position fixtures Rollout and recovery: Validate traces before map display; hide invalid markers while retaining unknown-location list rows. Project prerequisites: Synthetic vehicle telemetry with device sessions and sequence numbers Dispatch assignment and authorized region API contracts Engineer value: Practice geospatial boundaries, stream ordering, snapshot recovery, and concurrent operational commands. Company value: Inspect whether a developer keeps dispatch decisions grounded in current authorized data and exposes uncertainty during outages. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. #### FLEET-102 — Show dispatchers how old each vehicle position is **Story · High priority · Foundational** noCV practice brief v5 · FLEET-102 · A dispatch map that does not invent certainty Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Establish a truthful map. Depends on: FLEET-101. Difficulty: Foundational. Estimated focused work: 75 minutes; setup and prerequisite tickets are additional. Estimated field mix: Real-time systems 60% · Frontend 40%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. A van’s last position remains bright green after its device disconnects. Dispatch assigns a nearby job using a point that is twenty minutes old. Acceptance criteria - Map and list expose last accepted fix time and age. - Positions move through configured fresh, stale, and unknown states without requiring a new event. - Device timestamps outside the allowed clock-skew range cannot make a position appear indefinitely fresh. Implementation constraints - Use a controllable clock and text labels as well as visual styling. Verification - Advance the clock past both freshness thresholds and verify map/list agreement. - Send a future-dated fix and disconnect the stream; no false current label remains. Deliverables - Position freshness policy and fake-clock UI checks Rollout and recovery: Release age labels before assignment features; disable freshness coloring if timestamp authority is uncertain. Project prerequisites: Synthetic vehicle telemetry with device sessions and sequence numbers Dispatch assignment and authorized region API contracts Engineer value: Practice geospatial boundaries, stream ordering, snapshot recovery, and concurrent operational commands. Company value: Inspect whether a developer keeps dispatch decisions grounded in current authorized data and exposes uncertainty during outages. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. #### FLEET-103 — Fit selected vehicles without zooming out across the entire planet **Bug · Medium priority · Intermediate** noCV practice brief v5 · FLEET-103 · A dispatch map that does not invent certainty Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Establish a truthful map. Depends on: FLEET-101. Difficulty: Intermediate. Estimated focused work: 120 minutes; setup and prerequisite tickets are additional. Estimated field mix: Frontend 100%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. A synthetic depot near the date line has vans at longitudes 179.8 and -179.7. Fit selection zooms to the whole world because the bounding box takes the long route. Acceptance criteria - Viewport fitting chooses the intended minimal longitude span for the selected valid points. - One-point and empty selections use documented zoom/fallback behavior. - Unknown-location vehicles remain listed but do not distort geographic bounds. Implementation constraints - Bound this task to viewport fitting; route calculation and global projection replacement are excluded. Verification - Fit points on both sides of the date line and verify a local view contains both. - Fit an empty selection, one point, and a mix containing invalid fixes; no invalid bounds or extreme zoom occurs. Deliverables - Dateline-aware bounds helper and geographic edge-case fixtures Rollout and recovery: Enable for selection fitting only; retain a manual reset-to-depot control if bounds calculation fails. Project prerequisites: Synthetic vehicle telemetry with device sessions and sequence numbers Dispatch assignment and authorized region API contracts Engineer value: Practice geospatial boundaries, stream ordering, snapshot recovery, and concurrent operational commands. Company value: Inspect whether a developer keeps dispatch decisions grounded in current authorized data and exposes uncertainty during outages. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. ### Reconcile live telemetry Handle device ordering and reconnect boundaries. #### FLEET-104 — Prevent delayed telemetry from moving a van backwards **Bug · High priority · Advanced** noCV practice brief v5 · FLEET-104 · A dispatch map that does not invent certainty Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Reconcile live telemetry. Depends on: FLEET-102. Difficulty: Advanced. Estimated focused work: 150 minutes; setup and prerequisite tickets are additional. Estimated field mix: Real-time systems 70% · Data engineering 30%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. A device buffers updates through a tunnel, then sends them out of order. The marker jumps to an older point and the arrival-age label resets incorrectly. Acceptance criteria - Per-device session and sequence identify whether a fix advances accepted position. - Duplicates and earlier fixes do not replace current position or refresh its age. - A new device session follows an explicit reset/authority policy rather than comparing unrelated sequence counters. Implementation constraints - Arrival time alone cannot establish device order; keep bounded diagnostics for rejected categories. Verification - Deliver sequence 40, 42, 41, and 42 again; accepted position remains at 42. - Restart the device session with sequence 1 and replay an old-session fix; the documented session policy chooses one authority. Deliverables - Device-session telemetry reducer and reordered-trace tests Rollout and recovery: Replay fixed traces before live pilot; freeze a device at its last confirmed fix when session authority is ambiguous. Project prerequisites: Synthetic vehicle telemetry with device sessions and sequence numbers Dispatch assignment and authorized region API contracts Engineer value: Practice geospatial boundaries, stream ordering, snapshot recovery, and concurrent operational commands. Company value: Inspect whether a developer keeps dispatch decisions grounded in current authorized data and exposes uncertainty during outages. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. #### FLEET-105 — Reconnect the map without losing updates between snapshot and stream **Task · High priority · Expert** noCV practice brief v5 · FLEET-105 · A dispatch map that does not invent certainty Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Reconcile live telemetry. Depends on: FLEET-103, FLEET-104. Difficulty: Expert. Estimated focused work: 210 minutes; setup and prerequisite tickets are additional. Estimated field mix: Real-time systems 60% · Distributed systems 40%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. The dashboard downloads a vehicle snapshot and opens the live stream afterward. Updates during that gap never arrive, so a van appears stale until its next fix. Acceptance criteria - The snapshot supplies an authorized region identity and exact stream watermark. - Buffered or replayed events after that watermark apply once after snapshot installation. - Expired watermarks, buffer overflow, and mismatched region data trigger explicit resync rather than a partial-current view. Implementation constraints - Document the snapshot/replay boundary contract; use a bounded buffer and synthetic trace harness. Verification - Inject movement during snapshot loading and confirm the final position includes it exactly once. - Expire the watermark and switch region during recovery; no mixed-region positions or falsely current state appears. Deliverables - Snapshot/stream handoff protocol and gap-recovery harness Rollout and recovery: Pilot with forced reconnects; keep the map visibly stale and commands disabled until a coherent snapshot is installed. Project prerequisites: Synthetic vehicle telemetry with device sessions and sequence numbers Dispatch assignment and authorized region API contracts Engineer value: Practice geospatial boundaries, stream ordering, snapshot recovery, and concurrent operational commands. Company value: Inspect whether a developer keeps dispatch decisions grounded in current authorized data and exposes uncertainty during outages. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. ### Support operational decisions Keep assignments, filters, and access consistent. #### FLEET-106 — Resolve competing dispatch assignments explicitly **Bug · High priority · Advanced** noCV practice brief v5 · FLEET-106 · A dispatch map that does not invent certainty Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Support operational decisions. Depends on: FLEET-105. Difficulty: Advanced. Estimated focused work: 165 minutes; setup and prerequisite tickets are additional. Estimated field mix: Real-time systems 40% · Backend 30% · Frontend 30%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. Two dispatchers assign the same van to different pickup jobs. Both dashboards show success until a refresh reveals the losing assignment disappeared. Acceptance criteria - Assignment commands include expected van/job revision and a stable operation key. - Only the server-confirmed assignment becomes authoritative in map and list. - A competing change shows the current assignment and preserves the unsubmitted alternative for an explicit decision. Implementation constraints - Use conditional updates at the repository boundary; stale location is shown as context, not assumed current availability. Verification - Assign a free van and verify map/list share the confirmed revision. - Race two dispatchers and lose one acknowledgement; one assignment wins, retries do not duplicate it, and the conflict is visible. Deliverables - Revision-aware dispatch command and concurrent-assignment tests Rollout and recovery: Enable for one synthetic depot after replay checks; disable assignment writes if confirmed map/list state diverges. Project prerequisites: Synthetic vehicle telemetry with device sessions and sequence numbers Dispatch assignment and authorized region API contracts Engineer value: Practice geospatial boundaries, stream ordering, snapshot recovery, and concurrent operational commands. Company value: Inspect whether a developer keeps dispatch decisions grounded in current authorized data and exposes uncertainty during outages. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. #### FLEET-107 — Keep map, list, and counts on the same filtered vehicle set **Bug · Medium priority · Intermediate** noCV practice brief v5 · FLEET-107 · A dispatch map that does not invent certainty Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Support operational decisions. Depends on: FLEET-102, FLEET-106. Difficulty: Intermediate. Estimated focused work: 105 minutes; setup and prerequisite tickets are additional. Estimated field mix: Frontend 60% · Real-time systems 20% · Accessibility 20%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. Filtering to Unassigned removes map markers but leaves assigned vans in the keyboard list. The count in the toolbar then disagrees with both. 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 - 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. Project prerequisites: Synthetic vehicle telemetry with device sessions and sequence numbers Dispatch assignment and authorized region API contracts Engineer value: Practice geospatial boundaries, stream ordering, snapshot recovery, and concurrent operational commands. Company value: Inspect whether a developer keeps dispatch decisions grounded in current authorized data and exposes uncertainty during outages. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. #### FLEET-108 — Remove out-of-region location data when dispatch scope changes **Task · High priority · Advanced** noCV practice brief v5 · FLEET-108 · A dispatch map that does not invent certainty Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Support operational decisions. Depends on: FLEET-105, FLEET-106. Difficulty: Advanced. Estimated focused work: 150 minutes; setup and prerequisite tickets are additional. Estimated field mix: Security 40% · Real-time systems 30% · Privacy engineering 30%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. A dispatcher moves from North depot coverage to East, but an existing stream continues delivering North vehicle coordinates. Hidden markers remain in the browser store. Acceptance criteria - Subscriptions and snapshot queries enforce current authorized region at the service boundary. - Scope changes close old delivery, clear disallowed cached positions, and reconcile a new authorized snapshot. - Diagnostics contain safe event categories and IDs, not raw coordinate trails or personal driver details. Implementation constraints - Use synthetic fleet data and do not add employee behavior scores or continuous personal-device tracking. Verification - Switch from North to East and verify only authorized East vehicles remain in storage and presentation. - Queue an old-region event during scope revocation; reject it after the documented barrier and deny a forged region query. Deliverables - Region-scoped delivery lifecycle and cross-region denial tests Rollout and recovery: Require this before multi-depot pilots; close all location streams when current scope cannot be established. Project prerequisites: Synthetic vehicle telemetry with device sessions and sequence numbers Dispatch assignment and authorized region API contracts Engineer value: Practice geospatial boundaries, stream ordering, snapshot recovery, and concurrent operational commands. Company value: Inspect whether a developer keeps dispatch decisions grounded in current authorized data and exposes uncertainty during outages. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. ### Bound and rehearse the system Maintain responsiveness and verify failure recovery. #### FLEET-109 — Coalesce position rendering without dropping dispatch events **Task · High priority · Expert** noCV practice brief v5 · FLEET-109 · A dispatch map that does not invent certainty Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Bound and rehearse the system. Depends on: FLEET-104, FLEET-107, FLEET-108. Difficulty: Expert. Estimated focused work: 210 minutes; setup and prerequisite tickets are additional. Estimated field mix: Performance engineering 50% · Real-time systems 30% · Frontend 20%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. A replay of 500 vans updating twice a second freezes the browser. Dropping every other message improved drawing but also lost assignment changes. Acceptance criteria - Position drawing may coalesce to the newest accepted fix per vehicle within a bounded frame window. - Assignment, authorization, and removal events follow their full ordered state path and are never discarded as visual updates. - A reproducible load profile records input rate, render frequency, memory bound, and keyboard interaction latency. Implementation constraints - Separate authoritative state reduction from rendering cadence; use synthetic bounded traces. Verification - Replay the agreed 500-vehicle trace and measure the documented interaction budget. - Interleave assignment, region removal, and position bursts; all nonvisual state transitions apply and removed vehicles do not reappear. Deliverables - Render coalescing scheduler and mixed-event load report Rollout and recovery: Canary with conservative draw limits; reduce displayed live density or use the list if interaction budgets fail, preserving command state. Project prerequisites: Synthetic vehicle telemetry with device sessions and sequence numbers Dispatch assignment and authorized region API contracts Engineer value: Practice geospatial boundaries, stream ordering, snapshot recovery, and concurrent operational commands. Company value: Inspect whether a developer keeps dispatch decisions grounded in current authorized data and exposes uncertainty during outages. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. #### FLEET-110 — Rehearse a depot outage before enabling live dispatch **Chore · High priority · Intermediate** noCV practice brief v5 · FLEET-110 · A dispatch map that does not invent certainty Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Bound and rehearse the system. Depends on: FLEET-105, FLEET-106, FLEET-108, FLEET-109. Difficulty: Intermediate. Estimated focused work: 120 minutes; setup and prerequisite tickets are additional. Estimated field mix: Real-time systems 40% · Site reliability 30% · Quality engineering 30%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. Dispatch needs to know what remains usable when telemetry stops but assignment storage still works. Write a fixed-data outage rehearsal and an operator decision note. Acceptance criteria - The rehearsal separates telemetry outage, assignment-store outage, and authorization outage. - Every scenario records visible freshness, permitted actions, and recovery state. - The note defines safe fallback actions and states that synthetic replay is not proof of real fleet readiness. Implementation constraints - Do not send real dispatch commands or connect to personal/production location feeds. Verification - Stop telemetry, advance the clock, and recover by snapshot; stale labels and final positions match the trace. - Fail assignment storage and then authorization during a pending command; show no false success and close delivery when scope is unknown. Deliverables - Depot outage rehearsal and dispatch operator runbook Rollout and recovery: Require a reviewed rehearsal for pilot use; pause live dispatch when authority or assignment confirmation is unavailable. Project prerequisites: Synthetic vehicle telemetry with device sessions and sequence numbers Dispatch assignment and authorized region API contracts Engineer value: Practice geospatial boundaries, stream ordering, snapshot recovery, and concurrent operational commands. Company value: Inspect whether a developer keeps dispatch decisions grounded in current authorized data and exposes uncertainty during outages. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence.