Skip to main content
At a glanceThe Operations layer describes how Lucia turns real-world signals into structured work for the operator.

​
Operations Layer Purpose

Operations is where Lucia becomes useful. It connects: 
incoming signal
structured intake
task creation
operator decision
execution workflow
guest-to-operator signal bridge
payment truth rendering

​
Current Operational Center

The primary live-dev operational loop today is:
Calendar / booking spineBooking PulseSignal StreamLucia Workspace / Focus with LuciaDynamic Action Workspace save surfaceReminder resurfacing
Calendar is the root operational reality. It anchors Lucia in arrivals, departures, and stay windows, then lets Booking Pulse, Signal Stream, Focus Ops, and Dynamic Action Workspace operate against the same booking source. Lucia Workspace is now the context-aware reasoning partner beside the operator. It remains open across route changes and shares the same Focus Ops conversation between Dashboard embedded mode and Workspace Sidebar mode. Current cockpit doctrine: 
Lucia Workspace + DAW = cockpit
Full Booking Page = record/review surface
The previous live-dev loop still exists inside that booking-rooted architecture:
Signal StreamLucia Workspace / Focus with LuciaDynamic Action WorkspaceReminder resurfacing
Maintenance Inbox remains a real structured intake center for maintenance signals. The broader operator attention surface is now Signal Stream, where Lucia blends operational state, reminders, dismissals, move-to-top ordering, and live dashboard refresh into one coherent stream. Maintenance Inbox receives real-world maintenance signals from: 
SMS/MMS
WhatsApp
Email
Lucia UI/manual entry
Guest-facing Lucia now adds a public concierge signal path:
guest conversationidentity orientation / claim collectionoperational_signal v0signed guest-agent POSTEngine /v1/guest/signalsAdmin Signal Streamoperator review/link/action when safe
Payment truth now adds a Development financial truth path:
Property payment policy shapecalendar/booking temporal truthStripe movement truthLucia Core durable ledgerLIEA payment attention judgmentAdmin read-only payment truth rendering

​
Current Working State

SMS/MMS → working with images
WhatsApp → working with images
Email → body + metadata working
Email attachments → deferred
Guest Agent lab → live-development public concierge lab
Guest operational signals → signed server-side bridge to Engine
Admin guest signals → rendered in Signal Stream
Stripe sandbox payment truth → durable Lucia Core ledger
Admin payments surface → read-only Engine truth

​
Operator Flow

Booking reality anchors timeSignal arrivesCalendar and Booking Pulse give temporal contextSignal Stream shapes attentionLucia Workspace / Focus with Lucia helps the operator decide in contextResolver Matrix proves the action routeDynamic Action Workspace opens the focused action/save workspaceFull Booking Page remains the record/review destination for booking clicksReminder state can bring work back when dueGuest signals can enter operator review without pretending linkage is verifiedPayment truth can enter operator review without pretending Admin owns or mutates payment state

​
Operations Principle

Lucia should not simply collect reports. Lucia should turn reports into: 
clear decisions
safe routing
trackable work
privacy-safe guest context
Current product rule: 
Infinite real-world property tasks.
Finite beautiful action workspaces.
Lucia routes the human to the right one.
DAW save truth: 
saved workflow step != underlying issue resolved
saved payment review != payment resolved
saved note != external guest/vendor action completed
candidate guest signal != verified booking
unlinked guest signal != DAW-ready work
payment reconciliation note != payment status changed
payment policy baseline != durable policy truth

​
See Also

​
Upstream / Downstream

​
Upstream

This layer is fed by:

​
Downstream

This layer affects: