RouteNet owns candidate computation and versioned plan; dispatch authority remains with the configured operations system.
AutoBuild your programIF-13 · Cloud interface
Optimization demand, candidate and publication
Carry immutable demand, resources, constraints, cost basis, objective, candidate plan, human review and publication receipt.
Authority model
Name the source—and name what it cannot prove.
The same message can be observation, projection, plan, receipt or physical evidence. This contract keeps those meanings separate.
Infeasible or partial plans expose violations; locked work remains fixed and stale inputs cannot publish.
An optimized candidate never implies dispatch, driver receipt, completed work or realized savings.
Product allocation
Producer and consumer responsibilities are explicit.
A product can appear on both sides when it transforms one authority into another; each transformation retains its own evidence.
Transport allocation
Choose transport after semantics are fixed.
The program can select one or more transports without changing the source authority or failure contract.
Synchronous or batch APIPlan eventExecution adapter
Compatibility vector
- schema or ABI version
- producer release
- consumer release
- policy and entitlement revision
- content/configuration revision
- territory/platform profile
Acceptance evidence
- contract compatibility
- nominal and negative scenarios
- ordering, replay and idempotency
- latency, capacity and resource bounds
- security, privacy and role enforcement
- offline, recovery and rollback
- target or operational acceptance
OEM program workshop
Freeze the Optimization demand, candidate and publication contract before integration.
Allocate owners, transport, schema, releases, policy, content, degradation, replay and target acceptance in one controlled baseline.