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

# START HERE - Operations

<Note>
  **At a glance**

  The Operations layer describes how Lucia turns real-world signals into structured work for the operator.
</Note>

***

## Operations Layer Purpose

Operations is where Lucia becomes useful.

It connects:

```text theme={"dark"}
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:

<div className="hl-flow-v"><span>Calendar / booking spine</span><span>Booking Pulse</span><span>Signal Stream</span><span>Lucia Workspace / Focus with Lucia</span><span>Dynamic Action Workspace save surface</span><span>Reminder resurfacing</span></div>

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:

```text theme={"dark"}
Lucia Workspace + DAW = cockpit
Full Booking Page = record/review surface
```

The previous live-dev loop still exists inside that booking-rooted architecture:

<div className="hl-flow-v"><span>Signal Stream</span><span>Lucia Workspace / Focus with Lucia</span><span>Dynamic Action Workspace</span><span>Reminder resurfacing</span></div>

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:

```text theme={"dark"}
SMS/MMS
WhatsApp
Email
Lucia UI/manual entry
```

Guest-facing Lucia now adds a public concierge signal path:

<div className="hl-flow-v"><span>guest conversation</span><span>identity orientation / claim collection</span><span>operational\_signal v0</span><span>signed guest-agent POST</span><span>Engine /v1/guest/signals</span><span>Admin Signal Stream</span><span>operator review/link/action when safe</span></div>

Payment truth now adds a Development financial truth path:

<div className="hl-flow-v"><span>Property payment policy shape</span><span>calendar/booking temporal truth</span><span>Stripe movement truth</span><span>Lucia Core durable ledger</span><span>LIEA payment attention judgment</span><span>Admin read-only payment truth rendering</span></div>

***

## Current Working State

```text theme={"dark"}
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

<div className="hl-flow-v"><span>Booking reality anchors time</span><span>Signal arrives</span><span>Calendar and Booking Pulse give temporal context</span><span>Signal Stream shapes attention</span><span>Lucia Workspace / Focus with Lucia helps the operator decide in context</span><span>Resolver Matrix proves the action route</span><span>Dynamic Action Workspace opens the focused action/save workspace</span><span>Full Booking Page remains the record/review destination for booking clicks</span><span>Reminder state can bring work back when due</span><span>Guest signals can enter operator review without pretending linkage is verified</span><span>Payment truth can enter operator review without pretending Admin owns or mutates payment state</span></div>

***

## Operations Principle

Lucia should not simply collect reports.

Lucia should turn reports into:

```text theme={"dark"}
clear decisions
safe routing
trackable work
privacy-safe guest context
```

Current product rule:

```text theme={"dark"}
Infinite real-world property tasks.
Finite beautiful action workspaces.
Lucia routes the human to the right one.
```

DAW save truth:

```text theme={"dark"}
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

* [01 - Maintenance Workflow](/lucia/operations/maintenance-workflow)
* [02 - Task Creation and Routing](/lucia/operations/task-creation-and-routing)
* [06 - Calendar and Booking Spine](/lucia/operations/calendar-and-booking-spine)
* [Lucia Payment Truth Foundation](/lucia/system-architecture/lucia-payment-truth-foundation)
* [05 - Guest-to-Operator Bridge](/lucia/guest-facing-lucia/guest-to-operator-bridge)
* [02 - Guest Operational Signals](/lucia/guest-facing-lucia/guest-operational-signals)
* [04 - Lucia Workspace OS Milestone](/lucia/system-architecture/lucia-workspace-os-milestone)
* [01 - Ingestion Layer](/lucia/system-architecture/ingestion-layer)
* [02 - Focus Ops Intelligence](/lucia/intelligence/focus-ops-intelligence)

***

## Upstream / Downstream

### Upstream

This layer is fed by:

* [02 - Current System State](/lucia/start-here-lucia-ai/current-system-state)
* [00 - START HERE - System Architecture](/lucia/system-architecture/start-here-system-architecture)

### Downstream

This layer affects:

* [00 - START HERE - Operations](/lucia/operations/start-here-operations)
* [00 - START HERE - Evaluation System](/lucia/evaluation/start-here-evaluation-system)
* [Lucia Decision Log](/lucia/decisions/lucia-decision-log)