Edge, IoT & Compute · Module
Edge Sync
Offline work that never loses or duplicates a business action
Edge Sync is the planned offline substrate for One3. It defines what each device may hold offline, queues writes as Actions and replays them through the Action Bus with permission and policy checked again.
What it does
Edge Sync makes One3 work offline for people, devices and sites without losing or duplicating business actions. It is the core module of the app and the same engine that POS, Field Service, Facilities technician flows and EHS inspections are planned to use. The plan's reliability bar comes from the POS roadmap: an 8-hour offline test with thousands of sales syncs and no loss or duplication.
How it works
- Sync scopes declare, per object type, which rows a client may hold (for example 'my jobs for the next three days' or 'checklists for my site'), which fields and attachments, size limits and which Actions are allowed offline.
- Every offline write is an Action with an idempotency key, a hybrid logical clock timestamp, the actor, the policy snapshot version and dependencies. Clients never write to server tables.
- Replay re-validates. On reconnect, queued Actions replay in dependency order through the Action Bus, and entitlement, permission, policy and delegation of authority are checked again. Rejections come back with a reason and options.
- Conflict rules are declared, not guessed: server wins, client wins, field-level last writer, set-merge for append-only lists, domain rules (stock counts become adjustments) or manual review. The losing value is never discarded.
- Irreversible Actions wait. Sending a WhatsApp message or issuing an invoice with IRN cannot execute offline; they queue as drafts that need online approval.
Sites without a network
At GA, a site edge node (a One3 Box edge profile or approved hardware) serves LAN clients during a WAN outage with a local cache, a local queue and conflict pre-checks, then forwards everything with idempotency keys when the WAN returns. Long-disconnection policies set maximum offline duration per scope, with stale-data banners and read-only degrade after expiry.
Security
The local store is encrypted with per-client keys, wiped on revoke, and removed automatically when a member is offboarded. Permission loss removes records on next sync. Agents never operate through offline clients.
Features
What Edge Sync includes
Sync scopes
Declarative, versioned definitions per object type: row filter, fields, related records, attachment policy, size limits and offline-allowed Actions.
Sync client registration
Every mobile install, PWA and edge node registers as a client bound to membership, device and app version.
Encrypted offline store
Local database encrypted at rest with per-client keys wrapped by the platform keystore; wiped on revoke.
Offline Action queue
Actions captured with idempotency key, hybrid logical clock, actor, policy snapshot version and dependencies.
Replay with re-validation
Dependency-ordered replay through the Action Bus with entitlement, permission, policy and DoA re-checked.
Conflict rules and review queue
Per-field strategies with Pack defaults and tenant tightening; a supervisor queue shows both versions and a suggested resolution.
Attachment sync
Resumable uploads for photos, voice and video with checksums, background upload and Wi-Fi-only rules per type.
Sync log and client health
Last successful sync, queue depth, oldest queued Action age, failures and storage per client.
Version compatibility
Minimum client version per scope and forced update prompts before an incompatible replay.
Site edge node
On-premises relay serving LAN clients during WAN outage with local cache, queue and store-and-forward.
Long-disconnection policy
Maximum offline duration per scope, offline session grants with expiry and read-only degrade.
Revoke and remote wipe
Revoke offline data at next contact, remote wipe through Device Management, automatic revoke on offboarding.
Bandwidth controls and observability
Delta sync, compression, metered-connection mode, SLO dashboards and a replay simulator in CI.
Pack declarations
Syncable objects, scopes and conflict rules declared in Pack manifests and validated in CI.
Workflow
Offline capture and replay
- 1
User acts offline with a local policy pre-check
- 2
Action queued with idempotency key, clock and dependencies
- 3
Queue uploads in dependency order on reconnect
- 4
Action Bus re-checks entitlement, permission, policy and DoA
- 5
Conflicts resolved by declared rule or sent to review
- 6
Committed changes sync back to the client
Workflow
Site edge node during WAN outage
- 1
LAN clients read and queue Actions through the edge node
- 2
The node serves its cache, pre-checks conflicts and persists the queue
- 3
Clients see local confirmations marked pending
- 4
When the WAN returns, the node forwards the queue with idempotency keys
- 5
Final status and conflict items return to clients
- 6
Delta changes for scopes flow back to the node
AI
AI skills and Digital Employees
Conflict resolution suggestion
Suggests a resolution with the rule, both values, actors and times. AI never resolves a conflict itself.
Scope sizing advisor
Predicts payload size, sync time and storage for a proposed scope and flags scopes over budget.
Replay failure triage
Clusters rejected replays by reason and drafts the worker-facing explanation in their language.
Sync health anomaly detection
Flags clients and sites whose queue age, failure rate or storage deviates from their own pattern.
Digital Employees that use this module
They act through the same governed Actions as people; risky steps wait for approval.
Frequently asked questions
What happens if two people edit the same record offline?
The declared conflict rule for that field decides, or the item goes to a supervisor review queue. The losing value is kept in history with actor and time.
Can something be sent to a customer while offline?
No. Externally or legally irreversible Actions, such as sending a WhatsApp message, queue as drafts and need online approval. POS receipts follow the POS module's own offline tax rules (verify).
Is a device's offline data safe if it is lost?
The offline store is encrypted with per-client keys. Admins can revoke at next contact or remote-wipe through Device Management, and queued Actions from wiped clients are quarantined for a supervisor decision.
Does it need special hardware?
Phones and PWAs work without extra hardware. Long outages at a site can use a site edge node on a One3 Box edge profile or approved hardware, planned at GA in W4.
See Edge Sync in your workflow
Tell us about your team and the outcomes you want. We will walk you through the apps, the Digital Employees and the plan for your industry.