Identity, roles and organisations
activeOrganisation, practitioner, client, household and caregiver permissions.
Platform blueprint
Modular architecture for Phase 1 and Phase 2 delivery
Domain modules
Boundaries kept visible from the first build
authorganisationsusershouseholdsformscalendarrecipesmediameal-plansshopping-pantrylogsreportsbiomarkersfood-reactivityprotocolsfastingaianalytics-dashboardnotificationsaudit-security
Module activation map
Intake and forms
activeTemplates, assignments, responses, consent, baseline and check-in forms.
Google Calendar booking
activePractitioner calendars, appointment types, availability and client-linked bookings.
Recipes, media and Canva import
activeStructured recipe records with traceable source assets, photos and videos.
Meal planning and shopping
activeWeekly plans, household assignment, portion scaling, pantry flags and shopping lists.
Meal, symptom, mood and energy logging
activePerson-specific logging with creator attribution for caregiver workflows.
Tests and results hub
activeReport uploads, source typing, attachments, doctor commentary and practitioner notes.
Biomarkers and food reactivity
foundationReviewed extraction, status flags, provider extensibility and tolerance result mapping.
AI assistant layer
foundationSession prep, report summary drafts, review states and source separation.
Protocols, fasting and progress
foundationPhase-based protocols, fasting sessions, adherence and trend dashboards.
Payments and commercial expansion
reservedReserved module boundary for memberships, invoices, digital products and licensing.
Non-negotiable data rules
Every care record belongs to an organisation and person profile where applicable.
Household sharing is explicit; symptom and outcome logs remain person-specific.
Canva is treated as a source studio, while structured recipe and media data lives in the app database.
Reports keep attachments, extracted data, doctor commentary, practitioner notes and AI drafts separate.
AI never publishes directly to clients and every output carries review state.
Supabase implementation
Schema entry point
The initial migration in supabase/migrations defines stable top-level tables for identity, households, forms, calendar, recipes, meal planning, logs, reports, biomarkers, food reactivity, protocols, fasting, AI review and audit records. RLS policies can now be layered on top of those organisation-scoped relationships.
Active routes