Reviewedv1Reliability
Offline-first behavior and sync
Persist user intent locally, replay it in a governed order, and distinguish pending from confirmed state.
Explicit local state
Never present a local operation as server-confirmed. Use explicit states such as pending, syncing, confirmed, failed, and conflict.
Governed replay
- Persist operation_id and idempotency_key before the first send.
- Preserve ordering for dependent operations.
- Allow an independent operation to pass a blocked item only by policy.
- Never retry forever or without jitter.
Reconciliation
Compare snapshot or delta from the authoritative source, match acknowledgements, and retain diagnostics without sensitive payloads.