# 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. ## CROUTE — An offline field-service route notebook Fictional maintenance coordinator Elm dispatches non-safety-critical inspection visits. Implement a mobile application in an emulator with local API stubs; physical devices and credentials are unnecessary. **Field:** Mobile. **Suggested stack:** React Native, TypeScript, SQLite, Emulator. **Engineer value:** Practice durable mobile state and explicit sync conflicts. **Company value:** Inspect how an engineer protects field work during disconnection. **Delivery agreement:** Use synthetic notes and emulator runs; no location tracking or real dispatch. ### Setup prerequisites - Create synthetic visits and a local sync adapter. - Provide controllable connectivity and process-restart simulation. ### Make visits readable Define local visit state. #### CROUTE-101 — Label route-note timestamps with their actual zone **Bug · Medium priority · Foundational** noCV practice brief v5 · CROUTE-101 · An offline field-service route notebook Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Make visits readable. Depends on: No preceding ticket. Difficulty: Foundational. Estimated focused work: 60 minutes; setup and prerequisite tickets are additional. Estimated field mix: Mobile 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. Visit notes appear an hour early after an emulator zone change. Distinguish stored instants from displayed local times. Acceptance criteria - Instants remain UTC - Display identifies zone - Invalid timestamps show unavailable Implementation constraints - Inject time and zone in tests. Verification - Change emulator zone - Render malformed timestamp Deliverables - Timestamp formatter and cases Rollout and recovery: Restore UTC display if local conversion fails. Project prerequisites: Create synthetic visits and a local sync adapter. Provide controllable connectivity and process-restart simulation. Engineer value: Practice durable mobile state and explicit sync conflicts. Company value: Inspect how an engineer protects field work during disconnection. 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. #### CROUTE-102 — Show downloaded visits when route refresh fails **Story · High priority · Foundational** noCV practice brief v5 · CROUTE-102 · An offline field-service route notebook Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Make visits readable. Depends on: No preceding ticket. Difficulty: Foundational. Estimated focused work: 75 minutes; setup and prerequisite tickets are additional. Estimated field mix: Mobile 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. An offline refresh replaces the route with an empty screen. Retain downloaded visits and identify staleness. Acceptance criteria - Cached visits remain visible - Last sync time appears - Retry does not delete cache Implementation constraints - Distinguish empty success from network failure. Verification - Load cached route offline - Return successful empty route Deliverables - Route loading states Rollout and recovery: Disable refresh clearing if cache disappears. Project prerequisites: Create synthetic visits and a local sync adapter. Provide controllable connectivity and process-restart simulation. Engineer value: Practice durable mobile state and explicit sync conflicts. Company value: Inspect how an engineer protects field work during disconnection. 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. #### CROUTE-103 — Persist field-note edits before leaving a visit **Bug · High priority · Intermediate** noCV practice brief v5 · CROUTE-103 · An offline field-service route notebook Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Make visits readable. Depends on: CROUTE-101, CROUTE-102. Difficulty: Intermediate. Estimated focused work: 120 minutes; setup and prerequisite tickets are additional. Estimated field mix: Mobile 60% · Database engineering 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. Back navigation occasionally loses the last sentence. Commit local edits before acknowledging navigation. Acceptance criteria - Confirmed save survives restart - Failed writes retain editor - Navigation explains unresolved persistence Implementation constraints - Use a local transaction, not delayed component state. Verification - Save then restart - Inject storage failure on Back Deliverables - Durable draft write and restart cases Rollout and recovery: Prevent exit with unsaved changes until repaired. Project prerequisites: Create synthetic visits and a local sync adapter. Provide controllable connectivity and process-restart simulation. Engineer value: Practice durable mobile state and explicit sync conflicts. Company value: Inspect how an engineer protects field work during disconnection. 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. ### Protect offline work Persist notes and resolve conflicts. #### CROUTE-104 — Queue field-note synchronization by immutable operation ID **Task · High priority · Advanced** noCV practice brief v5 · CROUTE-104 · An offline field-service route notebook Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Protect offline work. Depends on: CROUTE-103. Difficulty: Advanced. Estimated focused work: 180 minutes; setup and prerequisite tickets are additional. Estimated field mix: Mobile 40% · Database engineering 30% · Distributed systems 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. The same offline note uploads twice after a timeout. Persist an operation ID alongside each queued change. Acceptance criteria - Retries reuse ID - Accepted changes leave queue atomically - New edits create new operations Implementation constraints - Server stub must deduplicate operations. Verification - Replay accepted upload - Crash after acceptance before dequeue Deliverables - Sync queue and replay tests Rollout and recovery: Pause uploading without deleting queued work. Project prerequisites: Create synthetic visits and a local sync adapter. Provide controllable connectivity and process-restart simulation. Engineer value: Practice durable mobile state and explicit sync conflicts. Company value: Inspect how an engineer protects field work during disconnection. 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. #### CROUTE-105 — Preserve conflicting offline visit notes for explicit resolution **Story · High priority · Advanced** noCV practice brief v5 · CROUTE-105 · An offline field-service route notebook Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Protect offline work. Depends on: CROUTE-104. Difficulty: Advanced. Estimated focused work: 180 minutes; setup and prerequisite tickets are additional. Estimated field mix: Mobile 50% · Distributed systems 50%. 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 emulators edit one visit offline and last-write-wins removes a paragraph. Surface both revisions. Acceptance criteria - Conflict preserves both texts - No silent merge occurs - Resolution creates a new revision Implementation constraints - Synthetic notes only; omit content from logs. Verification - Resolve two independent drafts - Reject a stale resolution revision Deliverables - Conflict screen and revision cases Rollout and recovery: Keep conflicts read-only while resolver is repaired. Project prerequisites: Create synthetic visits and a local sync adapter. Provide controllable connectivity and process-restart simulation. Engineer value: Practice durable mobile state and explicit sync conflicts. Company value: Inspect how an engineer protects field work during disconnection. 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. #### CROUTE-106 — Resume route-note upload after application termination **Bug · High priority · Expert** noCV practice brief v5 · CROUTE-106 · An offline field-service route notebook Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Protect offline work. Depends on: CROUTE-104. Difficulty: Expert. Estimated focused work: 240 minutes; setup and prerequisite tickets are additional. Estimated field mix: Mobile 50% · Distributed systems 30% · Site reliability 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. Killing the process mid-sync leaves operations marked Sending forever. Add a recoverable lease state. Acceptance criteria - Expired sends return to retryable - Active leases avoid duplicate work - Attempt count is bounded Implementation constraints - Use an injected monotonic lease clock. Verification - Restart after expired lease - Restart before lease expiry Deliverables - Lease recovery and crash schedule Rollout and recovery: Pause runner and retain durable queue. Project prerequisites: Create synthetic visits and a local sync adapter. Provide controllable connectivity and process-restart simulation. Engineer value: Practice durable mobile state and explicit sync conflicts. Company value: Inspect how an engineer protects field work during disconnection. 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. #### CROUTE-107 — Remove downloaded visit attachments without deleting notes **Task · Medium priority · Intermediate** noCV practice brief v5 · CROUTE-107 · An offline field-service route notebook Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Protect offline work. Depends on: CROUTE-102, CROUTE-103. Difficulty: Intermediate. Estimated focused work: 120 minutes; setup and prerequisite tickets are additional. Estimated field mix: Storage systems 60% · Mobile 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. Attachment cache consumes emulator storage. Add per-visit cleanup that preserves authored drafts. Acceptance criteria - Cleanup targets downloaded blobs - Notes and queue remain intact - Failed deletion reports reclaim uncertainty Implementation constraints - Separate cache paths from draft storage. Verification - Clean one visit - Fail blob removal and inspect notes Deliverables - Cache cleanup and isolation cases Rollout and recovery: Disable cleanup if protected paths overlap. Project prerequisites: Create synthetic visits and a local sync adapter. Provide controllable connectivity and process-restart simulation. Engineer value: Practice durable mobile state and explicit sync conflicts. Company value: Inspect how an engineer protects field work during disconnection. 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. ### Recover interruptions Bound retries and explain sync outcomes. #### CROUTE-108 — Bound offline route-note retry backoff **Chore · Medium priority · Intermediate** noCV practice brief v5 · CROUTE-108 · An offline field-service route notebook Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Recover interruptions. Depends on: CROUTE-106. Difficulty: Intermediate. Estimated focused work: 105 minutes; setup and prerequisite tickets are additional. Estimated field mix: Mobile 60% · Site reliability 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 disconnected emulator retries uploads continuously and drains resources. Add capped backoff with manual retry semantics. Acceptance criteria - Delays grow to cap - Connectivity recovery can wake once - Manual retry cannot create parallel senders Implementation constraints - Inject timers; avoid wall-clock sleeps in tests. Verification - Observe scheduled delays - Toggle connectivity repeatedly Deliverables - Retry scheduler and fake-clock tests Rollout and recovery: Stop automatic retries and expose manual sync. Project prerequisites: Create synthetic visits and a local sync adapter. Provide controllable connectivity and process-restart simulation. Engineer value: Practice durable mobile state and explicit sync conflicts. Company value: Inspect how an engineer protects field work during disconnection. 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. #### CROUTE-109 — Explain partial route synchronization per visit **Story · Medium priority · Intermediate** noCV practice brief v5 · CROUTE-109 · An offline field-service route notebook Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Recover interruptions. Depends on: CROUTE-105, CROUTE-108. Difficulty: Intermediate. Estimated focused work: 120 minutes; setup and prerequisite tickets are additional. Estimated field mix: Mobile 80% · API design 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 global Sync complete banner hides a failed visit. Show per-visit pending, conflicted, and acknowledged states. Acceptance criteria - Global summary counts unresolved visits - Each failure has action - Success follows acknowledgement Implementation constraints - Do not infer sync from an empty in-memory queue. Verification - Sync mixed outcomes - Restart with persisted pending work Deliverables - Sync summary and recovery checks Rollout and recovery: Hide global success if summaries disagree. Project prerequisites: Create synthetic visits and a local sync adapter. Provide controllable connectivity and process-restart simulation. Engineer value: Practice durable mobile state and explicit sync conflicts. Company value: Inspect how an engineer protects field work during disconnection. 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. #### CROUTE-110 — Export a synthetic field-note recovery bundle deliberately **Chore · Low priority · Advanced** noCV practice brief v5 · CROUTE-110 · An offline field-service route notebook Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Recover interruptions. Depends on: CROUTE-106, CROUTE-109. Difficulty: Advanced. Estimated focused work: 150 minutes; setup and prerequisite tickets are additional. Estimated field mix: Privacy engineering 60% · Mobile 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. Debugging a stuck route requires durable state without sharing account tokens. Provide a previewed local recovery bundle. Acceptance criteria - Includes operation metadata - Excludes tokens and attachment bytes - User explicitly includes note text Implementation constraints - Default export omits note bodies. Verification - Export default bundle - Verify secret-like fixture text is absent Deliverables - Bundle schema and redaction cases Rollout and recovery: Remove export if exclusions fail. Project prerequisites: Create synthetic visits and a local sync adapter. Provide controllable connectivity and process-restart simulation. Engineer value: Practice durable mobile state and explicit sync conflicts. Company value: Inspect how an engineer protects field work during disconnection. 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.