HelloLucia Library

This roadmap separates durable direction, a status snapshot dated 2026-08-12, and the launch blockers on record as of 2026-09-10. It is not the live backlog, a start-date promise, or proof that every listed capability is deployed. See Current System State for the evidence ledger.

Status vocabulary

Label	Meaning on this page
Durable direction	Product doctrine or architecture direction. It is not a runtime claim.
Implemented	Owning source implements the bounded capability at the cited revision. This does not automatically prove deployment, provider execution, data freshness, production readiness, or a completed human workflow.
Active development	The named product surface or release line was active at the snapshot date. It does not mean every older roadmap bullet is in progress.
Deferred	The capability is explicitly not implemented in the accepted evidence set.
Future / release-gated	Direction that requires later authorization, implementation, and proof. It is not available behavior or scheduled work.

Durable direction

Calendar and booking truth form Lucia's temporal spine.
Lucia Workspace + Dynamic Action Workspace form the operator cockpit.
Full Booking Page is the booking record/review surface.
Guest-facing Lucia is a privacy-safe front-of-house teammate.
Eval Labs is first-class evaluation, evidence, and regression infrastructure.
Deterministic owners retain identity, property, payment, task, route, saved-state, and verified-completion truth.
Models may assist language and judgment only inside those contracts.

Launch blockers on record — 2026-09-10

These are the gates the founder or Main named on Linear between a working Development and any production use. Each is dated by its record; a Linear status is not the evidence.

Blocker	What must be true	Record
A stand-in voice, designed	Focus composes on Anthropic’s Fable with no fallback (“quiet and honest”, founder 2026-09-04). A stand-in that may later sit above that floor must earn its voice on the full Focus bank, switch by a recorded health decision, and never show the owner a provider name. The design is Planned, not built; it is the recorded launch blocker for the voice.	ALGO-41 (Planned); ALGO-40
Payment: round two is the production gate	The deposit-paid-reads-as-fully-paid seam is fixed against the booking total; the founder’s “round two” of payment work is the production gate.	ALGO-24 (founder decision 2026-09-02)
Stripe: test now, live possible, never on	One mode switch selects the key pair, webhook secret, and hosts; no code path differs between modes; the live flip is a founder decision plus a key swap on production.	LUCI-215 (founder, 2026-09-06: “Test now → flip to live.”)
lucia-world doors, round 03	The world generator’s doors on the Engine finish their third review round before any production use.	ALGO-26 (In Progress)
Calendar is unscoped	What Lucia’s Calendar is, which surfaces render it, and how it binds to truth are a founder planning conversation, then a spec, then lanes.	LUCI-99 (Planned, due 2026-09-14)

Direction the founder set in September, not a shipped fact: Anthropic’s models are to be Lucia’s predominant voice, flipped task by task behind the bank and the Fieldwork replays with GPT as the recorded fallback; the Fieldwork conversation stays on GPT (ALGO-39, 2026-09-03; ALGO-41 sequencing law, 2026-09-04). The order of work is fixed: Fieldwork and Admin speak one language, then the Algorithm proves it understands intake, then the guest agent and its model mix.

Implemented — status snapshot 2026-08-12

