Distinguish independent checklist edits from conflicting edits
The sync service treats every concurrent change as either a blanket overwrite or a blanket conflict.
- Focused work estimate
- 2h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Conflict modeling · Data semantics
Estimated field mix
- Distributed systems60%
- System design40%
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
A fictional field team inspects equipment with intermittent connectivity. Two tablets can edit the same checklist and an old upload may restore a deleted finding.
Setup prerequisites
- Create two local client-state simulators and a synthetic inspection API.
- Use fabricated notes and local attachment bytes.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Define fields that can merge independently.
- Require explicit conflict when the same protected value diverges.
- Document attachment and deletion conflict rules separately.
Implementation constraints
- Use a small fixed checklist; avoid a general-purpose merge language.
Verification to include
- Merge edits to two independent checklist items.
- Edit the same item differently and preserve both proposed values as a conflict.
Deliverables
- Merge policy table and worked examples
Rollout and recovery
Review the policy before automatic merging; keep unresolved fields on manual resolution.
Value of the work
For the engineer: Practice offline synchronization, causal revisions and conflict resolution.
For the team: Review whether field work survives disconnection without hiding conflicting observations.
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.