Skip to main content
Guest-facing Lucia is HelloLucia, LLC’s public concierge product surface. She helps guests warmly before verification, preserves privacy while identity is uncertain, and turns guest conversation into structured operational clarity for the property team.

​
Product Line

HelloLucia, LLC now owns three major product lines:
Guest-facing Lucia is not simply a chatbot. She is a front-of-house teammate connected to operational truth. The operator-facing Lucia OS remains the calm operating partner for owners and property teams. Guest-facing Lucia is the warm public concierge surface that can help, collect claims, and escalate structured signals without violating booking privacy. Eval Labs is the proof and regression system for both surfaces.

​
Current Implemented State

Current guest-facing Lucia implementation recorded by this Canon milestone:
Both Lucia Engine and Lucia Guest Agent currently use gpt-5.6-sol, but the shared value does not imply inheritance. Engine configuration and /admin/operator-focus provenance establish Engine runtime truth. Guest Agent configuration and its separately deployed provider proof establish Guest Agent runtime truth. The Guest Agent does not expose or persist the Engine’s meta.model_runtime provenance contract. Its 2026-07-12 verification proved both the effective configured model and the provider-returned model as gpt-5.6-sol; it did not change prompts, verification flow, routing, schemas, or the core SSE events start, token, cta, meta, and done. This is deployed runtime and live-development product truth. It is not a broader production-readiness claim.

​
Guest Product Versioning

Current guest-facing product milestone:
Definition:
Versioning boundary:
The guest-facing UI should eventually show both:

​
What Changed

Guest-facing Lucia is now a distinct major product surface inside the Canon. Current implemented surface:
The interaction should feel like Lucia orienting herself, not like a form.

​
Completed Reservations + Verification Loop

The completed live-development proof now connects:
This remains a controlled seed/test reservation loop. It is not a public booking engine, payment system, Lodgify replacement, auth system, or production OTA integration.

​
Identity Orientation Options

Guest-facing Lucia begins by asking the guest to orient the relationship:
These are not decorative buttons. They are the first step in privacy-safe context collection.

​
Product Doctrine

Guest-facing Lucia may help before verification. Guest-facing Lucia may collect claims. Guest-facing Lucia may not expose booking-private details or mutate booking records until identity/linkage is verified or operator-linked. Core public-facing doctrine:
Guest-facing Lucia should remain:
Guest-facing Lucia must not become:

​
Guest-Facing Lucia Eval Track

Eval Labs now needs a first-class Guest-Facing Lucia Eval Track separate from operator-facing Lucia evals. Purpose:
The track must cover identity orientation, booked-guest claim parsing, claim fragments across turns, weak vs strong claims, ambiguous/no-match cases, magic-link eligibility, verification-email privacy, token consume/replay/expiry, verified session state, guest operational signals, Admin Signal Stream visibility, Focus Ops no Luca/Nora drift, and warm hospitality tone.

​
Knowledge Center Map

Start here, then read:

​
Current Boundary

Implemented does not mean production-hardened. Current non-production gaps include:
Canon should record implemented state, doctrine, and roadmap separately.