Capability	Status and evidence boundary
Focus Ops Engine/Admin seam	Implemented in the audited Development source and deployed identities. Engine owns the response and model contract; Admin renders it. The source default is `gpt-5.6-sol`, but no same-request provider-resolved model was captured on 2026-08-12.
Calendar, Booking Pulse, Signal Stream, Workspace, and DAW seams	Implemented in the audited Admin and Engine source. Detailed Calendar/fixture and Workspace/DAW behavior remains bounded by the 2026-05-26 and 2026-05-29 checkpoints where a fresh authenticated August interaction was not performed.
Guest Agent	Implemented as a controlled-preview product. Source was reviewed on 2026-08-12; the latest accepted same-deploy and provider proof is dated 2026-07-18 and does not establish fresh August execution or broad production readiness.
Guest identity, magic-link, controlled-reservation, and optional signal paths	Implemented as bounded controlled/test contracts. They do not prove public booking, payment, or OTA readiness, automatic human handoff, or verified operator action.
Evaluation Labs	Implemented production internal evaluation and evidence platform. Production identity was verified on 2026-08-12 without a new provider-bearing run or authenticated database recount. The Engine bank contains 217 cases; `76/217` was a non-green diagnostic, and no replacement green baseline is claimed.
Lucia Fieldwork App and API	Implemented production surfaces under active development. Accepted source was verified on 2026-08-12; no fresh authenticated UI interaction or live-data read was performed. Fieldwork delegates Lucia intelligence to Engine.
Engine maintenance webhook intake	Engine source implements `/webhooks/maintenance` and channel-specific handling. Twilio and Postmark provider-console destinations were not re-read on 2026-08-12, so current external routing and delivery are unverified.
Payment foundation	Dated Development evidence records Stripe sandbox, durable-ledger, and Admin read-only seams. The August 12 review did not reverify provider movement, authenticated datastore contents, or restart continuity. Admin `/property` remains a draft/no-persistence policy surface, not durable property-policy truth.

Active development — status snapshot 2026-08-12

Lucia Admin and Lucia Booking Engine have active dev release lines with separately verified Development identities. Their older Staging deployments are not aliases for the current Development commits.
Lucia Fieldwork App and API are production surfaces under active development; each retains its own repository, runtime, persistence, and authentication boundary.
Eval Labs is an active internal evidence platform with onboarding, role, review, hydration, and rollout hardening still in progress at the surface level.

This section does not relabel every legacy Phase 2 feature as In Progress. A feature needs its own current, attributable evidence before it can carry that state.

Deferred

The accepted August 12 evidence explicitly left these capabilities unimplemented:

durable Engine-owned property payment policy contract
Admin property payment-policy editing and persistence
policy-aware payment judgment
end-to-end property policy wiring into Signal Stream and LIEA

Since then the property’s terms and times are read from the property block as property data (ALGO-23, ALGO-34, 2026-09-03), and payment truth is judged against the booking total and those terms (ALGO-24). Owner editing of property settings remains deferred. The current payment truth is documented with the system-architecture pages of Canon Wave 3.

Future / release-gated direction

Guest production hardening: rate-limit, replay, spam, abuse, privacy, consent, operator review/link, Eval Labs, booking, payment, OTA, and property-specific provider gates.
Richer Calendar context, calendar import/onboarding, and booking-spine proof that does not depend on a synthetic fixture.
Task, priority, booking-work-queue, concierge, and vendor-dispatch refinement, each with explicit persistence and completion semantics.
Payment mutations, refunds, charge or mark-paid controls, billing, subscriptions, users, and permission systems under separately owned authorization and evidence contracts.
Multi-property inventory, property-aware memory, analytics, and mobile/tablet Workspace experiences.
Any property-specific launch only after fresh source, provider, environment, data, privacy, and operational proof. A Villa Valentin-labeled fixture is never launch evidence or live client data.

These are product directions, not start dates, active-work claims, or release commitments.

Get Started

Foundation

System Architecture

Intelligence

Intelligence Architecture

Properties

Evaluation

Guest-Facing Lucia

Project Operating Context

Operations

Infrastructure

Marketing

Roadmap

Decisions

Releases

Templates

Branding and Identity

Lucia Encyclopedia of Knowledge

Lucia Intent Layer Canon Pack

Lucia Capability Roadmap

Status vocabulary

Durable direction

Launch blockers on record — 2026-09-10

Implemented — status snapshot 2026-08-12

Active development — status snapshot 2026-08-12

Deferred

Future / release-gated direction

​Status vocabulary

​Durable direction

​Launch blockers on record — 2026-09-10

​Implemented — status snapshot 2026-08-12

​Active development — status snapshot 2026-08-12

​Deferred

​Future / release-gated direction

​Related truth surfaces

Status vocabulary

Durable direction

Launch blockers on record — 2026-09-10

Implemented — status snapshot 2026-08-12

Active development — status snapshot 2026-08-12

Deferred

Future / release-gated direction

Related truth surfaces