Network directory
Onboarding, identity, geofence, enabled modes and node endpoints for every network on the platform — one record per city, country or company.
Network plane · M01 · roadmap
The directory and control plane of the network.
The Network Registry registers every network — city, country, company — maintains its identity and state, and issues the dispatch authorization that lets a node operate. Without a valid authorization, a node can't process orders. This is what makes all governance operational.
In build · roadmap
Build status. The network plane — registry, immutable ledger, cross-network roaming and the open protocol — is on the roadmap and shown as a target architecture, not a live service. The operation plane (node, apps, dispatch, payments, tracking) is what ships today.
What it does
Four jobs, one source of truth.
The registry is the directory every node looks up and the authority every node answers to — the equivalent of being "online with the card network" for a bank.
Dispatch authorization
A short-lived signed token the node renews while it complies. This is what makes all governance operational: without a valid authorization, a node can't process orders.
Discovery
Resolves which network covers a given geography and service type — the lookup routing relies on to send an order to the right node.
Federation
Models the country → cities relationship, so a country-level network can hold policy while each city operates its own sovereign node beneath it.
The keystone
The dispatch authorization is what makes governance operational.
It is a short-lived signed token the node renews only while it complies. Every renewal re-checks the rules: verified drivers, current protocol version, settlement up to date. The moment a network falls out of compliance, the next renewal is denied — and the node stops processing orders. No after-the-fact enforcement; the gate is the operation.
See governanceDispatch authorization
networkcity:sf-yellow
parentcountry:us
modesrides, delivery
statusauthorized
issued2026-06-13T14:02:11Z
expires2026-06-13T14:07:11Z
signatureed25519:9f2a…c41d
Renews every 5 min while compliant · denied otherwise
How a node goes live
From record to authorized — and back.
A network registers once, then earns its right to operate continuously. The registry is the only place that grants — or revokes — that right.
01
M01
Register the network
The directory record is created: identity, geofence, enabled modes and node endpoints — for a city, a country or a company.
02
M01
Request authorization
The node asks the registry to operate. The registry checks the rules — verified drivers, current protocol, settlement up to date.
03
M01
Issue a short-lived token
On pass, a signed dispatch authorization is issued. The node can now process orders — and renews the token while it stays compliant.
04
M01
Resolve & route
Discovery resolves which network covers a geography and service type; routing sends the order to that node's endpoint — if its authorization is valid.
05
M01
Renew — or revoke
Each renewal re-checks compliance. Fall out of the rules and the next renewal is denied; the token expires and the node can no longer dispatch.
Discovery
Resolve a geography to a node.
Routing asks the registry one question — who covers this place, for this service? The registry answers with the network and its node endpoint. This is the first hop in handling any order.
Request
GET/api/v1/registry/resolve
lat,lng37.7790, -122.4170
moderides
Response
200 OK application/json
{
"network": "city:sf-yellow",
"parent": "country:us",
"endpoint": "node.sf-yellow.tr",
"modes": ["rides", "delivery"],
"status": "authorized"
}Illustrative. The endpoint, payload and IDs above show the target shape of the registry API — the network plane is roadmap, not a live service today.
Federation
Country holds policy. Cities operate.
Federation models the country → cities relationship. A country-level network carries shared policy and identity; each city below it runs its own sovereign node.
country:uspolicy · identity
city:sf-yellowauthorized
city:nyc-metroauthorized
city:atx-rideshareonboarding
Each city operates its own node; the registry makes them interoperable beneath one country policy. How countries use it.
Why it matters
A rulebook nobody enforces is just a PDF.
Plenty of platforms publish rules. The registry is what turns rules into something operational: comply, or you can't dispatch.
| Capability | Rules in a policy doc | Network Registry · M01 |
|---|---|---|
| Compliance is enforced at run time | No | Yes — every renewal |
| A non-compliant node can be stopped instantly | No | Deny the next renewal |
| One lookup resolves a geography to a node | No | Discovery |
| Country policy over sovereign city nodes | No | Federation |
| Available today | — | Roadmap |
Build status. The registry, ledger, roaming and protocol — the whole network plane — are on the roadmap and shown here as a target architecture, not a live service. What ships today is the operation plane: the Node, apps, dispatch, payments and tracking.
Where it sits
The registry connects; the node operates.
M01 is the network plane's control plane. It governs what the operation plane is allowed to do, and feeds the rest of the network plane.
The Node M03
A single operator's live network — dispatch, payments, tracking. It can't process orders without a valid authorization from the registry.
See the NodeLedger
The auditable record of what each authorized network settled. The registry gates who is allowed to write to it. Roadmap
See the LedgerProtocol
The open interface agents and merchants enter through. The registry stamps the protocol version a node must run to stay authorized. Roadmap
Read the protocolGet started
Operate a node. Answer to the network.
A node disconnected from the network isn't a transport network — it's a database. The registry is what makes a node count.