Build nutrition agents at meal prep, not consumption…
Build nutrition agents at the meal preparation layer (Sunday evening meal prep) rather than the consumption layer (what to eat when hungry), because deciding what to eat while hungry and facing an open refrigerator is too late to override depletion.
When This Fires
- When designing agents for eating behavior or nutrition goals
- When willpower-based approaches to eating have failed repeatedly
- When you notice food decisions degrade in quality as the day progresses or when hungry
- When applying the upstream intervention principle to health behaviors
Common Failure Mode
Relying on willpower at the moment of consumption: "I'll just choose the salad instead of the pizza." When you're standing in front of a pizza and a salad, hungry after a long day, the pizza wins because it offers more immediate metabolic reward. The time to make the salad win was Sunday, when you prepped it, placed it at eye level in the fridge, and didn't buy pizza.
The Protocol
(1) Move nutrition decisions to the preparation layer: Sunday meal prep, grocery list construction, or weekly menu planning. (2) Make the decisions while fed and rested — never plan meals while hungry. (3) Design the consumption environment for defaults: prepared healthy meals visible and accessible, less-healthy options absent or inconvenient. (4) At the consumption layer, the "decision" should already be made: "What's for lunch? The meal I prepped." No real-time deliberation needed. (5) Track preparation compliance separately from consumption: if preparation fires at 80%+ (Define agent success as 80%+ firing rate, not subjective…), consumption usually follows automatically because the environment handles it.