Resume inspection synchronization from a server-confirmed cursor
The tablet stores a local cursor before receiving server confirmation and skips updates after a crash.
- Focused work estimate
- 5h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Checkpointing · Recovery
Estimated field mix
- Distributed systems60%
- Mobile40%
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
Acceptance criteria
- Advance the local acknowledged cursor only after durable server outcome.
- Bind cursor to inspection scope and sync generation.
- Require resnapshot when the server cannot honor the retained history window.
Implementation constraints
- Use two client simulators with controlled interruption points.
Verification to include
- Crash during a sync page and resume without missing confirmed operations.
- Use an expired or cross-scope cursor and reject incremental sync safely.
Deliverables
- Cursor recovery protocol and crash harness
Rollout and recovery
Enable incremental sync after the resnapshot path passes; retain local pending operations until acknowledged.
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.