Skip to main content
Lucia Canon v1.0 Lucia turns real-world hospitality signals into clear operator decisions, trusted workflows, and calmer ownership.
Lucia is the front door to a proprietary hospitality intelligence system built to turn operational noise into calm, trusted execution. This library defines the architecture, doctrine, workflows, and decision logic behind an AI operating layer designed for owners, teams, guests, and long-term property performance.
Lucia primary avatar

Primary Lucia avatar

Who Lucia Is

Lucia is an AI built for hospitality operators and their guests — though that framing undersells her. She feels less like software and more like the calm, capable person you wish was sitting beside you when the day gets messy. The kind of teammate who reads a room before she speaks, knows when to step in and when to hold back, and somehow makes everything feel a little more handled the moment she joins the conversation. She is steady, warm, attentive, and quietly sharp. Lucia reads the operational signals around the property — arrivals, departures, stay windows, payments, maintenance flags, concierge requests, the quiet things guests don’t say out loud — and she senses the pressure the operator is carrying underneath all of it. Her job is to take the noise of running a property and shape it into one clear next move. Not a feed. Not a dashboard. A direction. She doesn’t flood the operator with detail or perform her own helpfulness. She narrows the field, protects the operator’s attention, and keeps the work moving — without ever making ownership feel heavier than it already is. She is not a chatbot. She is not a dashboard. She is becoming the context-aware operating layer for hospitality work — one that stays beside the operator, helps people think more clearly, act more confidently, and take better care of both their guests and themselves.

What Lucia Is

This Library frames Lucia’s hospitality intelligence system through three enduring product-family lenses:
These three items organize the product story and documentation. They are not a complete count of repositories, deployed services, or private operating surfaces. For dated runtime ownership, environments, release identity, and evidence boundaries across the full fleet, use Current System State.
At the practical level, Lucia does one thing extremely well: take real-world operational signals and tell the operator what to do next. Lucia is built to reduce overwhelm, remove ambiguity, surface the single most important action, preserve trust-state discipline, and keep ownership calm and controlled.

The Core System Rule

The Operator System is the current operating cockpit: Focus Ops, Calendar, Signal Stream, Dynamic Action Workspace, Full Booking Page, task routing, and decision support. The Guest-Facing System is a distinct public concierge surface: the Lucia guest lab, identity orientation, privacy-safe claim collection, guest operational signals, and magic-link booking verification. Guest-facing Lucia may help before verification, but operator/system truth still controls booking-private data, verified linkage, and mutations.

Quick Start

System Architecture

How signals become structured operator decisions.

The Intelligence Layer

Intent, focus, reasoning — plus the Human Guidance Engine.

Branding & Identity

Lucia’s voice, color, and visual system.

Real Operations

The Calendar & Booking Spine and Maintenance Workflow.

Workspace OS Milestone

The context-aware operator companion.

Guest-Facing Lucia

The public concierge surface and identity discipline.

Current surface status

As of 2026-08-12 · last verified 2026-08-12. This is a concise orientation layer. Current System State owns the detailed fleet matrix and attributes each claim to owning repository source, accepted release receipts, or explicitly dated runtime proof.
  • Operator Lucia — active Development operator surface; Admin presents Engine-owned runtime and intelligence truth.
  • Lucia Guest Agent — deployed as a controlled-preview guest product; its production hosting context does not imply broad product readiness.
  • Lucia Fieldwork — production employee operations app and API under active development.
  • Eval Labs — production internal evaluation and evidence platform; it records proof without taking ownership of Lucia’s generating runtime.
  • Workbench — separately owned private operator tooling outside this public Library.
  • Fleet Control Scanner — candidate source exists; it is not deployed.
  • Symphony-derived executor — architectural candidate only; it is not installed or deployed.
These status labels are orientation, not detailed topology or a fleet-wide readiness claim.

Evals and Improving Lucia

EvaluationLabs.ai is Lucia’s evaluation and evidence platform. Eval Labs evaluates behavior, records evidence, and informs human-reviewed improvements. It does not train Lucia or own the generating model. Evaluation covers not just accuracy but warmth, humanity, empathy, and judgment in real operational moments.
Read on: Evaluation System · Eval Labs Platform

Best Reading Order

1

Mission and Mandate

2

System Architecture

3

Branding and Identity

4

Intelligence Layer

5

Guest-Facing Lucia

6

Operations, Infrastructure, Evaluation

System Navigation

Current System State

How to Use This Canon

Historical Obsidian Canon Map

Canon Update Ritual

Navigation Shortcuts

Source-truth discipline. If reality changes, the Canon changes. If the Canon claims something is implemented, it must be implemented or explicitly marked as future/deferred.