> ## Documentation Index
> Fetch the complete documentation index at: https://helloluciallc.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Domains and Live Routing
This page records Lucia’s public domains, environment routing, and current live-development operating loop.
***
## Operating Doctrine
Lucia is moving away from localhost-first development.
```text theme={"dark"}
Live internet development infrastructure → real operating loop
localhost → isolated debugging only
```
Lucia v0.1.3.6 is the current Development baseline. Engine behavior, Admin UI, CI gates, and Eval Labs production routing are aligned around the live internet workflow as of the routing correction verified on 2026-07-10.
***
## Current Version Routing
```text theme={"dark"}
Engine: engine-v0.1.3.6
Admin: admin-v0.1.3.6
Guest Agent: lucia-guest-agent
Engine branch: dev
Admin branch: dev
Guest Agent branch: main
Guest Agent source commit: 826a6a14e2fa95bfd60c8008fb0cdc9d846b4231
Guest Agent production URL: https://guest.hellolucia.ai
Guest Agent model: gpt-5.6-sol through independent VV_AI_MODEL configuration
Dev topbar: displays current Admin and Engine build identity
Payment truth live-dev proof tags: Admin 7c9683a, Engine 88a09a1
Guest Agent lab: visible build tag on public lab page
```
The Admin/Engine build identity tag is runtime proof for live-dev identity. Admin build identity is injected at Admin build time. Engine build identity is fetched live from the Engine root endpoint. Do not treat this as production readiness, and do not fake or hardcode deploy identity in Canon.
Current Development validation target:
```text theme={"dark"}
https://api-dev.hellolucia.ai/admin/operator-focus
```
Live Eval Labs environment variable:
```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 Eval Labs routing history:
```text theme={"dark"}
Uninterrupted Staging-target configuration began: 2026-05-04T16:21:35Z
Development routing correction live-verified: 2026-07-10
Current production target: https://api-dev.hellolucia.ai/admin/operator-focus
```
This proves routing configuration across the interval; it does not prove that every historical run individually used Staging. Historical run endpoint/model provenance is not reconstructed when it was not captured.
Current staging decision:
```text theme={"dark"}
Do not promote v0.1.3.6 to Staging yet.
Hold promotion until Eval Labs captures and reviews the v0.1.3.6 Development behavior baseline.
```
***
## Domain Matrix
| URL | Purpose | Environment | Visible/user-facing? | Notes |
| -------------------------------------------------- | ---------------------------------------------- | -------------------------------------------------------- | -------------------: | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `https://hellolucia.ai` | Primary Lucia public domain | Production / brand | yes | Primary marketing / waitlist public site hosted through Cloudflare Pages project `lucia-marketing`. Canon does not claim production app routing. |
| `https://www.hellolucia.ai` | WWW domain for primary Lucia public site | Production / brand | yes | Public WWW surface for the HelloLucia.ai marketing site. |
| `https://lucia-marketing.pages.dev` | Cloudflare Pages dev domain for marketing site | Cloudflare Pages | yes | Pages-provided public domain for the `lucia-marketing` project; not the primary brand URL. |
| `https://dev.hellolucia.ai` | Admin Development UI | Development | yes | Dev topbar shows live-dev identity with Admin and Engine build identities. Admin dev deploys after CI checks pass. |
| `https://api-dev.hellolucia.ai` | Engine Development API | Development | no | Current live development API. Eval Labs v0.1.3.6 target is `/admin/operator-focus`; Engine GET / exposes build identity. |
| `https://staging.hellolucia.ai` | Admin Staging UI | Staging | yes | v0.1.3.6 has not been promoted here yet. |
| `https://api-staging.hellolucia.ai` | Engine Staging API | Staging | no | Staging API exists for promoted validation; not the current Eval Labs target. |
| `https://helloluciallc.com` | Canonical HelloLucia documentation library | Documentation / Mintlify | yes | Canonical published documentation for Lucia, Lucia Fieldwork, and Eval Labs. Source: `hello-lucia/lucia-library`. |
| `https://docs.hellolucia.ai` | Legacy Lucia Obsidian Publish site | Legacy documentation | yes | Remains live but is non-canonical and does not currently redirect. Do not use it as current source truth. |
| `https://guest.hellolucia.ai` | Lucia Guest Agent production URL | Netlify production deployment / live-development product | yes | `hello-lucia/lucia-guest-agent` `main`; GPT-5.6 Sol was independently live-verified on 2026-07-12. Hosting context does not establish broader product readiness. |
| `https://lucia-guest-agent.netlify.app/lucia-lab/` | Guest-facing Lucia public concierge lab | Development / guest-facing lab | yes | Live-development lab owned by `hello-lucia/lucia-guest-agent`; not a production readiness claim. |
| `https://hellolucia.ai/newsroom` | HelloLucia.ai Newsroom | Production / brand | yes | Static newsroom surface owned by `lucia-marketing`. |
| `https://send.hellolucia.ai` | Resend outbound email sending domain | Email infrastructure | no | Verified Resend sending subdomain for waitlist and guest verification emails; not a website route. |
| `https://evaluationlabs.ai` | Live Eval Labs app | Evaluation | yes | Targets `https://api-dev.hellolucia.ai/admin/operator-focus` for v0.1.3.6 Development evals; correction live-verified 2026-07-10. |
| `https://docs.evaluationlabs.ai` | Legacy Eval Labs Obsidian Publish site | Legacy documentation | yes | Remains live but is non-canonical and does not currently redirect. Do not use it as current source truth. |
| `https://evaluationlabs.com` | Evaluation Labs domain | Brand / reserved | yes | Purpose beyond domain ownership/routing is not claimed in this Canon pass. |
***
## Current Development API Contract
Focus Ops Development endpoint:
```text theme={"dark"}
https://api-dev.hellolucia.ai/admin/operator-focus
```
This endpoint is the correct target for v0.1.3.6 Eval Labs dev-baseline validation.
Current Admin live-dev route doctrine:
```text theme={"dark"}
/workspace behavior = Lucia Workspace Sidebar Mode inside Admin Development shell
/calendar = monthly booking/stay-window spine
/admin/bookings = booking source used by Calendar and Booking Pulse
/bookings/:bookingId = Full Booking Page record/review destination
/bookings/29110012 = Harper Quinn live-dev payment truth proof route
/payments = read-only durable payment truth ledger rendering
/property = Admin-only Payment Policy Baseline v0, policy draft / no persistence
/ops/actions = default Dynamic Action Workspace for structured Focus Ops actions
/ops/actions?intent=payment_reconciliation&booking_id=29110012&focus=payment_reconciliation = Harper Quinn DAW payment reconciliation proof route
/v1/guest/signals = Engine signed guest operational signal intake
```
Current Engine payment route contracts:
```text theme={"dark"}
GET /admin/stripe/payment-status
GET /admin/stripe/payment-status/:bookingId
POST /admin/stripe/create-checkout-session
POST /webhooks/stripe
```
Payment route boundary:
```text theme={"dark"}
Admin /payments and /bookings/:bookingId render Engine payment truth read-only.
Admin never talks directly to Supabase.
Admin does not store payment truth.
Admin has no payment write controls.
The Engine create-checkout-session route exists, but Admin UI has not exposed it as an operator control.
```
Calendar booking clicks route to `/bookings/:bookingId`, not DAW. Structured Focus Ops CTAs route through `/ops/actions` when the operator needs a focused action workspace.
Lucia Workspace Sidebar Mode is Development/live-dev Admin behavior, not a production routing claim. The Workspace remains open across route changes and sends current surface context through `active_context.workspace`.
Guest Agent is deployed through Netlify's production context at `https://guest.hellolucia.ai`, while its documented product-maturity posture remains live-development and not broadly production-ready. It independently resolves `gpt-5.6-sol` through `VV_AI_MODEL`; this does not inherit from Lucia Engine configuration. Guest Agent signed signals target the Engine guest signal intake route when configured.
These routes record Development/v0.1.x truth, not production readiness.
Current payment truth routes record Development/live-dev proof only. They do not claim staging promotion, production readiness, durable policy persistence, Admin payment writes, or a full billing system.
***
## Provider Routing
Current external provider routing targets Development:
```text theme={"dark"}
Twilio SMS/MMS → api-dev
Twilio WhatsApp → api-dev
Postmark inbound email → api-dev
Resend waitlist and guest verification outbound email → send.hellolucia.ai
Guest Agent operational signals → api-dev /v1/guest/signals
```
Staging can receive signals only when provider routing is intentionally switched.
***
## Waitlist Routing
Current waitlist signup route:
```text theme={"dark"}
https://hellolucia.ai/api/waitlist
```
Current runtime owner:
```text theme={"dark"}
repo: hello-lucia/lucia-marketing
hosting: Cloudflare Pages
function: functions/api/waitlist.js
```
Current email outbound route:
```text theme={"dark"}
Resend verified sending domain: send.hellolucia.ai
From: Lucia from HelloLucia.ai
Reply-to: hello@hellolucia.ai
```
Duplicate signup behavior is intentionally no-resend.
***
## HelloLucia.ai Newsroom Workflow
Public surfaces:
```text theme={"dark"}
Primary site: https://hellolucia.ai
Newsroom route: https://hellolucia.ai/newsroom
WWW domain: https://www.hellolucia.ai
Cloudflare Pages dev domain: https://lucia-marketing.pages.dev
```
Implementation owner:
```text theme={"dark"}
Local repo: /Users/avivhadar/Desktop/lucia-marketing
GitHub repo: hello-lucia/lucia-marketing
Branch: main
Hosting/deploy surface: Cloudflare Pages
Cloudflare Pages project name: lucia-marketing
Automatic deployments: enabled
Production branch: main
Connected GitHub repo: hello-lucia/lucia-marketing
Functions directory: /functions
Wrangler config: none found
```
Deployment model:
```text theme={"dark"}
Newsroom source markdown is edited in the lucia-marketing repo.
The newsroom builder generates static files.
Generated static files are committed to hello-lucia/lucia-marketing.
Pushing main triggers Cloudflare Pages automatic deployment.
Cloudflare publishes the committed static site assets to hellolucia.ai.
```
Do not describe Cloudflare as "skipping deploy." The Cloudflare log line `No build command specified. Skipping build step.` means Cloudflare skips a custom build command, not deployment.
Current Cloudflare build truth:
```text theme={"dark"}
Cloudflare Pages auto-deploys from pushes to main.
Cloudflare build command: none specified; Cloudflare skips a custom build command.
Newsroom build location: local/Codex pre-commit in lucia-marketing.
Published output: committed static assets from lucia-marketing.
Exact configured Cloudflare output directory: not yet recorded in Canon.
```
Recent verified deployment snapshot:
```text theme={"dark"}
Commit: recorded in Cloudflare deploy logs
Message: newsroom article imagery update
Status: Success
Time: May 12, 2026 at 7:14 AM
Duration: 19s
```
Source markdown:
```text theme={"dark"}
newsroom/content/*.md
```
Generated newsroom output:
```text theme={"dark"}
newsroom/index.html
newsroom/data/posts.json
newsroom/articles/[slug]/index.html
```
Rebuild only the newsroom from the `lucia-marketing` repo root:
```bash theme={"dark"}
node tools/newsroom/build-newsroom.js
```
Article image frontmatter:
```text theme={"dark"}
image = newsroom grid/card image
articleImage = article detail page image and OG/social image
assets folder = newsroom/assets/
```
Example:
```yaml theme={"dark"}
articleImage: /newsroom/assets/article-interior.webp
image: /newsroom/assets/07-article-bg.webp
```
Local validation flow from the `lucia-marketing` repo root:
```text theme={"dark"}
1. Run the newsroom rebuild: node tools/newsroom/build-newsroom.js
2. Serve locally: python3 -m http.server 8080
3. Check http://localhost:8080/newsroom/
4. Check http://localhost:8080/newsroom/articles/[slug]/
5. Commit the generated newsroom files.
6. Push main.
7. Wait for the Cloudflare Pages deployment.
8. Hard refresh the live newsroom page.
```
If local output is correct but live is stale:
```text theme={"dark"}
1. Confirm the newsroom rebuild was run.
2. Confirm generated files changed.
3. Confirm generated files were committed.
4. Confirm push to main completed from lucia-marketing.
5. Confirm Cloudflare Pages deployment for that commit succeeded.
6. Hard refresh the live page.
7. If still stale, treat it as browser/CDN cache until proven otherwise.
```
***
## Staging Gate
Before v0.1.3.6 is promoted to Staging:
```text theme={"dark"}
Eval Labs captures Development baseline
baseline is reviewed
promotion decision is explicit
```
No Canon page should imply v0.1.3.6 is already staged.
***
## See Also
* [00 - START HERE - Infrastructure](/lucia/infrastructure/start-here-infrastructure)
* [01 - Render](/lucia/infrastructure/render)
* [02 - Cloudflare](/lucia/infrastructure/cloudflare)
* [Email Services](/lucia/infrastructure/email-services)
* [09 - OpenAI Model Layer](/lucia/infrastructure/openai-model-layer)
* [10 - GitHub and Branch Discipline](/lucia/infrastructure/github-and-branch-discipline)
* [02 - Current System State](/lucia/start-here-lucia-ai/current-system-state)