Supabase is Lucia’s data platform direction. Lucia Core development now uses Supabase for durable Stripe financial ledger truth, while some operational state still relies on Engine-side state files.
Current Role
Supabase is part of the Lucia stack for structured persistent data.
Current implemented Development use:
Lucia Core development durable Stripe ledger
Project name: lucia-core-dev
Project ref: jgnxomyzqotnqsmlxlsz
Current Reality
Some current runtime state is still file-backed in the Engine.
Examples include:
guest state
maintenance inbox state
stripe_financial_records
stripe_financial_events
RLS enabled on both durable ledger tables
No anon read policies
No authenticated-user read policies
Engine uses service-role-only access
Admin never talks directly to Supabase
SUPABASE_URL
SUPABASE_SERVICE_ROLE_KEY
LUCIA_STRIPE_FINANCIAL_LEDGER_STORE=dual
LUCIA_STRIPE_LEDGER_DURABLE_REQUIRED=true
Harper Quinn #29110012 completed a $500.00 Stripe sandbox checkout
Durable record/event were written
Engine restarted via Render
payment-status still returned known=true and financialTruthState=confirmed_paid
Future Direction
Supabase should eventually own more durable operational data:
bookings
guests
tasks
maintenance inbox
audit logs
operator actions
Durable Stripe movement truth = implemented
Durable property payment policy truth = not yet implemented
Property Payment Policy v0 = Admin-visible draft/read-only baseline only
Migration Principle
Do not migrate data storage blindly.
Move to Supabase when:
schema is clear
workflows are stable
audit requirements are known
UI behavior is validated
Canon Rule
Docs must distinguish:
current file-backed runtime
current durable ledger-backed runtime
future database-backed architecture
See Also
