Knowledge with provenance
Answers reference approved documents, versions and review dates. If a source is missing or policies conflict, the workflow asks for human confirmation.
FLATWHITE AI · HOSPITALITY AUTOMATION & INTELLIGENCE
A reference architecture for individually developed hotel solutions. With source provenance, scoped permissions and control before critical actions.
A possible architecture for your hotel. From permitted access to a traceable action, every step has a purpose, a boundary and a responsible role.
Reference architecture for potential client solutions. The website demo uses fictional data only and is not connected to hotel software.
Connect only sources explicitly approved by the hotel and the provider.
Turn different formats into a consistent, understandable hotel data model.
Check who may see and use each piece of data before further processing.
Prepare tasks using approved knowledge and clearly defined metrics.
Break an agreed plan into individual, reviewable steps.
The responsible person decides on consequential actions.
Make outcomes and failures visible and provide a reliable fallback.
ILLUSTRATIVE GUEST REQUEST · NO LIVE DATA
Email → permission check → approved hotel policies → reply draft → approval → authorised channel → audit
Spa availability is missing? The draft says so. Approval is rejected? Nothing is sent. An event arrives twice? It does not create a second action.
Answers reference approved documents, versions and review dates. If a source is missing or policies conflict, the workflow asks for human confirmation.
Access is checked before retrieval. Tenants and roles remain separate; an external integration partner receives only the necessary, agreed scope.
Tools and actions are explicitly allowlisted. A draft is not permission to send. Consequential guest, rate and financial decisions require the responsible person.
Timeouts, stale data and unavailable APIs stop the affected action. Limited retries, unique event IDs and idempotency prevent duplicate tasks or messages.
Testing and evaluation begin in a sandbox. Staging and production remain separate. Logs contain technical references rather than guest content; retention and deletion are defined.
EU cloud, private deployment and on-premises options are assessed for the actual project. Providers, remote access, contracts and international transfers need review.
The actual design depends on interfaces, permissions, data quality and contractual requirements. Security and privacy measures are assessed for each project; no blanket certification or EU-only processing is claimed.
Answers come from approved hotel information. When a current source is missing, the question goes to your team.
Explore the architectureApproved arrival and stay information. The front desk reviews any special commitments.
citation: demo-policy-1 · v3
role-scoped retrieval · no guest data
Approved service information. Availability and appointments require current confirmation.
citation: demo-policy-2 · v2
role-scoped retrieval · no guest data
Ownership, standards and escalation routes. Only the appropriate hotel roles receive access.
citation: demo-policy-3 · v4
role-scoped retrieval · no guest data
Current version. Appropriate role. Traceable approval.