Skip to main content
Guest-facing Lucia has crossed from future concept into implemented controlled-preview infrastructure. Production readiness still requires security, operator workflow, booking integration, consent, and Eval Labs proof.
Source was reviewed as of 2026-08-12 and the deployment re-read on 2026-09-10; the Guest Agent is unchanged since 2026-07-18. The newest accepted production verification cited here was recorded on 2026-07-18; no newer live production check is asserted.

​
Current implemented baseline

Guest-facing Lucia currently runs as the independently deployed Lucia Guest Agent:
Current Guest-owned runtime contract:
The Guest Agent owns its OpenAI generation path. VV_AI_MODEL is Guest-specific and does not inherit Lucia Engine configuration. A shared model name across services does not create shared runtime truth.

​
Accepted live evidence

The latest accepted live Guest evidence is:
This evidence applies to that exact deployment, still the published one on 2026-09-10. It does not prove September 2026 live freshness or general production readiness.

​
Where guest-facing Lucia sits in the September order

Sequencing law, founder 2026-09-04 (recorded on A stand-in voice, designed, ALGO-41): Fieldwork and Admin speak one language → the Algorithm proves it understands intake → then the guest agent and its model mix. Guest-facing Lucia is therefore last in the order, on purpose. As of 2026-09-10:
Two September laws already bind the guest surface without changing its code: the names law (Lucia and Villa Valentin with a plain i on every surface, LUCI-238, 2026-09-09) and the guest-mail button rule (rectangles with 4 to 5px corners, centred; the guest-agent button “takes the same shape because it is the same family”, LUCI-237, 2026-09-09). Both are rulings applied on the Engine’s guest-mail family; neither is a shipped change to the Guest Agent at fbf77b6. Nothing on this page writes a plan as shipped.

​
Version domains

Guest-facing Lucia does not have one global version value: Roadmap decisions must name the domain they change. Do not present the UI label, package version, signal schema, or commit as interchangeable.

​
Execution-path boundary

Not every Guest request invokes a model. Current deterministic paths can complete before the Responses API call:
Model-bearing conversation turns use the Guest-owned Responses API path. Health/config responses and deterministic outcomes must never be documented as model execution proof.

​
Verification, privacy, and operator boundary

The hardening roadmap starts from these implemented invariants:
The Guest Agent does not guarantee automatic operator handoff. It must not say it alerted, notified, messaged, sent, connected, or confirmed with the team unless an independently proven workflow supports that exact claim. When configured, the Guest server may deliver a signed, privacy-reduced operational signal for later operator review. Signal delivery is not human action, booking linkage, or completion proof.

​
Near-term hardening

Near-term work:

​
Historical controlled-reservations proof — 2026-06-11

On 2026-06-11, an accepted controlled development receipt recorded this seed/test path:
That receipt is dated architecture evidence. It does not establish deployment or live verification after 2026-06-11, and it is not production booking readiness.

​
Future property reservation settings

Reservation rules should move from Villa Valentin v0 defaults into owner/operator-configured settings:

​
Admin and operator surface

Needed Admin work:

​
Eval Labs surface

​
Implemented bounded check

The Guest Facing Agent Verification Check is implemented in Eval Labs for deterministic booked-guest verification scenarios against Guest Agent Production. That implementation statement is supported by Eval Labs owning source and deployed release identity 6cbfd15f75330c414bfe79e0d2fab51ef8115102, reviewed on 2026-08-12. The review established the check surface and its target contract. It did not execute the check, inspect a fresh authenticated result, or provide a current pass or launch-readiness result.

​
Requested/future broader battery

The broader first-class Guest-Facing Lucia Eval Track remains Requested with capability status future. Its required coverage includes:

​
Production readiness gate

Guest-facing Lucia should not be treated as production-ready until the system has:
Production readiness must not be inferred from a health 200, a configured model name, a successful deterministic response, an accepted operational signal, or the July 2026 deployment evidence alone. By the founder’s September order, guest-facing hardening and the guest agent’s model mix begin only after Fieldwork and Admin speak one language and the Algorithm proves it understands intake (ALGO-41, 2026-09-04).

​
Doctrine to preserve

The hardening path must preserve the product soul:
Warmth and privacy discipline must advance together.