# 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. ## FIELD — An offline workday for field technicians The fictional Vale facilities team services equipment in basements with poor reception. Technicians receive assigned work orders, record checks, and attach synthetic equipment photos. The practice app uses an on-device database and a stub sync service; background location tracking is excluded. **Field:** Mobile. **Suggested stack:** React Native, TypeScript, SQLite, Jest, Android emulator. **Engineer value:** Practice durable local state, mobile lifecycle recovery, and conflict resolution in realistic offline workflows. **Company value:** Review whether an engineer can protect field work through crashes, interrupted uploads, and reassignment. **Delivery agreement:** Deliver selected tickets against synthetic work orders. Full project phases are optional and do not require a live dispatch service. ### Setup prerequisites - Synthetic work orders and a revisioned sync contract - An emulator with controllable connectivity and app lifecycle ### Start the offline day Make downloaded work clear and durable. #### FIELD-101 — Tell technicians which work orders are available offline **Story · High priority · Foundational** noCV practice brief v5 · FIELD-101 · An offline workday for field technicians Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Start the offline day. 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. The assignment list looks ready in the depot, but opening a work order downstairs produces an endless spinner. Distinguish listed work from fully downloaded details. Acceptance criteria - Each order states whether required details are cached, downloading, or unavailable offline. - Opening an uncached order offline shows a recoverable explanation. - The app shows the last successful download time without presenting cached data as current. Implementation constraints - Use a connectivity adapter for fixtures; an online signal does not guarantee the API is reachable. Verification - Download an order, disable connectivity, and open its cached details. - Open a listed but uncached order offline and simulate a reachable network with a failed API; neither path spins indefinitely. Deliverables - Offline-availability presentation and connectivity fixture cases Rollout and recovery: Pilot with a small depot dataset; retain read-only cached access if download status regresses. Project prerequisites: Synthetic work orders and a revisioned sync contract An emulator with controllable connectivity and app lifecycle Engineer value: Practice durable local state, mobile lifecycle recovery, and conflict resolution in realistic offline workflows. Company value: Review whether an engineer can protect field work through crashes, interrupted uploads, and reassignment. 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. #### FIELD-102 — Commit a completed checklist item before showing it saved **Bug · High priority · Intermediate** noCV practice brief v5 · FIELD-102 · An offline workday for field technicians Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Start the offline day. Depends on: No preceding ticket. 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. A technician checks Replace intake filter and force-closes the app. On reopening, the check is gone even though the screen showed Saved. Acceptance criteria - Saved appears only after the local transaction commits. - A committed answer survives process termination and reopening. - Database write failure preserves the editable value and clearly marks it unsaved. Implementation constraints - Keep persistence behind a repository boundary; component state alone is not durable. Verification - Commit an answer, terminate the app, and verify the answer after restart. - Inject a database-full error before commit; the UI must not claim success or discard the typed value. Deliverables - Transactional checklist persistence and restart regression test Rollout and recovery: Enable on pilot devices with synthetic work; stop editing if local persistence is unavailable rather than falsely confirming saves. Project prerequisites: Synthetic work orders and a revisioned sync contract An emulator with controllable connectivity and app lifecycle Engineer value: Practice durable local state, mobile lifecycle recovery, and conflict resolution in realistic offline workflows. Company value: Review whether an engineer can protect field work through crashes, interrupted uploads, and reassignment. 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. #### FIELD-103 — Make inspection inputs usable with large text **Task · Medium priority · Foundational** noCV practice brief v5 · FIELD-103 · An offline workday for field technicians Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Start the offline day. Depends on: FIELD-101. Difficulty: Foundational. Estimated focused work: 75 minutes; setup and prerequisite tickets are additional. Estimated field mix: Accessibility 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. A technician increases system text size. Pass/Fail controls overlap equipment names, and the last input disappears beneath the keyboard. Acceptance criteria - The agreed largest supported text setting keeps labels and choices readable. - Focused fields can scroll above the keyboard without hiding their error messages. - Each checklist choice has an accessible name that includes its inspection item. Implementation constraints - Do not disable system text scaling to make the layout fit. Verification - Complete a six-item inspection at large text size with the on-screen keyboard. - Use a long equipment name and an invalid reading; controls and errors remain reachable through assistive navigation. Deliverables - Adaptive inspection layout and emulator accessibility walkthrough Rollout and recovery: Review on the smallest supported test device; revert affected layout components if input becomes unreachable. Project prerequisites: Synthetic work orders and a revisioned sync contract An emulator with controllable connectivity and app lifecycle Engineer value: Practice durable local state, mobile lifecycle recovery, and conflict resolution in realistic offline workflows. Company value: Review whether an engineer can protect field work through crashes, interrupted uploads, and reassignment. 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. ### Record the visit Capture work and attachments through interruptions. #### FIELD-104 — Keep photo evidence attached after the app is suspended **Bug · High priority · Advanced** noCV practice brief v5 · FIELD-104 · An offline workday for field technicians Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Record the visit. Depends on: FIELD-102. Difficulty: Advanced. Estimated focused work: 165 minutes; setup and prerequisite tickets are additional. Estimated field mix: Mobile 60% · Storage 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. A technician takes an equipment photo, answers a phone call, and returns to a blank attachment tile. The draft stored a temporary camera URI that no longer exists. Acceptance criteria - Attachment metadata becomes saved only after the file is copied into app-owned storage. - Restart restores pending attachments with a clear missing-file recovery action when necessary. - Cancelled capture and failed copies leave neither dangling records nor orphaned temporary files. Implementation constraints - Use synthetic equipment images; permission to capture does not authorize unrelated gallery access. Verification - Capture, suspend, terminate, and reopen; the saved attachment remains available. - Delete the source URI before copying and cancel another capture; no accepted attachment or orphaned pending row remains. Deliverables - Durable attachment staging and lifecycle failure cases Rollout and recovery: Pilot capture separately from uploads; disable new capture if staged-file recovery fails while preserving existing files. Project prerequisites: Synthetic work orders and a revisioned sync contract An emulator with controllable connectivity and app lifecycle Engineer value: Practice durable local state, mobile lifecycle recovery, and conflict resolution in realistic offline workflows. Company value: Review whether an engineer can protect field work through crashes, interrupted uploads, and reassignment. 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. #### FIELD-105 — Explain why a work order is not ready to finish **Story · Medium priority · Intermediate** noCV practice brief v5 · FIELD-105 · An offline workday for field technicians Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Record the visit. Depends on: FIELD-102, FIELD-103, FIELD-104. Difficulty: Intermediate. Estimated focused work: 90 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. Finish visit is disabled with no explanation when a required reading or photo is missing. Technicians tap through every section to find the blocker. Acceptance criteria - A completion summary lists missing required answers and attachments with navigation actions. - Optional notes never block completion. - Finishing offline creates a pending completion operation and labels it as awaiting sync rather than server-confirmed. Implementation constraints - Derive readiness from the current local revision and the downloaded checklist version. Verification - Fill the required inputs and finish offline; a pending operation is visible after restart. - Remove a required photo and leave optional notes empty; only the photo blocks completion. Deliverables - Completion-readiness summary and offline finish cases Rollout and recovery: Enable the summary before completion changes; pause finishing if checklist versions cannot be resolved. Project prerequisites: Synthetic work orders and a revisioned sync contract An emulator with controllable connectivity and app lifecycle Engineer value: Practice durable local state, mobile lifecycle recovery, and conflict resolution in realistic offline workflows. Company value: Review whether an engineer can protect field work through crashes, interrupted uploads, and reassignment. 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. ### Reconnect safely Resolve retries, reassignment, and conflicting edits. #### FIELD-106 — Drain the sync queue without duplicating completed visits **Task · High priority · Advanced** noCV practice brief v5 · FIELD-106 · An offline workday for field technicians Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Reconnect safely. Depends on: FIELD-105. 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. Reception returns briefly and drops again during sync. The same completed visit is sent twice, while a later note disappears after a failed batch. Acceptance criteria - Each queued operation has a stable identity and advances only after acknowledgement. - Per-order dependencies preserve answer and completion ordering while unrelated orders can progress. - Retry uses bounded backoff and keeps unacknowledged operations durable across restart. Implementation constraints - The fixture service deduplicates operation IDs; do not assume a timeout means the server rejected a write. Verification - Acknowledge a batch and verify only confirmed queue entries leave local storage. - Drop a response after server acceptance and restart; retries keep the same IDs and produce one logical completion. Deliverables - Durable sync queue processor and interrupted-batch tests Rollout and recovery: Limit initial batch size and observe backlog age; pause queue draining on repeated protocol errors without deleting pending work. Project prerequisites: Synthetic work orders and a revisioned sync contract An emulator with controllable connectivity and app lifecycle Engineer value: Practice durable local state, mobile lifecycle recovery, and conflict resolution in realistic offline workflows. Company value: Review whether an engineer can protect field work through crashes, interrupted uploads, and reassignment. 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. #### FIELD-107 — Keep reassigned work from being silently completed offline **Bug · High priority · Expert** noCV practice brief v5 · FIELD-107 · An offline workday for field technicians Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Reconnect safely. Depends on: FIELD-106. Difficulty: Expert. Estimated focused work: 210 minutes; setup and prerequisite tickets are additional. Estimated field mix: Mobile 40% · Security 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. Dispatch reassigns a job while the original technician is underground. That device later uploads completion against the old assignment. Preserve the technician’s work while honoring current server authority. Acceptance criteria - Sync includes the assignment revision that authorized the offline visit. - Reassignment rejection moves local work into an explicit review-required state without marking the job complete. - The technician can inspect their unsynced notes and a redacted export while server-only actions remain blocked. Implementation constraints - Do not automatically apply old work to the new assignee; supervisor resolution is a documented stub contract. Verification - Sync a completion with the current assignment revision and confirm acceptance. - Reassign before reconnecting and reject the old revision; retain local work and prevent repeated automatic completion retries. Deliverables - Reassignment conflict flow and preserved-work recovery fixture Rollout and recovery: Pilot with forced reassignment scenarios; disable offline finishing if authority conflicts cannot retain work safely. Project prerequisites: Synthetic work orders and a revisioned sync contract An emulator with controllable connectivity and app lifecycle Engineer value: Practice durable local state, mobile lifecycle recovery, and conflict resolution in realistic offline workflows. Company value: Review whether an engineer can protect field work through crashes, interrupted uploads, and reassignment. 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. #### FIELD-108 — Resume a large photo upload without restarting the whole queue **Story · Medium priority · Advanced** noCV practice brief v5 · FIELD-108 · An offline workday for field technicians Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Reconnect safely. Depends on: FIELD-104, FIELD-106. Difficulty: Advanced. Estimated focused work: 150 minutes; setup and prerequisite tickets are additional. Estimated field mix: Mobile 40% · Storage systems 40% · Networking 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. One 12 MB equipment photo repeatedly fails halfway through and blocks all completed visits. Integrate the resumable-upload contract and isolate attachment progress from unrelated operations. Acceptance criteria - Committed upload offsets are persisted and reconciled with the service after reconnect. - An expired upload session starts a new session without losing the source file. - Failure of one attachment does not block sync for another independent work order. Implementation constraints - Use small synthetic chunks in tests; server file integrity and scanning remain separate responsibilities. Verification - Interrupt after two acknowledged chunks and resume from the server-confirmed offset. - Expire the session and simulate a missing local file; show repair guidance and allow another work order to sync. Deliverables - Resumable upload adapter and offset/session recovery cases Rollout and recovery: Enable for larger attachments first; pause uploads and keep staged files if offset reconciliation fails. Project prerequisites: Synthetic work orders and a revisioned sync contract An emulator with controllable connectivity and app lifecycle Engineer value: Practice durable local state, mobile lifecycle recovery, and conflict resolution in realistic offline workflows. Company value: Review whether an engineer can protect field work through crashes, interrupted uploads, and reassignment. 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 the rollout Protect devices and give support safe diagnostics. #### FIELD-109 — Clear a shared device without dropping pending work invisibly **Story · High priority · Advanced** noCV practice brief v5 · FIELD-109 · An offline workday for field technicians Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Support the rollout. Depends on: FIELD-107, FIELD-108. 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. Two technicians share a tablet between shifts. Sign-out currently leaves cached addresses for the next user, but blindly deleting storage would also erase unsynced repairs. Acceptance criteria - Sign-out reports pending work before an explicit discard or sync choice. - Confirmed sign-out removes account-scoped database rows, staged files, and credentials from the usable app context. - Signing in as a different technician cannot render or sync the prior account’s data. Implementation constraints - Document the limits of app-level deletion; do not claim forensic erasure or export data automatically. Verification - Sync all work, sign out, and sign in as another user; no previous records appear. - Fail sync with pending attachments and choose cancel; preserve the current session and work without exposing it to another account. Deliverables - Shared-device sign-out flow and account-boundary tests Rollout and recovery: Require this check before shared-device pilots; disable account switching if cleanup cannot be confirmed. Project prerequisites: Synthetic work orders and a revisioned sync contract An emulator with controllable connectivity and app lifecycle Engineer value: Practice durable local state, mobile lifecycle recovery, and conflict resolution in realistic offline workflows. Company value: Review whether an engineer can protect field work through crashes, interrupted uploads, and reassignment. 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. #### FIELD-110 — Expose sync health that depot support can act on **Chore · Medium priority · Intermediate** noCV practice brief v5 · FIELD-110 · An offline workday for field technicians Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Support the rollout. Depends on: FIELD-106, FIELD-109. Difficulty: Intermediate. Estimated focused work: 90 minutes; setup and prerequisite tickets are additional. Estimated field mix: Mobile 50% · Site reliability 30% · Privacy engineering 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. Depot support cannot distinguish a device waiting for Wi-Fi from one stuck on an expired upload. Add an account-local sync health page and a safe support bundle. Acceptance criteria - The page separates queued, retrying, blocked, and acknowledged counts with last successful sync time. - The bundle includes app/schema versions and operation categories but excludes notes, photos, addresses, and tokens. - A retry action obeys the same queue rules and cannot bypass blocked authority conflicts. Implementation constraints - Keep diagnostic storage bounded and document one recovery action per blocker category. Verification - Create a retryable upload and a reassignment blocker; verify distinct states and actions. - Seed private fixture content and inspect the exported bundle; none of it is present and blocked work is not force-sent. Deliverables - Sync health screen and depot troubleshooting note Rollout and recovery: Enable for pilot support staff; remove bundle export if redaction fails while retaining local status labels. Project prerequisites: Synthetic work orders and a revisioned sync contract An emulator with controllable connectivity and app lifecycle Engineer value: Practice durable local state, mobile lifecycle recovery, and conflict resolution in realistic offline workflows. Company value: Review whether an engineer can protect field work through crashes, interrupted uploads, and reassignment. 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.