Milestones are sequenced product slices. Each slice gets its own implementation plan in this folder before work starts. “Specified” means the UX documents describe the behavior; it does not mean the behavior exists.
| Milestone | Slice | Status | Plan |
|---|---|---|---|
| M0 | Local scaffold and product specification | Done | — |
| M1 | Adult-only logging | Tasks 1–8 implemented (Task 7 review done 2026-09-19 with the playful adult-facing UI, shared diary entry cards, bottom navigation; Task 8 privacy-safe audit/telemetry done with local in-process sinks only); Task 9 e2e Maestro flows and demo runbook written (not executed here, Maestro unavailable); device/simulator validation of native camera, SQLCipher, and SecureStore still pending | 2026-09-19 M1 adult logging |
| M2 | Planning (personal meal plan) | API implemented 2026-09-20 as a generated weekly meal plan (ADR-0010): preferences (allergens, dislikes, focus, pattern, servings, location, units, time zone), Monday-to-Sunday generation through the mock seam, editable items with ingredients and nutrition, plan-to-diary confirmation, mutual read-only shared planning, synchronized shopping list with ticks, Sunday-morning auto-generation in the worker; mobile screens pending Mobile Plan tab implemented 2026-09-20 (week view, editor, I-ate-this confirmation); device validation pending. | 2026-09-20 M2 planning and M3 foundations |
| M3 | Household, subscription, export/deletion, alerts | API foundations implemented 2026-09-20 with mocks only (two-adult invitations and sharing settings, mock billing with photo-analysis allowance, per-adult export and verified deletion, planned-meal/water reminders and problem notices); mobile screens pending Mobile Me tab implemented 2026-09-20 (household, subscription, reminders, your data, privacy, preferences, about). | 2026-09-20 M2 planning and M3 foundations |
| M4+ | Remaining approved scope, not yet sequenced | Real provider adapters (identity, photo analysis, nutrition data, billing, notifications); production deployment and operations | — |
M2 covers the Planning flows in user flows and the UX inventory, redirected on 2026-09-20 to a generated weekly plan: the week runs Monday to Sunday, is produced from stored preferences (allergens as hard exclusions, dislikes, focus, dietary pattern, servings, location, units) through the meal-plan provider seam, stays fully editable, is regenerated every Sunday morning for adults who keep auto-generation on, and drives a shopping list ordered by the first day each ingredient is needed with tickable lines. Plans are organizational suggestions, never prescriptions; there are no numeric goals; and a plan item never becomes a diary fact without adult confirmation (ADR-0010).
Alerts decision (product, 2026-09-20): alerts mean (a) reminders for planned meals and water
and (b) notices about saving or photo-estimate problems. There are no threshold or goal
warnings (“over your target”); they conflict with the calm, non-judgmental
content guidance. Delivery goes through the NotificationProvider
seam with the mock adapter only (in-app list plus mock receipts); a real push adapter is M4+.
Goals decision (product, 2026-09-20, evening): explicit goals with computed daily calorie and protein targets and under/on-track/over progress are in (ADR-0011). Progress is shown as neutral information in the diary and plan; alerts still send no goal warnings.