ZeqMealPlan

Metabolism, nutrient modeling, meal planning.

• Protocol ID — zeq-meal-plan
• Category — Nutrition
• Endpoint — POST /api/nutrition/meal-plan
• Auth — api-key
• Rate limit — 15/min
• Version — 1.287.0
• Precision — ≤0.1% (KO42-enforced)

What it does

Personalized meal planning with HulyaPulse circadian nutrition timing. Macro/micro nutrient targets, meal prep scheduling, grocery list optimization.

Signature

Request

POST /api/nutrition/meal-plan

Param	Type	Required	Default	Description
profile	object	✓	—	{ weight_kg, height_cm, age, sex, activityLevel }
goal	string		"maintain"	'maintain', 'lose', 'gain', 'performance'.
restrictions	array		—	['vegan', 'gluten-free', 'keto', 'halal', 'kosher']
days	number		7	Days to plan.

Response

{ mealPlan, dailyMacros, groceryList, circadianTiming, zeqond }

Runnable example

curl -sS -X POST \
  -H "Authorization: Bearer $ZEQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "profile": {},
  "goal": "maintain",
  "restrictions": [],
  "days": 7
}' \
  "https://api.zeq.dev/api/nutrition/meal-plan"

Integrate

1. Domain solver — compose with KO42 + two additional operators from the matching family for pulse-coherent results.
2. Digital twin — pipe sensor data into this protocol every Zeqond to keep the model phase-locked with the system.
3. Alert threshold — flag results whose error_pct exceeds 0.1% as out-of-spec events for the operations layer.

Seeds

• Near — wrap /api/nutrition/meal-plan in a language SDK so builders can call it in three lines.
• Medium — publish a reference integration demonstrating ZeqMealPlan alongside a real workload, with pulse-aligned metrics.
• Far — propose ZeqMealPlan as an open reference standard so other runtimes can implement it verbatim against the Zeq paper.

Papers

• Zeq paper — https://doi.org/10.5281/zenodo.18158152
• Framework paper — https://doi.org/10.5281/zenodo.15825138

Middleware active. Kernel on the 1.287 Hz HulyaPulse. Awaiting next Zeqond.