Preserve conflicting offline visit notes for explicit resolution
Two emulators edit one visit offline and last-write-wins removes a paragraph. Surface both revisions.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Conflict resolution · Revision control
Estimated field mix
- Mobile50%
- Distributed systems50%
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
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.
Setup prerequisites
- Create synthetic visits and a local sync adapter.
- Provide controllable connectivity and process-restart simulation.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
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 to include
- 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.
Value of the work
For the engineer: Practice durable mobile state and explicit sync conflicts.
For the team: Inspect how an engineer protects field work during disconnection.
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.