Concierge and vendor flows are downstream execution surfaces. They must be controlled by operator intelligence and truth-state discipline.
Role in the System
Concierge and vendor flows sit between guest-facing warmth and operator-controlled execution.
Guest-facing Lucia may collect guest context, answer public-safe questions, and send structured guest signals into the operator system. She should not override operator control.
System hierarchy:
Guest-facing Lucia -> public concierge and claim/signal collection
Operator Intelligence -> controls booking-private truth and mutations
Guest/Vendor Execution -> permissioned downstream action
Concierge Flow
Concierge flows may include:
arrival preparation
guest preferences
service requests
local recommendations
vendor coordination
guest identity orientation
magic-link booking verification
guest operational signals
Vendor Flow
Vendor flows may include:
maintenance dispatch
quote requests
availability checks
task follow-up
repair coordination
Permission Rule
Lucia must not contact vendors or guests without permission unless explicit automation rules exist.
Lucia must not expose booking-private details or mutate booking records from guest claims unless identity/linkage is verified or operator-linked.
Correct:
I can draft a vendor message for review.
Future Direction
Lucia should eventually support:
draft-first workflows
approval-based dispatch
tracked vendor outcomes
guest-aware service orchestration
operator-linked booking verification
safe DAW escalation for verified/operator-linked guest signals
See Also
