Offline operation queue — idempotent push/pull, conflicts, cursors
Op-apply semantics unit-tested in the kernel; server push/pull endpoints behind entitlement + RBAC + device-ownership lock; schema covered by disposable-PG16 integration test.
Route product / Field
Keep field execution moving when the network does not.
Offline field-sales automation, journey planning, outlet visits, order capture, collections, returns, merchandising evidence and van sales.
Tenant-isolated workspace. Access requires an explicit rtm.field entitlement.
Readiness is generated from the product registry. A public product site never turns a roadmap item into an operational claim.
One focused product, independently entitled. It can stand alone and connect to the wider Route portfolio when useful.
Op-apply semantics unit-tested in the kernel; server push/pull endpoints behind entitlement + RBAC + device-ownership lock; schema covered by disposable-PG16 integration test.
ROUTE-20X: replaced the contract-only store-ops placeholder — the RTM-native workspace ships beat FSM (draft→published→retired), visit recording (replay-safe) and sync-conflict resolution (first decision wins). Quarantined order drafts become convertible on CLIENT_WINS.
order_draft ops ride the offline op-log; the visit drawer converts an accepted draft into a Channel sales invoice through the shared idempotent document writer. Server-side repricing against PIM is NOT built yet — conversion trusts the captured prices.
Operating mode inside QuantumOS Field — never a separate product.
Turn territories and beats into a focused day in the field.
Capture orders, collections and evidence at the outlet.
Sync safely with explicit conflict handling and ownership.
Field sales teams, supervisors and van-sales operators