> ## Documentation Index > Fetch the complete documentation index at: https://helloluciallc.com/llms.txt > Use this file to discover all available pages before exploring further. # Current System State This page records what is true right now. It should be updated whenever Lucia’s runtime, routing, or launch reality changes. *** ## Live Transition Status ```text theme={"dark"} Status: active live-transition Current baseline: v0.1.3.6 Primary client context: Villa Valentin Primary active environment: Development Validation environment: Staging Production: future Marketing/waitlist surface: live Guest Agent: production deployment of a live-development product surface ``` Lucia v0.1.3.6 remains the current Development baseline for Engine behavior, Admin UI, CI gates, and Eval Labs review. Eval Labs production routing is aligned to Development as of the correction live-verified on 2026-07-10; the earlier routing drift is recorded below rather than erased. Current live-dev build identity: ```text theme={"dark"} 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 Admin/Engine build identity tag is runtime evidence for the currently deployed Admin/Engine pair, not decorative copy. Canon must not hardcode or fake deploy identity and should not record volatile commit hashes as doctrine. Staging promotion is intentionally held until Eval Labs captures and reviews the v0.1.3.6 Development behavior baseline. *** ## Current Version Stack ```text theme={"dark"} Engine local workspace: engine-v0.1.3.6 Admin local workspace: admin-v0.1.3.6 Guest Agent local workspace: lucia-guest-agent Guest Agent product milestone: v0.1.0 - Guest Identity + Magic-Link Lab Guest Agent branch: main Guest Agent source commit: 826a6a14e2fa95bfd60c8008fb0cdc9d846b4231 Engine branch: dev Admin branch: dev ``` Current payment truth development proof snapshot: ```text theme={"dark"} Admin live-dev visible commit tag: 7c9683a Engine live-dev visible commit tag: 88a09a1 Payment truth proof environment: Development/live-dev Production readiness: not claimed Staging promotion: not claimed ``` *** ## Current Product Lines HelloLucia, LLC currently owns three major product lines: ```text theme={"dark"} Lucia AI - Operator / Owner-Facing OS Lucia AI - Public / Guest-Facing Concierge Eval Labs - Evaluation + Regression System ``` Current Canon boundary: ```text theme={"dark"} operator-facing Lucia = calm operating partner and action cockpit guest-facing Lucia = public front-of-house concierge and claim/signal bridge Eval Labs = proof, review, and regression system ``` This product-line framing does not claim that guest-facing Lucia is fully production-hardened. *** ## Active Public Surfaces Development: ```text theme={"dark"} https://dev.hellolucia.ai https://api-dev.hellolucia.ai ``` Current payment truth development surfaces tested: ```text theme={"dark"} https://dev.hellolucia.ai/property https://dev.hellolucia.ai/payments https://dev.hellolucia.ai/bookings/29110012 https://dev.hellolucia.ai/ops/actions?intent=payment_reconciliation&booking_id=29110012&focus=payment_reconciliation ``` Staging: ```text theme={"dark"} https://staging.hellolucia.ai https://api-staging.hellolucia.ai ``` Evaluation: ```text theme={"dark"} https://evaluationlabs.ai ``` Guest-Facing Lucia: ```text theme={"dark"} https://guest.hellolucia.ai https://lucia-guest-agent.netlify.app/lucia-lab/ ``` Marketing / Waitlist: ```text theme={"dark"} https://hellolucia.ai https://hellolucia.ai/api/waitlist ``` Documentation Library: ```text theme={"dark"} https://helloluciallc.com ``` *** ## Documentation Library HelloLucia, LLC documentation is published as one unified **Mintlify library** at `helloluciallc.com`. Its product switcher has three documentation homes: **Lucia**, **Lucia Fieldwork**, and **Eval Labs**. ```text theme={"dark"} Canonical source: hello-lucia/lucia-library (git, MDX) Published library: https://helloluciallc.com Products: Lucia + Lucia Fieldwork + Eval Labs Legacy site: https://docs.hellolucia.ai — still live, non-canonical, no redirect Legacy site: https://docs.evaluationlabs.ai — still live, non-canonical, no redirect Historical Obsidian vaults: read-only import material, not an authoring or sync authority ``` This repository and its Mintlify deployment replace the two Obsidian Publish sites as the canonical documentation home. The legacy sites’ continued availability is not redirect proof and does not give them current source-truth status. See [ADR - Unify Docs into Mintlify Library](/lucia/decisions/adr-unify-docs-into-mintlify-library). *** ## Current External Routing ```text theme={"dark"} Twilio SMS/MMS → api-dev Twilio WhatsApp → api-dev Postmark inbound email → api-dev Eval Labs production → https://api-dev.hellolucia.ai/admin/operator-focus Resend waitlist and guest verification outbound email → send.hellolucia.ai Guest Agent operational signals → api-dev /v1/guest/signals ``` Staging can receive these signals but is not targeted unless provider webhooks are manually switched. The live Eval Labs app resolves to: ```text theme={"dark"} VITE_LUCIA_EVAL_ENDPOINT=https://api-dev.hellolucia.ai/admin/operator-focus ``` A Netlify redeploy is required after changing that Vite environment variable. Confirmed routing history: ```text theme={"dark"} Uninterrupted Staging-target configuration began: 2026-05-04T16:21:35Z Routing correction and live Development verification: 2026-07-10 Current target: https://api-dev.hellolucia.ai/admin/operator-focus ``` This establishes a continuous routing-configuration drift window. It does **not** prove that every individual historical run in that interval executed against Staging, and historical run records must not be rewritten to imply evidence they did not capture. Eval Labs now exposes an owner-only **Lucia Runtime Verification** dashboard. It reads provenance from the same `/admin/operator-focus` response that produced the answer and shows the resolved endpoint, classified environment, Engine commit SHA, configured model, provider-resolved model, model-invoked state, deterministic-path state, fallback state, and verification timestamp. *** ## Operating Loop Lucia is moving away from localhost-first development. ```text theme={"dark"} Live internet development infrastructure → real operating loop localhost → isolated debugging only ``` *** ## Workspace OS Milestone Lucia has crossed the Workspace OS / context-aware operator companion milestone in Development/v0.1.x. The product transition is: ```text theme={"dark"} from: AI chat embedded in a dashboard to: context-aware hospitality operating system with Lucia beside the operator ``` Current doctrine: ```text theme={"dark"} Lucia is becoming the operating layer for hospitality work. The operator can keep Lucia beside the app while moving through the workspace. The same Lucia conversation should survive route changes and mode changes. Lucia can orient to the current surface and recommend the next safe move. ``` This is Development/live-dev runtime truth. It is not a production-readiness or staging-promotion claim. *** ## Guest-Facing Lucia Milestone Guest-facing Lucia has crossed from future concept into a distinct live-development product surface. Current guest-facing runtime truth: ```text theme={"dark"} Product milestone: Guest Agent v0.1.0 - Guest Identity + Magic-Link Lab GitHub repo: hello-lucia/lucia-guest-agent Local path: /Users/avivhadar/Desktop/lucia-guest-agent Branch: main Source commit: 826a6a14e2fa95bfd60c8008fb0cdc9d846b4231 Production URL: https://guest.hellolucia.ai/ Live lab: https://lucia-guest-agent.netlify.app/lucia-lab/ Guest Agent build tag is visible on the page Default model: gpt-5.6-sol (GPT-5.6 Sol) Production override: VV_AI_MODEL=gpt-5.6-sol Source fallback: gpt-5.6-sol Model gateway: OpenAI Responses API Embeddings model: text-embedding-3-small Live provider-returned model proof: gpt-5.6-sol Model boundary: independently configured and verified from Lucia Engine ``` Lucia Engine and Lucia Guest Agent both currently use `gpt-5.6-sol`, but neither inherits configuration or runtime proof from the other. The Engine exposes same-response runtime provenance through `/admin/operator-focus`; the Guest Agent does not expose or persist that Engine provenance contract. The Guest Agent's provider-returned model was verified independently on 2026-07-12. Guest Agent v0.1.0 definition: ```text theme={"dark"} first working guest-facing Lucia lab guest-facing concierge independently configured for gpt-5.6-sol through VV_AI_MODEL identity orientation handshake booked-guest claim collection claim fragment memory Engine candidate lookup Resend magic-link verification verified session state guest operational signal bridge Admin Signal Stream visibility foundation ``` Versioning boundary: ```text theme={"dark"} commit tag = engineering truth product version = milestone/product truth future UI target = Guest v0.1.0 · ``` Current guest-facing UI truth: ```text theme={"dark"} Villa/Lucia-style lab page created and polished editorial visual system: Canela, nucleus divider, black top bar, refined chat card guest identity orientation lives inside Lucia's first message guest must select identity orientation before chatting orientation prompt appears in the composer guest sends the orientation prompt identity buttons disappear normal conversation begins ``` Identity orientation options: ```text theme={"dark"} I'm already booked I'm joining someone's stay I'm planning a trip Just exploring ``` Current guest verification and signal truth: ```text theme={"dark"} identity/linkage contract implemented guest operational_signal v0 generated guest agent signs and POSTs signals server-side to Engine Engine accepts signed guest signals through /v1/guest/signals Engine persists guest signals safely Admin /admin/dashboard exposes sections.guest_signals Admin Signal Stream renders guest signals candidate/unlinked guest signals do not open fake DAW Magic Link Booking Verification v0 implemented Resend-backed verification email delivery implemented verified session state implemented prompts, verification flow, routing, and schemas unchanged by the model upgrade core SSE events preserved: start, token, cta, meta, done ``` This is implemented live-development state. Runtime files, persistence, rate limits, replay/spam protection, Admin review/link tooling, and launch privacy copy still need hardening before production readiness is claimed. Guest-facing Lucia also requires a first-class Guest-Facing Lucia Eval Track in Eval Labs, separate from operator-facing Lucia evals. Manual testing cannot cover every possible guest phrasing, so Eval Labs must stress-test guest identity, verification, privacy, tone, and guest-to-operator routing at scale. *** ## Payment Truth Foundation Lucia has completed the Development payment truth foundation across Stripe sandbox movement truth, Lucia Core durable ledger storage, LIEA payment attention suppression, and Admin read-only rendering. Current implemented Development truth: ```text theme={"dark"} Stripe sandbox checkout foundation implemented in Engine Lucia Core Supabase development project exists: lucia-core-dev / jgnxomyzqotnqsmlxlsz Durable Stripe ledger tables exist: stripe_financial_records and stripe_financial_events RLS is enabled on both durable ledger tables No anon/auth read policies exist for the durable ledger tables Engine uses service-role-only Supabase access Admin never talks directly to Supabase Engine durable ledger mode is configured as dual with durable-required in Render Development Admin /payments renders global durable Engine payment truth Booking detail renders a read-only Payment Truth card Admin /property renders Payment Policy Baseline v0 as read-only/draft-safe only DAW payment reconciliation can open context without mutating payment state ``` Tested live-dev proof: ```text theme={"dark"} Harper Quinn booking #29110012 completed a $500.00 Stripe sandbox checkout Durable Supabase record and event were written Engine restarted via Render GET /admin/stripe/payment-status/29110012 still returned known=true and financialTruthState=confirmed_paid GET /admin/stripe/payment-status still included Harper Quinn /admin/operational-attention suppressed Harper Quinn as a payment blocker Arrival readiness remained as the non-payment issue Admin /payments, /bookings/29110012, /property, and payment DAW proof routes loaded in live-dev ``` Current boundaries: ```text theme={"dark"} Durable Stripe movement truth is implemented. Durable property payment policy truth is not implemented yet. Property Payment Policy v0 is Admin-visible as a no-persistence baseline only. LIEA consumes Stripe financial truth for payment attention suppression. LIEA does not yet consume durable property payment policy truth. Signal Stream is not yet wired to LIEA. Admin-local Signal Stream scoring remains a bridge. Admin has no payment write controls. Admin has no charge/refund/mark-paid/create-checkout UI yet. Eval Labs Supabase remains separate and untouched. ``` See [Lucia Payment Truth Foundation](/lucia/system-architecture/lucia-payment-truth-foundation) for the detailed payment truth architecture, route contracts, proof set, and deferred gaps. *** ## Maintenance Intake | Input | Status | Notes | | ------------------------- | -------: | ------------------------------------ | | SMS | Working | Twilio inbound | | MMS images | Working | Auth fetch → Bunny CDN | | WhatsApp | Working | Twilio WhatsApp webhook | | WhatsApp images | Working | Auth fetch → Bunny CDN | | Email body | Working | Postmark inbound | | Email attachment metadata | Working | Metadata only | | Email image rendering | Deferred | Requires Postmark API retrieval path | *** ## Waitlist Outbound Email Current waitlist outbound email status: ```text theme={"dark"} provider: Resend sending domain: send.hellolucia.ai sender: Lucia from HelloLucia.ai reply-to: hello@hellolucia.ai runtime owner: hello-lucia/lucia-marketing function: functions/api/waitlist.js route: POST /api/waitlist status: implemented / configured / tested live ``` Current verified behavior: ```text theme={"dark"} new signup → Supabase insert → Resend welcome email sent duplicate signup → ok:true duplicate:true → no resend Resend message id returned by endpoint on send success ``` Known gap: ```text theme={"dark"} Resend message id and send status are not yet persisted back into Supabase. ``` *** ## Media Pipeline Current media pipeline:
Twilio media URLauthenticated Engine fetchBunny StorageBunny CDNAdmin UI render
Known correct CDN base: ```text theme={"dark"} https://Lucia-Maintenance-Inbox.b-cdn.net ``` *** ## Lucia Engine Model Layer Current Development truth: ```text theme={"dark"} gpt-5.6-sol default model (GPT-5.6 Sol) Lucia JSON model gateway migrated from Chat Completions to OpenAI Responses API Semantic conversational intent assist live in Focus Ops GPT-5.6 Sol response refinement sits over verified context packs with truth/routing guardrails provider-returned response.model is captured as resolved_model /admin/operator-focus exposes runtime and model provenance in meta Strict brain quality eval reached 178/178 after workspace-context awareness ``` The stable top-level `/admin/operator-focus` contract remains `ok / data / meta`. `meta.runtime` reports Engine identity, while `meta.model_runtime` reports `configured_model`, `resolved_model`, `model_invoked`, `deterministic_path`, `fallback_used`, and per-task evidence. Model invocation and no-attempt deterministic execution are complementary states; fallback is recorded independently. Successful task evidence is required before provider-backed output is claimed. Live owner verification on 2026-07-10 proved: ```text theme={"dark"} configured model: gpt-5.6-sol provider-resolved model: gpt-5.6-sol model invoked: true deterministic path: false fallback used: false verification status: Verified ``` Lucia Guest Agent also currently uses `gpt-5.6-sol`, but through its own `VV_AI_MODEL` production override and source fallback. Its independently verified provider-returned model does not extend or reuse the Engine's `meta.model_runtime` contract. Model changes must preserve: ```text theme={"dark"} response contract truth-state discipline operator calm routing correctness ``` Current live-dev product architecture: ```text theme={"dark"} Calendar = root operational reality Booking Pulse = granular intelligence lens over booking/calendar reality Signal Stream = what needs attention Lucia Workspace = reasoning partner beside the operator Focus Ops = shared reasoning and conversation Dynamic Action Workspace = action/save surface Full Booking Page = record/review surface Guest-Facing Lucia = public concierge and claim/signal bridge Guest-to-Operator Bridge = structured privacy-safe operational signal path Eval Labs = behavioral proof and regression protection ``` Current product pillar: ```text theme={"dark"} Workspace OS / context-aware operator companion Calendar-rooted operating intelligence Signal → Action → Save → Reminder loop Guest-facing public concierge with identity/linkage discipline Guest signal → Operator review/link/action loop ``` Current doctrine: ```text theme={"dark"} Calendar is Lucia's temporal spine. Lucia Workspace is the 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 is the cockpit. Full Booking Page is the record/review surface. Guest-facing Lucia is a front-of-house teammate. Operator-facing Lucia is a calm operating partner. Eval Labs is the proof/regression system. ``` This is Development/live-dev runtime truth. It is not a production-readiness claim. Current Admin runtime truth: ```text theme={"dark"} Lucia Workspace Sidebar Mode is implemented Top shell opens Workspace from the top-left icon and Open Workspace 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 Calendar is second in the main nav Calendar route is /calendar Calendar reads /admin/bookings Calendar shows monthly booking/stay-window reality Calendar supports bounded continuous scroll: 12 months back, 24 months forward Calendar booking clicks route to /bookings/:bookingId, not DAW Booking Pulse derives from the same booking source Signal Stream expands up to 20 rows with Show More Signal Stream supports move-to-top persistence and dismiss persistence Guest signals render in Admin Signal Stream Actionable guest signals are visible before collapsed rows Unlinked guest signals show honest review/link language Candidate/unlinked guest signals do not fake DAW routing Signal Stream wraps due reminders as Open Reminder cards Got it acknowledges a due reminder; it does not resolve the underlying issue Dashboard polling brings due reminders in without manual refresh Lucia Workspace / Focus with Lucia is the active conversation workspace Dynamic Action Workspace at `/ops/actions` is the default CTA surface for structured Focus Ops actions Resolver Matrix exists as a routing proof layer Admin shell topbar is sticky/stable Route changes reset scroll to top ``` Current Engine runtime truth: ```text theme={"dark"} Engine normalizes active_context.workspace safely Lucia can answer workspace-orientation and workspace-next-step prompts using current surface context Supported surfaces: Dashboard, Calendar, DAW, Full Booking, Bookings, Maintenance, Concierge, Tasks, Reconciliation Explicit prompt subject still wins over page context Engine avoids raw metadata language like active_context, current_surface, payload, and metadata Prior recommendation memory implemented Newest verified recommendation replaces older active recommendation Prior offer context implemented: yes confirms the last offered action instead of generic fallback Filler/preamble normalization implemented Next-step sequencing resolves What is next / Now what / What should I handle next through workspace and prior context Payment priority hardened: near-arrival open payment/balance outranks normal concierge extras unless verified habitability/safety/access issues outrank or tie it Saved DAW workflow awareness implemented Engine can distinguish DAW workflow saved from underlying issue unresolved Development bootstraps realistic demo fixture: 36 bookings across 18 occupied months Demo fixture has no impossible overlaps and no stale arrival_profile days Villa Valentin is modeled as one rentable inventory unit real operator reminder persistence relative reminder timing: in one minute, in X minutes, in X hours, tomorrow, next week due reminders exposed through dashboard data reminder acknowledge endpoint Engine build identity exposed on GET / Focus Ops scoped entity routing fixed: named guest/service/request overrides generic ranking Focus Ops supports active_context from Signal Stream Chat Focus Ops supports prior recommendation memory for short follow-ups Newest verified concrete recommendation replaces prior recommendation memory Strict brain quality eval reached 178/178 after workspace-context awareness Payment DAW hydrates known guest identity when available DAW saved state is sent to Lucia through active_context.workspace Engine normalizes guest signals into explicit identity/linkage contract fields Anonymous/unlinked guest signals default to public_only / review_only / no mutations Guest-claimed bookings default to candidate_booking / operator_link_required / no mutations Verified guest sessions use verified_booked_guest / verified_booking boundaries Engine accepts signed guest signals through /v1/guest/signals Candidate lookup supports conservative booking verification matching Magic-link verification token/session state is implemented Verification emails go only to the booking email already on file ``` *** ## Repositories ```text theme={"dark"} hello-lucia/lucia-admin hello-lucia/lucia-booking-engine hello-lucia/lucia-marketing hello-lucia/lucia-guest-agent ``` Branches: ```text theme={"dark"} dev stage ``` Admin Development CI: ```text theme={"dark"} npm ci npm run lint npm run build ``` Admin dev deploys after checks pass. *** ## Current Deferred Items ```text theme={"dark"} Postmark API attachment retrieval Resend message id/send status persistence to Supabase full maintenance inbox integration into Engine Focus Ops prioritization richer Calendar visible-month and booking-detail 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 onboarding/property profile/payment policy capture users/permissions billing/payment gateway/subscriptions production environment routing guest-surface production hardening v0.1.3.6 staging promotion Villa Valentin exclusive live launch mobile/tablet Workspace UX later ``` *** ## See Also * [00 - START HERE - Infrastructure](/lucia/infrastructure/start-here-infrastructure) * [11 - Domains and Live Routing](/lucia/infrastructure/domains-and-live-routing) * [04 - Lucia Workspace OS Milestone](/lucia/system-architecture/lucia-workspace-os-milestone) * [00 - START HERE - Guest-Facing Lucia](/lucia/guest-facing-lucia/start-here-guest-facing-lucia) * [01 - Maintenance Workflow](/lucia/operations/maintenance-workflow) * [07 - Postmark (Email Inbound)](/lucia/infrastructure/postmark-email-inbound) * [Email Services](/lucia/infrastructure/email-services) * [Resend Waitlist Outbound Email](/lucia/decisions/resend-waitlist-outbound-email)