Operation plane · M10 · Dispatch engine
Real-time trip assignment.
The operational heart of the node: it turns orders into driver assignments in real time. TechnoRides inherits the platform's ~1-second automatic dispatch and extends it to every mode — moto, car, van, shuttle, bus, and freight.
// Console shown with sample data. Dispatch is a live operation-plane module (M10). Ledger-read reputation and cross-node roaming depend on the network plane (Registry · Ledger), which is roadmap — not yet live.
Real-time matching
How an order becomes an assignment.
Every order is scored against nearby drivers on the factors that actually decide a good match — then dispatched automatically, or handed to the panel for special cases.
{
"order_id": "ORD-9120",
"trip_id": "TRP-8841",
"status": "assigned",
"mode": "car",
"driver": {
"id": "drv_44a",
"name": "A. Morales",
"eta_min": 3,
"distance_km": 0.9
},
"matched_on": ["proximity", "vehicle", "rules"]
}// Sample request/response. The dispatch API surface ships with the node; matched_on will include reputation once ledger reads go live (roadmap).
Every mode, one engine
Automatic for volume, manual for the exceptions.
The same ~1-second engine drives the routine flow and hands you the panel the moment a trip needs a human in the loop — across passengers, shared seats, and freight.
Automatic & manual dispatch
Automatic dispatch handles the volume in about a second. When an order is special — VIP, dispute, a stuck queue — assign it by hand from the panel with ranked candidates.
Reservations
Scheduled trips and recurring series — the weekday commute, the standing airport run — are dispatched on time, not at request time.
Shared capacity
Shuttles, buses, and vans dispatch with seats and stops — the engine fills capacity along a route instead of sending one vehicle per rider.
Freight
Trucks dispatch with capacity attributes — weight, volume, refrigeration — and close out with proof of delivery, not just a drop-off tap.
Authorization check
No order reaches a driver without a valid network authorization. The engine refuses unauthorized trips before they ever touch the board.
The result
Fewer cancellations, more rides per hour, and a better experience for passenger and driver alike — the work the dispatch board exists to do.
On the board
What dispatch emits, in real time.
Each match, accept, and start is an event your node can watch, log, and react to — the same stream that drives tracking and settlement downstream.
| Order | Mode | Driver | Status | ETA |
|---|---|---|---|---|
| ORD-9120 | Car | A. Morales | Assigned | 3 min |
| ORD-9121 | Moto | — | Awaiting | — |
| ORD-9122 | Shuttle | D. Park | Boarding | 5 min |
| ORD-9123 | Freight | — | Capacity | — |
| ORD-9124 | Van | S. Vance | Reserved | Mon |
| ORD-9119 | Car | J. Liu | En route | 2 min |
// All figures and IDs are illustrative sample data. The dispatch engine runs on your node today; cross-node events (node.sync, roaming) arrive with the network plane — roadmap.
Operation plane · M10
Put dispatch behind your own apps.
The engine that turns orders into assignments is most powerful inside your own branded passenger and driver apps. See how the operation plane fits together.