Reference
Progress
How far each workstream has come, and the timeline of how the project got here. Percentages are working judgment calls against each track's own definition of done, not measurements.
By workstream
Web product — feature-complete except payments~85%
Payments / revenue — schema only, no checkout~15%
Mobile app — auth + read-only shell of a 17-module spec~20%
AWS migration — deployed and verified July 17; DNS cutover + parity soak remain~90%
Design refresh — comps produced, direction not chosen~25%
Concept validation — 3 test apps built, focus group not yet run~50%
Timeline
| When | Milestone |
|---|---|
| 2025 | Lumenal web app built on Lovable (React + Supabase); launched at lumenal.ai with readings across eight belief systems, shop, social, gamification and admin console. |
| Jan 2026 | Product media shot (assets/); sample Solar Return report produced. |
| Feb 3-4, 2026 | Nine-document platform review written (docs/*.md): architecture, schema, APIs, features, admin, mobile spec and mobile design strategy. |
| Feb-Jun 2026 | lumenal_expo scaffolded and built to a Phase-1 shell — full theme system, auth, readings browsing — faithfully following the design-strategy doc. |
| Jul 10, 2026 | Full multi-agent review produced docs/index.html (canonical). Strategic decisions confirmed: AWS-native migration, direct Gemini API. CDK scaffold (infra/, 6 stacks) written and synth-verified against the target account. |
| Jul 17, 2026 | This reference site created: full inventory, 3 desktop + 4 mobile design comps, and 3 complete focus-group test apps (Daily, Guide, Deck) with built-in feedback capture. |
What "done" means per track
- Web product: a user can pay — checkout, webhooks, order emails. Everything else already works.
- Payments: first real Stripe charge in production; then subscriptions per the monetization decision.
- Mobile: focus-group winner rebuilt natively in
lumenal_expothrough spec Phases 1-2 (auth, dashboard, readings, generation). - AWS migration: Phase 8 cutover — lumenal.ai served from AWS, Supabase retired, Lovable gateway gone (Phase 1's direct-Gemini swap is the early win).
- Design: chosen direction applied to landing + dashboard with a shared token package.
- Validation: focus-group feedback collected and a winner declared against the pre-committed metrics.
Reading the chart honestly
The two tracks that matter most to the business — payments and mobile — are the two least advanced. That is the argument for the current plan: validate the mobile concept cheaply while payments get built, instead of resuming the 22-week mobile spec head-down.