Architecture · arrives in Phase 2
Feature Inventory
The complete feature catalogue as tables: name, purpose, inputs, outputs, dependencies and frequency of use — across dashboard, daily entries, cycle, symptoms, workouts, recovery, sleep, wearables, AI insights, recommendations, weekly trends, settings, permissions, authentication and historical views.
Scheduled for documentation Phase 2
This section's structure is reserved and its source material already exists in the shipped application. It will be populated when Phase 2 of the documentation package is delivered — see the roadmap.
What this section will contain
- —One table per domain with feature → purpose → inputs → outputs → dependencies → frequency
- —Engine features mapped to their consuming cards
- —Wearable pipeline features (Health Connect parse, sleep merge, overnight recovery, temperature import)
- —Authentication & sync features (Google OAuth, Drive appdata, localStorage fallback)
Grounded in (already shipped)
- ·lib/ engine layer: dailyFocus, fueling, whatChanged, whatNext, trends, playbook + 4 insight engines
- ·lib/wearable/: parseHealthConnect, mergeSleep, overnightRecovery, syncHealthConnect
- ·Storage keys and custom-tag CRUD per vocabulary