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:
It is not just deployment plumbing. It is part of the product.
Current Core Stack
Current Lucia Core development data addition:
Current Environment Model
Development is currently the live intake surface for external providers.
Staging is capable of handling intake but external providers do not target it unless manually switched.
Lucia v0.1.3.6 is the first clean development baseline where Engine behavior, Admin UI, CI gates, Codex project identity, and Eval Labs target routing all align around the live internet workflow.
Do not promote v0.1.3.6 to Staging until Eval Labs captures and reviews the Development behavior baseline.
Current Version Stack
Development surfaces:
Marketing / waitlist surface:
Staging surfaces:
Eval Labs v0.1.3.6 target:
Guest-facing Lucia lab:
Waitlist Email Infrastructure
Current Resend waitlist outbound status:
Service split:
Known gap:
Render Environment Names
Project:
Development environment:
Staging environment:
Payment Truth Infrastructure
Current Development status:
Durable ledger tables:
Access boundary:
See Lucia Payment Truth Foundation and 03 - Supabase.
Operating Loop
Lucia is moving away from localhost-first.
Localhost should not be treated as the default proof path for integrated behavior.
GitHub Organization
Current repositories live under:
Branch Discipline
Stage should be protected.
Direct stage pushes should be avoided.
Admin Development CI must pass before Admin dev deploy:
Infrastructure Rule
Every infrastructure claim in the Canon must specify whether it is:
No pretending.
See Also
Upstream / Downstream
Upstream
This layer is fed by:
Downstream
This layer affects:
