Skip to main content
Lucia converts external signals into structured decisions.

​
Flow

ExternalIngestionNormalizationIntelligenceWorkspace ContextExecutionSaved WorkUI
Guest-facing flow:
guest conversationidentity orientation / claim collectionsigned operational_signal v0Engine guest signal normalizationAdmin Signal Stream review/link surfaceFocus Ops context when safe

​
Temporal Spine

Calendar is Lucia’s temporal spine. Lucia is situationally aware because the system is grounded in: 
arrivals
departures
stay windows
booking identity

​
Current Live-Dev Product Flow

Calendar / booking spine
→ Booking Pulse
→ Signal Stream
→ Lucia Workspace / Focus with Lucia
→ Resolver Matrix
→ Dynamic Action Workspace for action/save work

Calendar booking click
→ Full Booking Page for record/review

Eval Labs
→ behavioral proof and regression protection

Guest-Facing Lucia
→ public concierge, identity/linkage discipline, and guest-to-operator signal bridge

Payment Truth Foundation
→ policy shape, booking timing, Stripe movement truth, durable ledger, LIEA attention judgment, and Admin read-only rendering
Core doctrine: 
Calendar = root operational reality.
Lucia Workspace = context-aware reasoning partner beside the operator.
Infinite real-world property tasks.
Finite beautiful action workspaces.
Lucia routes the human to the right one.
Lucia Workspace + DAW = cockpit.
Full Booking Page = record/review surface.
Guest-facing Lucia = front-of-house concierge.
Guest-to-Operator Bridge = structured privacy-safe operational signal path.
Eval Labs = proof/regression system.
Payment truth separates owed policy, Stripe movement, durable storage, attention judgment, and Admin rendering.
This is Development/live-dev runtime truth, not production readiness. See 04 - Lucia Workspace OS Milestone for the current Workspace OS milestone. See 00 - START HERE - Guest-Facing Lucia for the current guest-facing Lucia milestone. See Lucia Payment Truth Foundation for the current payment truth foundation.

​
Stack

Twilio, Postmark, Bunny, Engine, Admin UI, Guest Agent, Resend, Supabase, Stripe sandbox, GPT-5.5

​
Payment Truth Boundary

Current payment truth architecture:
Property policy truthcalendar/booking temporal truthStripe movement truthLucia Core durable ledgerLIEA financial judgmentAdmin payment truth rendering
Implemented Development truth: 
Durable Stripe movement truth is implemented.
Lucia Core Supabase durable ledger is configured and tested in Development.
LIEA consumes Stripe financial truth for payment attention suppression.
Admin renders Engine payment truth read-only.
Property Payment Policy v0 is visible in Admin as draft/no-persistence baseline only.
Not yet implemented: 
Durable Engine-owned property payment policy truth.
Signal Stream -> LIEA wiring.
Admin payment writes or payment creation/refund/mark-paid UI.
Full policy-aware due/overdue/partial/pending judgment.

​
Guest Verification Boundary

Current guest verification architecture: 
Candidate Booking Lookup Helper v0
Magic Link Verification Token + Session State v0
Magic Link Verification endpoints v0
Resend-backed verification email delivery
Verification emails go only to the booking email already on file. Guest-entered email is never trusted as the destination. Guest verification proves linkage. It does not grant unrestricted mutation access.

​
Environments

dev active, stage validation

​
Build Identity

Current live-dev build identity: 
The live-dev topbar displays Admin and Engine build identity.
Admin build identity is injected at Admin build time.
Engine build identity is fetched from the Engine root endpoint.
The tag is runtime evidence for the currently deployed Admin/Engine pair. Canon may document the identity mechanism, but must not hardcode volatile commit hashes as system truth.