Nutrition intake migration map

Purpose

Use this file when removing duplicated nutrition-intake workflow instructions from global files.

Instructions that belong in nutrition-intake

Move or keep here:

• intake detection and classification
• media copy requirements
• canonical daily-log creation rules
• ## Nutrition persistence and repair rules
• heading and timestamp application
• consumed-versus-received resolution
• completion gates
• return-media workflow at the intake stage
• summary-source-of-truth rule for already logged intake
• item-level nutrition log template ownership
• summary-table rebuild rules

Instructions that belong in nutrition-analysis

Move or keep there:

• specialist-ready routing context
• detected-item list expectations
• meal-role and session-context framing
• dietary uncertainty handling
• multi-service evidence-path decisions
• handoff payload structure

Instructions that belong in nutrition-reply

Move or keep there:

• athlete-facing nutrition wording
• blocked content
• required reply structure
• macro presentation
• daily-total presentation rules

Instructions that should remain in AGENTS.md

Keep only high-level statements such as:

• use nutrition-intake for nutrition intake persistence
• use nutrition-analysis for specialist-ready analysis preparation
• use nutrition-reply for athlete-facing nutrition reply wording
• coordinator ownership, communication boundaries, and attribution rules