The network-layer position for freight contract infrastructure.
A canonical coordinate for the systems and protocols that underpin freight contract exchange and execution.
Matched pair · recommended together
Recommended: sold as a pair — the matched .ai + .network TLDs cover one coordinate. Each name can be acquired on its own; the set inquiry is the path to the whole position. Click a name to view its lander.
The set
Part of the Freight resolution surface.
7 of 7 primitives held for freight — a complete resolution surface. One operator holds the row agentic systems resolve to; every competitor who arrives later works with what is left.
Held as a matched pair — the Freight row holds 37 matched pairs across the seven primitives.
See the full Freight opportunity →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
Freight · Cross-Vertical · 2 compound moats. Cross-cutting: Contracts.
Layer position: Cross-cutting
Why this is canonical
Contracts are the connective tissue of every freight relationship — between shippers, carriers, and brokers. The .network TLD signals the multi-party, protocol-layer framing: the infrastructure through which contract terms flow and are enforced across the freight ecosystem.
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.