> ## Documentation Index
> Fetch the complete documentation index at: https://helloluciallc.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Guest-Facing Roadmap

<Note>
  Guest-facing Lucia has crossed from future concept into implemented live-development infrastructure, but production readiness still requires verification, persistence, Admin review, security, and Eval Labs hardening.
</Note>

***

## Current Implemented Baseline

Current product milestone:

```text theme={"dark"}
Guest Agent v0.1.0 - Guest Identity + Magic-Link Lab
```

Current baseline:

```text theme={"dark"}
guest-facing Lucia lab page
guest-facing concierge independently configured for gpt-5.6-sol through VV_AI_MODEL
gpt-5.6-sol source fallback
OpenAI Responses API model gateway
text-embedding-3-small embeddings
identity orientation before chat
booked-guest claim collection
claim fragment memory for booked verification
Engine candidate lookup
operational_signal v0 generation
server-side signed signal posting from guest agent
Engine signed guest signal intake
Engine guest signal persistence
Admin guest_signals exposure
Admin Signal Stream guest signal rendering
identity/linkage normalization
magic-link verification v0
Resend verification email delivery
verified session state
verified-session recognition after magic-link click
guest-agent resend/status intent split
safe verification_expires_at metadata in pending guest-agent state
controlled/test guest reservations through /reservations
Engine seed booking endpoint
Engine seed booking availability endpoint
Guest Agent server-side HMAC signing boundary
Admin calendar visibility for generated seed bookings
branded Engine verification result page
```

The 2026-07-12 Guest Agent model upgrade is complete on `hello-lucia/lucia-guest-agent` `main` at source commit `826a6a14e2fa95bfd60c8008fb0cdc9d846b4231`. The production override and source fallback are both `gpt-5.6-sol`, and live verification returned `gpt-5.6-sol` from the provider.

Lucia Engine currently uses the same model name through a separate configuration and verification boundary. Neither surface inherits the other's model selection or runtime proof.

The model-only upgrade left prompts, verification flow, routing, schemas, and the core SSE events `start`, `token`, `cta`, `meta`, and `done` unchanged. This is implemented live-development state, not a broader production-readiness claim.

***

## Versioning Boundary

Guest-facing product versioning separates engineering identity from product milestone truth.

```text theme={"dark"}
commit tag = engineering truth
product version = milestone/product truth
```

The UI should eventually show both:

```text theme={"dark"}
Guest v0.1.0 · <commit>
```

***

## Near-Term Hardening

Near-term work:

```text theme={"dark"}
automated testing of guest verification combinations
Eval Labs guest identity battery
Admin guest signal review/link surface
owner/operator-configured reservation settings
production-grade booking/payment/OTA integration decisions
durable persistence for guest signals and verification state
rate limiting / replay / spam hardening
operator-linked booking verification
inquiry record support
guest-of-guest verification paths
production privacy/consent copy
Villa Valentin launch hardening
```

***

## Controlled Reservations Proof

The first guest-facing reservation loop is now proven live as a controlled seed/test path:

```text theme={"dark"}
guest creates a controlled/test Villa reservation with an owned/test email
Engine persists the seed booking in booking truth
booking appears in Admin calendar
guest later claims the booking in Guest Agent
Engine sends magic-link verification only to the booking email on file
verified session enables booking-specific guest planning
```

This is architecture proof, not production booking readiness.

***

## Future Property Reservation Settings

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

```text theme={"dark"}
minimum nights
same-day turnover allowed
check-in/check-out rules
property/unit availability rules
booking windows
hold/confirmed/tentative statuses
guest-facing reservation constraints
```

***

## Admin and Operator Surface

Needed Admin work:

```text theme={"dark"}
operator review/link UI for guest signals
clear candidate vs verified display
safe link/unlink audit trail
guest signal detail surface
controlled DAW escalation for verified/operator-linked signals
```

***

## Eval Labs Surface

Needed Eval Labs work:

```text theme={"dark"}
first-class Guest-Facing Lucia Eval Track
guest identity orientation battery
guest claim-strength battery
magic-link verification battery
privacy leakage battery
guest-to-operator routing battery
hospitality tone regression battery
Focus Ops no-drift battery for unlinked/candidate signals
```

***

## Production Readiness Gate

Guest-facing Lucia should not be treated as production-ready until the system has:

```text theme={"dark"}
durable verification/session persistence
rate-limit and replay protection
spam/abuse hardening
reviewed privacy and consent copy
operator review/link tooling
live and Eval Labs proof for verified session context, resend/status, expiry, and privacy boundaries
Eval Labs coverage for all critical guest identity states
production-grade booking/payment/OTA integration decisions
owner/operator-configured reservation constraints
Villa Valentin launch-specific proof
```

***

## Doctrine to Preserve

The hardening path must preserve the product soul:

```text theme={"dark"}
Guest-facing Lucia is a front-of-house teammate.
Operator-facing Lucia is a calm operating partner.
Eval Labs is the proof/regression system.
```

Warmth and privacy discipline must advance together.