What is a mutation queue (outbox)?

Every change recorded locally first, then replayed to the server in order.

The mutation queue — the outbox pattern — writes each change to durable local storage alongside the data, then replays entries to the server as connectivity allows. A write that can't reach the server isn't lost; it's queued, retryable and ordered.

It's what makes offline writes safe: close a work order in a dead zone, and the mutation sits queued until sync — then replays idempotently, so a retried send can never double-complete the job.

• How it's used