At a glanceLucia’s infrastructure layer supports public web access, controlled environments, real-world intake, observability, storage, authentication, and model execution.
Infrastructure Purpose
The infrastructure layer exists to make Lucia:
reachable
observable
recoverable
testable
upgradeable
safe to operate
Current Core Stack
Render → application hosting
Cloudflare → DNS / edge control
GitHub → source control
OpenAI → model execution
Twilio → SMS / MMS / WhatsApp
Postmark → email inbound
Resend → waitlist and guest verification outbound email
Bunny → media storage and CDN
Sentry → error observability
Supabase → data platform
Clerk → authentication
Netlify → Guest Agent live-development lab
Lucia Core Supabase dev project → durable Stripe financial ledger
Project: lucia-core-dev
Project ref: jgnxomyzqotnqsmlxlsz
Eval Labs Supabase → separate and untouched
Current Environment Model
Development → active live intake and dev-baseline validation
Staging → validation / pre-production behavior after promotion
Production → future
Marketing / waitlist surface → live public surface
Guest Agent lab → live-development public concierge surface
Current Version Stack
Engine: engine-v0.1.3.6
Admin: admin-v0.1.3.6
Guest Agent: lucia-guest-agent
https://dev.hellolucia.ai
https://api-dev.hellolucia.ai
https://hellolucia.ai
https://hellolucia.ai/api/waitlist
https://staging.hellolucia.ai
https://api-staging.hellolucia.ai
https://api-dev.hellolucia.ai/admin/operator-focus
https://guest.hellolucia.ai/
https://lucia-guest-agent.netlify.app/lucia-lab/
Waitlist Email Infrastructure
Current Resend waitlist outbound status:
implemented: yes
configured: yes
tested: yes
sending domain: send.hellolucia.ai
runtime owner: hello-lucia/lucia-marketing
runtime file: functions/api/waitlist.js
route: POST /api/waitlist
Postmark = inbound operational/system email intake
Resend = outbound waitlist welcome email and guest verification email
Resend message id and send status are returned by the endpoint but not yet persisted to Supabase.
Render Environment Names
Project:
Development environment:
lucia-admin-dev
lucia-booking-engine
lucia-admin-staging
lucia-engine-staging
Payment Truth Infrastructure
Current Development status:
Implemented: Stripe sandbox payment foundation in Engine dev
Implemented: durable Lucia Core Supabase Stripe ledger tables
Configured: Engine dev service-role-only access to Lucia Core Supabase
Configured: Render Engine dev durable ledger mode is dual and durable-required
Tested: Harper Quinn #29110012 payment truth survived Render Engine restart
Deferred: durable property payment policy persistence
Not yet implemented: Admin payment writes, policy persistence, charge/refund/mark-paid UI
stripe_financial_records
stripe_financial_events
RLS enabled on both durable ledger tables
No anon/auth read policies
Engine uses service-role-only access
Admin never talks directly to Supabase
Admin renders Engine payment truth only
Operating Loop
Lucia is moving away from localhost-first.
Live internet development infrastructure → real operating loop
localhost → isolated debugging only
GitHub Organization
Current repositories live under:
hello-lucia/lucia-admin
hello-lucia/lucia-booking-engine
Branch Discipline
dev → active development
stage → promoted validation branch
npm ci
npm run lint
npm run build
Infrastructure Rule
Every infrastructure claim in the Canon must specify whether it is:
implemented
configured
tested
deferred
future
See Also
Upstream / Downstream
Upstream
This layer is fed by:
Downstream
This layer affects:
