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:

​
Current Live-Dev Product Flow

Core doctrine:
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.6 Sol, OpenAI Responses API

​
Independent Model Configuration Boundaries

The matching model name does not create inheritance between the two surfaces. Each owns its configuration, deployment, and runtime verification. Both use the OpenAI Responses API; Guest Agent embeddings remain text-embedding-3-small. The Guest Agent model-only upgrade preserved prompts, verification flow, routing, schemas, and the core SSE events start, token, cta, meta, and done. Guest Agent does not expose or persist the Engine’s /admin/operator-focus provenance contract.

​
Focus Ops Runtime Evidence Flow

Eval Labs productionDevelopment /admin/operator-focusstable ok / data / meta responsemeta.runtime + meta.model_runtimeowner verification + per-run provenance
The Engine keeps operational output in data and exposes evidence in meta; provenance does not replace or reshape the stable response contract. Runtime identity reports the Engine environment and commit. Model-runtime evidence reports the configured model, provider-resolved model, model-invoked state, deterministic-path state, fallback state, and task outcomes. This architecture records model invocation versus no-attempt deterministic execution, proves provider-backed success through task evidence, and records fallback independently. Eval Labs persists captured evidence for new runs and explicitly reports that provenance was not captured for historical runs that lack it.

​
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:
Not yet implemented:

​
Guest Verification Boundary

Current guest verification architecture:
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 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.