Current State
An honest snapshot of every part of the workspace as of July 17, 2026. Short version: the web app is feature-complete except payments but lives on Lovable's stack; the mobile app is a polished read-only shell whose code is not even committed; the AWS exit ramp is scaffolded but not deployed.
Workspace map
| Directory | What it is | State |
|---|---|---|
lumenal-0a809f58/ | Production web app — React 18 + Vite + shadcn/Tailwind + Supabase (60 migrations, 19 Deno edge functions). Live at lumenal.ai. | Live |
lumenal_expo/ | Active mobile app — Expo SDK 54, expo-router, React 19, same Supabase backend. | Phase-1 shell |
lumenal_mobile/ | Empty legacy repo (bare git init, zero commits). Old docs still point here. | Retire |
infra/ | AWS CDK TypeScript scaffold — 6 stacks encoding migration Phase 0. | Synth-verified, not deployed |
docs/ | 9 markdown docs (Feb 2026, partially stale) + index.html (Jul 10, canonical). | Canonical doc fresh |
assets/ | Raw product photos and videos (Jan 2026), no code. | Reference |
references/ | This site — project reference, comps, and focus-group apps hub. | New |
Web app
Lovable-authored and feature-rich: 44 routes (13 admin), 42 Postgres tables with 127 row-level-security policies, and 19 edge functions of which 13 call AI. All AI traffic routes through Lovable's gateway to Google Gemini models — the project's number-one lock-in. The full user-facing catalog is on the Feature Inventory page.
Payments do not exist. Product, cart and order schema are complete, price tiers are defined ($39.99 / $69.99 / $99.99 curated boxes), but there is no checkout — the platform cannot take money. Dev credentials are committed in docs/README.md and flagged in the security review; rotation is a standing P0.
Mobile app (lumenal_expo)
A faithful implementation of the design strategy doc — full light/dark token system, Inter + Cormorant Garamond, hand-rolled shadcn-style UI kit — with working Supabase email/password auth and a real reading-detail view. But most interactive surfaces are stubs:
| Screen | Status | Notes |
|---|---|---|
| Welcome, Login, Signup | Working | Real Supabase auth; forgot-password link is a no-op |
| Dashboard | Partial | Profile fetch works; 3 of 4 quick-action cards do nothing |
| Readings list + detail | Read-only | Browsing works; "Generate Reading" has no handler |
| Calendar / moon phases | Mock | Hardcoded sessions and phases, no backend |
| Shop | Read-only | Catalog browsing only; cart badge hardcoded to 0 |
| Profile | Partial | Sign-out and cache-clear work; ~13 menu items are no-ops |
| Natal chart, reports, messaging, connections, achievements | Absent | Specified in docs, not started |
The entire real app — app/, src/, config — sits untracked on branch feature/env-config; the repo has a single "Initial commit". One disk failure loses the mobile app. Committing this is a five-minute task on the Open Tasks list.
Stack divergence worth knowing: the Feb specs prescribed React Query + Zustand + Tamagui/NativeWind + offline SQLite; the shipped app uses plain React Context + StyleSheet and none of the offline layer. The spec should be rewritten around the focus-group winner rather than retrofitted.
Infrastructure (AWS migration)
The migration described below as "not deployed" has since shipped in a new repo, nnolasco/lumenal-aws, live at d2ted2wy8rjgfj.cloudfront.net: Aurora Serverless v2 MySQL (Data API) with all 41 tables + data imported, the 127 RLS policies re-implemented as a server-side policy engine, all 19 functions ported to Lambda on the direct Gemini API, Cognito with lazy password migration from Supabase, and app + 290 media assets on S3 behind CloudFront. The original infra/ CDK scaffold (Aurora Postgres) is superseded. Remaining: lumenal.ai DNS cutover and a parity soak before retiring Supabase.
Six CDK stacks — Network (VPC), Database (Aurora Serverless v2 Postgres 16), Auth (Cognito + groups), Storage (S3 + CloudFront), Api (HTTP API + Cognito authorizer + Gemini secret), WebHosting (SPA hosting) — synthesized against account 052561863525 / us-east-1 on July 10, but nothing is deployed. No Lambda ports of the 19 edge functions exist yet (deliberately deferred to Phase 4). Standing cost once deployed: roughly $75-165/month, dominated by the Aurora floor.
The two acknowledged hard problems: re-plumbing 127 RLS policies that assume auth.uid() (plan: SET LOCAL app.user_id GUC + Cognito trigger), and replacing supabase-js's auto-generated API with a thin domain REST API.
Documentation
docs/index.html (July 10) is the canonical architecture and migration document — sections for overview, architecture, frontend, backend, mobile, local dev, AWS plan, open tasks, improvements, security, marketing, roadmap. The nine February markdown files predate the AWS decision; MOBILE_APP_NOTES.md is the most stale (it still points at the empty lumenal_mobile repo). Treat the markdowns as historical context only.