The first question in a field workflow is not “is the API reachable?” It is “can I safely finish this capture?” If the answer depends on the network, the system will eventually create duplicates, missing evidence, or a record nobody can explain.
VEQO persists the command envelope before showing the operation as captured. It gives the device an identity, keeps credentials out of the mobile bundle, and replays the operation against a server-side idempotency key.
The result is a calmer failure mode: the operator sees a pending or conflict state, not a second animal. The API returns the canonical record, version, timestamp, and next state once the command is accepted.
The contract is the product
Offline support is not a sync button added at the end. It is a contract between mobile storage, command validation, authorization, transactions, audit, and realtime updates.