Use cases
The jobs the layer is for.
Guest identity, by the role that needs it and by the system it sits above. Each page is a job, not a vendor logo wall, and not a story about a customer we have invented.
By role
IT / CTO
One trusted guest identity for the stack.
Stop wiring guest records system to system. One Master Profile sits above the stack, served over REST and MCP, with access you scope per connection.
Operations Director
Recognition at every outlet, from one record.
The desk, the bar and the spa should not have to vote on who the guest is. One resolved record, read beside the systems those teams already use.
General Manager
The house remembers the same guest.
A returning guest should not be a stranger at check-in. The record sits above the property system, so the house can recognise the same person.
Commercial Director
Commercial teams acting on one profile.
Loyalty and CRM should read the resolved guest, not own a second copy. Recognition is the layer’s job; the programme keeps the points engine.
By system type
PMS
Guest recognition above the property system.
The PMS guest card is not one person across the house. Recognition lives above the property system, so a PMS switch does not rebuild the guest.
AI agents
Agents that read the same Master Profile.
An agent pointed at one system inherits that system’s fragments. Point every agent at the Master Profile over MCP or REST instead.
See the systems, or walk through the layer.
The directory names every connection. A 20-minute demo maps the Master Profile to the stack you already run.