| name | offline-sync |
| description | Implement offline-first or offline-tolerant mobile state with local persistence, pending operations, conflict policy, retry, connectivity changes, and reconciliation. |
Offline Sync
Use when this procedure is the primary professional method needed for the assignment.
Procedure
- Confirm the decision or outcome this work must support, its scope, owner, constraints, and definition of success.
- Establish the evidence baseline using data model, API semantics, connectivity expectations, conflict rules, local storage, and user workflows. Do not fill material gaps with assumptions when they can change the result.
- Define authoritative state and offline scope, persist durable operation identity, queue safe mutations, reconcile conflicts, surface sync state, and test airplane/restart/reconnect sequences.
- Exercise realistic edge, failure, transition, or exception cases that could invalidate the result; record unresolved uncertainty explicitly.
- Validate the output against the original outcome and any neighboring professional contracts so this skill does not silently absorb another specialist's authority.
- Record the resulting artifact, measurements, decisions, provenance, and handoff information needed for another owner to reproduce or continue the work.
Quality gate
Repeated reconnect/retry cannot duplicate side effects and users can understand unsynced/conflicted state.
