N NOURISH / LAB Back to plan

PLANNED WORK · NOT YET LIVE

Development roadmap

The larger ideas have a permanent home now. Open any project to see what it would take to build, what data it depends on, and what the finished flow could look like.

PROJECT PIPELINE 6 larger developments recorded
SHIPPED IN THE CURRENT BUILD
01
Weekly planner + seven-day nutrient averagingBuild distinct days while letting liver, oysters, recipes, and other occasional foods contribute across the full week.
LARGER BUILD+
Daily macro targets→7-day constraint solver→Days + shopping list

Realistic implementation

  • Keep calories and macros within a chosen range each day while optimizing selected nutrients over seven days.
  • Add frequency rules such as liver once or twice weekly, minimum meal-sized proteins, leftovers, and foods to avoid repeating.
  • Show both each day and the weekly average so a strong weekly result never hides a poor individual day.

Dependency: a more formal constraint solver and saved multi-day state. Feasible with the existing food database.

02
Restaurant, fast-food, and cheat-meal entryAdd what was actually eaten without turning the curated food matrix into a fast-food catalogue.
MEDIUM BUILD+
Search or manual meal→Reserve consumed macros→Re-solve remaining day

Realistic implementation

  • Use a separate “meal already eaten” drawer with manual macros first, plus company-published nutrition when a source is available.
  • Subtract the meal from the day, then re-optimize the remaining curated foods for macros and nutrient gaps.
  • Label unavailable micronutrients as unreported instead of zero and keep these meals out of the food matrix.

Dependency: reliable first-party restaurant data or a licensed database; manual entry can ship earlier.

03
Product-specific nutrition + lab-tested profilesRepresent the exact goat milk, eggs, coconut water, meat source, or branded product you actually buy.
LARGER BUILD+
USDA baseline+Label or lab override→Personal product profile

Realistic implementation

  • Keep generic USDA values as the baseline, then override only nutrients explicitly measured on a label or laboratory report.
  • Attach a source, test date, preparation state, animal/feed claim, and confidence note to every override.
  • Never convert an absent label micronutrient into zero; the untouched USDA or unreported state remains visible.

Dependency: a profile editor, source attachments, and nutrient-by-nutrient provenance.

04
Automated Canadian store pricingTrack current Superstore, Costco, farmer’s-market, butcher, and other local prices with history.
DATA DEPENDENT+
Store + location→Matched package→Price history + day cost

Realistic implementation

  • Build on the current manual CAD offers and add postal-code/store-location awareness.
  • Match package sizes to foods, preserve sale dates and unit prices, and flag stale records rather than silently trusting them.
  • Import from permitted feeds, receipts, or user-entered records; avoid brittle scraping where a store blocks or changes access.

Dependency: store data access and product matching. The manual editor remains the reliable fallback.

05
Recipe builderTurn homemade marshmallows, gelatin desserts, meals, and batch-cooked foods into reusable plan items.
MEDIUM BUILD+
Ingredients→Cooked yield→Serving nutrient profile

Realistic implementation

  • Add ingredients by weight, record final batch yield, and choose a serving size or number of pieces.
  • Calculate macros, nutrient totals, and cost from the underlying sourced foods.
  • Let recipes participate in daily and weekly solvers without duplicating their ingredients in the plan display.

Dependency: recipe storage and yield handling. Feasible with the current food and pricing models.

06
Custom bioenergetic ratio profilesKeep Ray Peat, Georgi Dinkov, community interpretations, and personal working targets distinct and traceable.
RESEARCH + BUILD+
Named source profile→Personal target bands→Food + cofactor actions

Realistic implementation

  • Store the exact source and quote context behind every numeric band; keep directional claims visually separate.
  • Allow personal working ranges without presenting them as clinical requirements or attributing them to someone who did not publish them.
  • Connect out-of-range cards to the foods, data gaps, and logged supplements driving each side of the relationship.

Dependency: source-by-source research and a target-profile editor. The current ratio cards are the foundation.