The operating-system position for mobility infrastructure in the agentic era.
An organizing-layer coordinate for the software that governs how people and vehicles move — routing, orchestration, access, and real-time coordination unified under one canonical name.
The set
Part of the Mobility resolution surface.
7 of 7 primitives held for mobility — a complete resolution surface. One operator holds the row agentic systems resolve to; every competitor who arrives later works with what is left.
Coordinated sets this position belongs to — the coverage it extends. Counts are the live cluster size in the graph.
Primary home
Also appears in
Surfaces this position also reads to — addressability, not exclusivity. A name applicable to a category is not a claim to own it; these are the buyer pools the coordinate speaks to, beyond the clusters it is held in.
Architectural context
Mobility · Vertical-Specific · 2 compound moats. Architectural surface: OS.
Layer position: Cross-cutting
Why this is canonical
'Mobility OS' names the architectural ambition that every serious mobility infrastructure builder is working toward: a unified control layer beneath fleets, transit, logistics, and access systems. The .network TLD signals infrastructure and protocol-level positioning rather than a consumer product.
Where it fits
A few directions this coordinate opens —
Illustrative, not exhaustive — held as a transferable canonical position, open to the buyer's own use.