Keep deleted findings deleted when an old tablet reconnects
A tablet that missed a deletion resubmits its old finding and recreates content the team intentionally removed.
- Focused work estimate
- 5h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Deletion semantics · Synchronization
Estimated field mix
- Distributed systems60%
- Data 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
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
Acceptance criteria
- Represent deletion with an ordered tombstone.
- Reject stale recreation under the declared merge policy.
- Define tombstone retention and resnapshot requirements.
Implementation constraints
- Avoid using wall-clock time alone to order deletion and recreation.
Verification to include
- Delete a finding and replay an older update.
- Expire supported replay history in the simulator and require resnapshot rather than guessing.
Deliverables
- Tombstone protocol and stale-client cases
Rollout and recovery
Deploy tombstones before cleanup; halt tombstone removal until the resnapshot contract is available.
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.