The .com substrate position for hospitality data foundations.
A complementary .com anchor for the hospitality data and observability substrate — pairing with the agent-era TLD to control the canonical namespace across registries.
Matched pair · sold together
Held and transacted as one position. A matched .ai + .com pair forecloses its own most common confusable — one coordinate, not two names.
The set
Part of the Hospitality resolution surface.
7 of 7 primitives held for hospitality — 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 Hospitality row holds 2 matched pairs across the seven primitives.
See the full Hospitality 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
Architectural context
Hospitality · Vertical-Specific · 2 compound moats. Architectural surface: Substrate.
Layer position: Cross-cutting
Why this is canonical
The .com extension extends the substrate coordinate into the legacy-web namespace, providing TLD redundancy for a concept with multi-decade relevance. Hospitality data governance, audit, and provenance requirements predate the agentic era and will persist alongside it — the .com captures that longer arc.
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.