MumPA Development Checklists

Points where the prototype is ambiguous, self-contradictory or incomplete. Each one needs a product/dev decision before the affected module is built.

• The budget screen has no entry point from Home or any navigation in the prototype: it is a complete but unreachable screen, so whether Budget ships in v1 (as a seventh widget, a nav entry or a feature-flagged route) needs a product decision.
• shop-stores is likewise unreachable and the prototype's own changelog says store tiles were removed from Shop in the v2 simplification — a decision is needed on whether saved stores stay at all.
• Shop claims 12 items while showing fewer and still references a removed basket, so the canonical item-count source and the basket's fate need a product/dev decision.
• The parent's Family screen ids are t-stars / t-reqs while the teen's are tt-rewards / tt-requests; the naming collision with the t- teen prefix will mislead anyone porting ids verbatim and needs a rename decision before build.
• The add-task flow's back button and its final Save both navigate to schedule, not todo-home, so it is ambiguous whether To Do is a child of Plan or a peer agent — its ownership and post-save destination need confirmation.
• Star awards, rewards and taste profiles exist for both Alla (teen) and Nini (kid) but the prototype never shows the parent switching which child's rewards they are viewing outside the PIN-gated menu's selector, so the parent-side child-scoping model needs a decision.
• The parent UI does not visibly expose the approval queues required for child chore claims and teen-created goals, so where those queues live (Family requests, To Do, or a new surface) is an open product decision.
• The mumpa-robot mascot is fully drawn but never rendered, and Koko is the only mascot used for children — the intended role of the robot is undefined and needs a ship-or-drop decision.
• Onboarding step 2 lets you add members inline while child-add and account-invite are the full flows; whether onboarding writes real records or a draft roster committed at the end is unspecified.
• The PIN screen's keypad has no visible "confirm" — in the prototype any tap on 0 advances — so the real entry, error, retry-limit and lockout behaviour needs defining.
• MumPA is described as monitoring chats including third-party messaging ("Kids messaged via WhatsApp"), which implies an integration and a consent/DPIA question the prototype does not resolve.
• Teen themes apply four palettes app-wide but there is no equivalent for parent or kid accounts, so it is unclear whether theming is a teen-only feature or an unfinished global one.
• Parent and teen screens disagree on the current day, dinner meal and dinner time, so one canonical family timeline must be agreed before either surface is built.
• Parent and teen reward screens disagree on Alla's reward names and pocket-money amount, so the shared reward catalogue needs final content sign-off.
• Alla appears as ages 13 and 14 while Nini's kids mode conflicts with the under-13 "via parent" wording, so the age thresholds and device-access rules need confirmation.
• Jamie is shown as both an active co-parent and a pending invite, and the four-member count includes that ambiguous state, so the member/invite state model needs deciding.
• Several controls imply destinations that do not exist in the prototype — Add recipe, child editing, Privacy & data, Family safety, Subscription, photo proof and some direct-message threads — so each needs a build-or-defer decision.
• FoodSwipe includes a "Never tried" response while the settled persistence vocabulary only defines Like and Dislike, so that third state requires a data-model decision.

Every named view in the prototype and the module that accounts for it. Reference only — helper ids are state wrappers rather than screens.

