Commit a completed checklist item before showing it saved
A technician checks Replace intake filter and force-closes the app. On reopening, the check is gone even though the screen showed Saved.
- Focused work estimate
- 2h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- SQLite · Transactions · Lifecycle testing
Estimated field mix
- Mobile60%
- Database engineering40%
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 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.
Setup prerequisites
- Synthetic work orders and a revisioned sync contract
- An emulator with controllable connectivity and app lifecycle
Preceding work
No earlier ticket is required. Complete the project setup above.
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 to include
- 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.
Value of the work
For the engineer: Practice durable local state, mobile lifecycle recovery, and conflict resolution in realistic offline workflows.
For the team: Review whether an engineer can protect field work through crashes, interrupted uploads, and reassignment.
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.