The guest-to-operator bridge is the contract that lets public guest conversation become operator-visible clarity without pretending every guest is verified or every request is actionable.
Product Role
Guest-facing Lucia is a front-of-house teammate.
Operator-facing Lucia is a calm operating partner.
The bridge between them must be structured, signed, privacy-safe, and honest about verification.
guest conversationstructured signaloperator review/link/action
Current Bridge
Current implemented bridge:
Routing Safety
Unlinked/candidate guest signals do not open fake DAW.
Linked/verified signals may eventually route to DAW when safe.
Current routing rule:
DAW remains an action/save surface. It must not become a fake destination for unverified guest claims.
Operator Review Doctrine
The operator can receive guest-facing context before the guest is verified.
But the operator surface must preserve:
Operator language should distinguish:
Focus Ops Drift Protection
Focus Ops was hardened so unlinked/candidate guest signals do not drift into similar existing bookings.
This matters most when two guests share:
Service overlap is never identity evidence.
Airport pickup overlap must never attach an unlinked guest to Luca/Nora or any existing guest.
Future Admin Surface
The current bridge reaches Admin Signal Stream.
Roadmap Admin work includes:
See Also
