Lucia is moving from dashboard-bound AI chat into a context-aware hospitality operating layer that stays beside the operator while work happens.
Milestone Definition
This milestone records Lucia’s Development/v0.1.x transition:
from: AI chat embedded in a dashboard
to: context-aware hospitality operating system with Lucia beside the operator
Core Doctrine
Lucia is becoming the operating layer for hospitality work.
The operator should be able to:
open Lucia beside the app
navigate through Calendar, Signal Stream, DAW, Full Booking, Tasks, Concierge, Maintenance, and Reconciliation
keep the same Lucia conversation alive
ask what they are looking at
ask what to do here
ask what comes next
save work in DAW
return to booking records later
Lucia Workspace + DAW = cockpit
Full Booking Page = record/review surface
Current Development Implementation
Current Admin Development truth:
Lucia Workspace Sidebar Mode is implemented
Top shell opens Workspace from the top-left icon and Open Workspace action
Old sidebar navigation is bypassed/removed from active shell behavior
Topbar spans the full browser width
Workspace body sits below the topbar
Lucia sidebar and app workspace are side-by-side at 1000px+
Lucia sidebar is resizable from 260px to 460px
Lucia sidebar width preference persists
Workspace open/closed state persists across refresh
Lucia Workspace remains open across route changes
Same Focus Ops conversation is shared between Dashboard embedded mode and Workspace Sidebar mode
Signal Stream Chat seeds the shared Lucia conversation
Reset clears the shared conversation and context
Workspace context is sent through active_context.workspace
Workspace sidebar visual polish is complete for 260/320/380/460px widths
Dashboard Focus Ops composer breakpoint bug is fixed around 1280px
Engine normalizes active_context.workspace safely
Lucia can answer workspace-orientation and workspace-next-step prompts using current surface context
Supported surfaces include Dashboard, Calendar, DAW, Full Booking, Bookings, Maintenance, Concierge, Tasks, and Reconciliation
Explicit prompt subject still wins over page context
Lucia avoids raw metadata language such as active_context, current_surface, payload, and metadata
Strict brain quality eval reached 178/178 after workspace-context awareness
What am I looking at?
What should I do here?
What matters for this booking?
What should I pay attention to here?
Now what?
DAW as Action and Save Surface
DAW is now the action/work surface, not a copy-to-clipboard scratchpad.
Normal DAW workflows require a persistence target:
task-backed save
concierge request save
booking-note-backed save
insufficient-context bridge/fallback
Primary button: Save this step.
Saved confirmation: Saved.
active_context.workspace.
Important truth-state boundary:
saved workflow step != underlying issue resolved
saved payment review != payment resolved
saved arrival note != arrival details changed
saved note != external guest/vendor action completed
Review Nora Ibrahim's payment.
Review this guest's payment.
Architecture Doctrine
The current architecture doctrine is:
Calendar = temporal spine / booking reality
Booking Pulse = operational rhythm
Signal Stream = attention layer
Lucia Workspace = reasoning partner beside the operator
DAW = action/save surface
Full Booking Page = record/review surface
Eval Labs = proof/regression system
Guest-Facing Lucia = public concierge and claim/signal bridge
Guest-Facing Extension
Since this milestone, guest-facing Lucia has become its own live-development product surface rather than only a future concierge concept.
Current guest-facing extension:
Guest Agent lab exists at https://lucia-guest-agent.netlify.app/lucia-lab/
identity orientation happens before normal chat
guest operational_signal v0 can be generated
guest agent signs and POSTs signals server-side to Engine
Engine accepts signed guest signals through /v1/guest/signals
Admin Signal Stream renders guest signals
candidate/unlinked guest signals do not fake DAW routing
Magic Link Booking Verification v0 is implemented
Truth-State Boundaries
Lucia may orient the operator to the current surface.
Lucia may explain what matters on the current page.
Lucia may recommend the next safe action.
Lucia may acknowledge that a DAW step was saved when the system reports it as saved.
Lucia must not:
claim production readiness
claim staging promotion
invent missing booking, calendar, task, payment, or guest facts
turn missing counts into fake zero-count language
describe saved workflow steps as resolved operational issues
expose raw implementation language to the operator
Known Limitations
Current known limits:
Calendar context awareness is functional but still needs richer visible-month and booking-detail context
Guest-facing Lucia exists in live-development but still needs production hardening
Billing, users, permissions, payment gateway, and subscription systems are not yet complete
Below-1000px Workspace UI is not the main v1 target
Production and staging readiness are not claimed
Villa Valentin launch still requires product hardening and real onboarding/payment policy work
Future Roadmap
Future work is separate from current implementation:
richer Calendar context sent to Engine
automated testing of guest verification combinations
Eval Labs guest identity battery
Admin guest signal review/link surface
verified session use in guest-agent conversation context
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 guest-facing launch hardening
onboarding/property profile/payment policy capture
users and permissions
billing/payment gateway/subscriptions
production hardening
Villa Valentin exclusive live launch
eventual Lucia sidebar/avatar inside DAW and other sections
booking-level work queue / all workable DAW items per booking
mobile/tablet Workspace UX later
See Also
