The substrate-layer position for hospitality data provenance and observability.
A foundational coordinate for building the audit, attribution, and observability infrastructure beneath hospitality AI — where data lineage, agent actions, and compliance trails are anchored.
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
'Substrate' names the foundational layer of the agentic stack: the provenance, audit, and observability surface that higher-layer agents depend on. In hospitality, that substrate spans guest data, booking history, operational logs, and revenue attribution — all requiring traceable, auditable foundations as AI takes on more operational decisions.
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.