Show sync completion separately from resolved inspection conflicts
A tablet says all synced even though uploaded changes contain unresolved conflicts and a pending attachment.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Distributed UX · State semantics
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
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.
- AMERGE-101 · Define offline change envelopes with stable client operation IDs
- AMERGE-102 · Require current inspection access before applying a queued offline change
- AMERGE-103 · Distinguish independent checklist edits from conflicting edits
- AMERGE-104 · Apply offline operations with a durable deduplication record
- AMERGE-105 · Preserve concurrent inspection findings as explicit conflicts
- AMERGE-106 · Resolve an inspection conflict against its current proposal set
- AMERGE-107 · Keep deleted findings deleted when an old tablet reconnects
- AMERGE-108 · Finalize offline attachments by verified content identity
- AMERGE-109 · Resume inspection synchronization from a server-confirmed cursor
Acceptance criteria
- Report transport acknowledgement, conflict state and attachment state separately.
- Keep rejected operations visible with safe reasons.
- Never equate uploaded data with an approved inspection.
Implementation constraints
- Use a local status projection with accessible plain-language labels.
Verification to include
- Display a fully acknowledged conflict-free synthetic inspection.
- Acknowledge a conflicting batch and retain unresolved status.
Deliverables
- Sync status contract and state examples
Rollout and recovery
Publish precise status labels; restore prior layout without collapsing distinct states.
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.