NUTRISYNCBuilders Hub
🏠 🛠
NUTRISYNC · Docs

NutriSync — Developer Spec → Implementation Plan & Coverage

Source: NutriSync Collective — Complete Product & Developer Specification, v1.0, 29 pages. This plan extracts the user stories and functionality, records what is already built, and marks the remaining work. As of July 2026 the app is effectively 1:1 with the Figma prototype — the full screen set is built, wired to Supabase, and running the real-time CAS. The spec remains the single source of truth; where it conflicts with earlier inferences (e.g. luteal colour), the spec wins.

Status legend: ✅ done · 🟡 partial/foundation · ⬜ to build.


0. Corrections the spec forced (applied everywhere)

1. What's already built against the spec

2. User stories by module → status

Onboarding (§3) ✅

Daily Mood & Energy gate (§4) ✅

Home / Cycle (§5) ✅

CAS (§6) ✅ engine + ✅ UI wiring

NutriLog / Meals (§7) ✅

Movement Log (§8) ✅

Edit Period (§9) ✅

Edit Health / NutriGoals (§10) ✅

Notification Center (§ live feed) ✅

Calendar (§11) ✅

Progress (§12) ✅

Settings (§13) ✅

Personalisation engine (§3.9, §7.3, §16) ✅

Longitudinal intelligence (§6.3, §6.8, §9.5) 🟡

3. Non-negotiable rules (§16) — guardrails/tests

  1. Phase determined before score; no last_period_start_date → C1 = 0 and CAS blocked. ✅
  2. Never penalise aligned symptoms (low energy menstrual, high appetite luteal, fragmented sleep/variable mood late-luteal = full marks). ✅
  3. Checklists default checked; user unchecks what she didn't do. ✅
  4. Fitness opt-out → 10/20 passive. ✅
  5. NutriGoal locked 2 cycles. ✅
  6. All data user-scoped, RLS on every table. ✅
  7. Sex-log stars (protected/unprotected), calendar-only, private. 🟡
  8. CSS ≠ CAS — daily alignment vs cross-cycle stability. (documented; CSS depth post-MVP)
  9. Daily content changes every day within a phase (indexed by cycle_day). ✅
  10. Personalisation overrides phase defaults at the data layer. ✅
  11. Cycle-length personalisation (not fixed 28). ✅
  12. After 3 cycles → personal averages. 🟡
  13. BMR internal only — never show calories. ✅
  14. NutriGoal modulates every tip/insight/food. ✅

4. Module status summary

Module Status
CAS engine + real-time recompute
Onboarding (account → Nutri → cycle date → prefs → consent)
Daily Mood & Energy gate
Home / Cycle (phase ring, live Sync Score, 🔔)
NutriLog (tips + checklist + meal log + C3)
Movement Log (checklist + C4)
Edit Period (emotes, flow, symptoms)
Edit Health / NutriGoals
Notification Center (live feed)
Calendar (month grid, predictions)
Progress (CAS summary + history)
Settings (incl. App Prefs + Nutritional Prefs)
Web app stitched to Supabase
CI/CD (mobile OTA + web Pages)
Sex-log stars / Cycle History year view 🟡
CSS donut + full CAS-history charts 🟡
Pattern recognition (2 cycles) / personal averages (3 cycles) 🟡
Full auth-record deletion (service-role Edge Function)
Consent / cookie layer
2FA / passkeys ⬜ (deferred)
Wearable connectors ⬜ (roadmap 2028)

5. Remaining work

Depth on existing screens: sex-log stars and the Cycle History year view; the CSS donut and full CAS-history charts (by-phase bars, contributors) on Progress; biomarker-snapshot depth.

Intelligence: pattern recognition after 2 cycles and the switch to personal per-phase averages after 3 cycles (user_phase_averages schema is live; the logic is pending).

Compliance: full auth-record deletion via a service-role Edge Function, and a formal consent/cookie layer. (JSON export, in-app delete, and RLS are already live.)

Deferred by design: 2FA / passkeys, and wearable connectors (native dev build, roadmap 2028).

6. Content & assets still needed from the team