• account — module 13 (Account, Family & Settings)
• account-edit — module 13 (personal details editor)
• account-invite — module 13 (co-parent invite flow)
• bloom — module 18 (Open Bloom brand SVG symbol; non-content asset reused by the app shell in module 1 and hero cards in module 3)
• budget — module 10 (Budget)
• chat-dm — module 12 (Family Chat & MumPA Nudges — direct-message screen)
• chat-group — module 12 (group conversation and nudge cards)
• child-add — module 13 (add-child flow and per-child feature toggles)
• delete-confirm — module 5 (event delete confirmation overlay); also the source of the shared confirmation-overlay primitive in module 1
• event-detail — module 5 (Plan — Schedule & Calendar)
• family — module 11 (parent Family screen hosting the Rewards and Requests tabs)
• family-chat — module 12 (thread list, monitoring disclosure, chat API)
• foodswipe — module 8 (FoodSwipe & Family Taste)
• home — module 3 (Home Dashboard), with the shell/nav behaviour in module 1
• k-foodswipe — module 15 (Kids Experience — kid FoodSwipe)
• k-home — module 15 (kid home and child-safe navigation)
• k-req-sent — module 15 (managed-child request confirmation screen)
• k-requests — module 15 (Ask Mum preset and free-form requests)
• k-rewards — module 15 (sticker chart, rewards and chore list)
• k-task-detail — module 15 (chore-claim entry), with the claim state machine in modules 11 and 17
• k-task-pending — module 15 (pending-parent-approval state), parent side in module 11
• k-task-rejected — module 15 (rejected-claim retry state)
• k-vote — module 15 (child meal-rating experience)
• koko-koala — module 18 (kid mascot SVG symbol; non-content asset used throughout module 15)
• meals-onboard — module 8 (Family Taste Profile wizard host)
• meals-week — module 7 (full week plan)
• menu — module 7 (Menu hub)
• menu-edit — module 7 (editable meal-slot list)
• menu-share — module 7 (printable weekly menu card) and module 16 (shared export mechanics)
• mumpa — module 4 (MumPA Chat)
• mumpa-robot — non-content asset: SVG symbol defined but never referenced by any view; ship-or-drop decision itemised in module 18
• ob1 — module 8 (taste-profile step 1 pane)
• ob2 — module 8 (taste-profile step 2 pane)
• ob3 — module 8 (taste-profile step 3 pane)
• onboard-1 — module 2 (registration)
• onboard-2 — module 2 (family creation and member roster)
• onboard-3 — module 2 (Meet MumPA introduction)
• onboard-4 — module 2 (guided first action)
• onboard-done — module 2 (onboarding completion)
• recipe-adobo — module 7 (recipe detail template, instanced with sample data)
• recipe-book — module 7 (Recipe Book and recipe ingestion)
• reward-edit — module 11 (reward editor)
• reward-menu — module 11 (PIN-gated parent reward menu)
• reward-pin — module 11 (parent PIN entry and re-authentication)
• roblox-alla — module 18 (teen avatar SVG renderer, driven by the t-avatar-custom config in module 14)
• s1 — non-content helper: taste-profile step-dot 1; behaviour covered by the stepper item in module 8
• s2 — non-content helper: taste-profile step-dot 2; covered by the same stepper item
• s3 — non-content helper: taste-profile step-dot 3; covered by the same stepper item
• schedule — module 5 (Plan screen shell and tab switching)
• schedule-add — module 5 (add/edit event form)
• shop — module 9 (Shop — Shopping List)
• shop-export — module 9 (printable list) and module 16 (shared export mechanics)
• shop-stores — module 9, including the item to give it a reachable entry point or retire it
• stepNum — non-content helper: the "Step N of 3" label in the taste-profile header; covered by the stepper item in module 8
• swap-cur — non-content state target: the drawer's current-meal slot; covered under module 7
• swap-drawer — module 7 (meal-replacement bottom drawer)
• swap-manual — module 7 (drawer's manual-replacement pane)
• swap-meta — non-content state target: the drawer's day/meal-type context header; covered under module 7
• swap-suggest — module 7 (drawer's AI-suggestions pane)
• swipe-container — non-content interaction wrapper: the kid swipe stack and animation host; covered under module 15
• swipe-current — non-content state target: the active kid swipe card; covered under module 15
• t-account — module 14 (teen settings and themes)
• t-avatar-custom — module 14 (avatar customiser), with the renderer in module 18
• t-chat — module 14 (teen thread list)
• t-chat-fam — module 14 (teen family-group conversation)
• t-family — module 14 (teen Rewards and Requests tab host)
• t-home — module 14 (teen home dashboard)
• t-menu — module 14 (teen meals, ratings and FoodSwipe)
• t-mumpa — module 14 (teen MumPA chat)
• t-plan — module 14 (teen schedule and calendar integrations)
• t-reqs — module 11 (parent Family screen's Requests tab pane — note the id is parent-side despite the t- prefix)
• t-share-recipe — module 14 (teen recipe submission)
• t-shop — module 14 (teen shopping requests)
• t-stars — module 11 (parent Family screen's Rewards tab pane — parent-side despite the t- prefix)
• t-todo-home — module 14 (teen task list and Classroom sync)
• task-edit — module 11 (star-task editor)
• taste-match — module 8 (Taste Match reviews and rotation)
• tob1 — module 6 (add-task step 1 pane)
• tob2 — module 6 (add-task step 2 pane)
• tob3 — module 6 (add-task step 3 pane)
• todo-add — module 6 (three-step add-task wizard)
• todo-home — module 6 (To Do — Tasks)
• todoStepNum — non-content helper: the "Step N of 3" label in the add-task header; covered by the stepper item in module 6
• ts1 — non-content helper: add-task step-dot 1; covered by the stepper item in module 6
• ts2 — non-content helper: add-task step-dot 2; covered by the same stepper item
• ts3 — non-content helper: add-task step-dot 3; covered by the same stepper item
• tt-requests — module 14 (teen Family screen's Requests tab pane)
• tt-rewards — module 14 (teen Family screen's Rewards tab pane)
• twinkle-star — module 18 (celebration SVG symbol; non-content helper used on k-task-pending / k-task-rejected)
• view-day — module 5 (Plan day pane)
• view-month — module 5 (Plan month pane)
• view-week — module 5 (Plan week pane)