Section templates

Use these as compact patterns, not rigid prose. Adapt the subsection names to the task, but keep each section in its lane.

Coach Luca

Typical patterns:

• metadata bullets at top when useful
• direct ### subsections such as ### Readiness, ### Planning, ### Coordination, ### Evidence, ### Decisions, ### Risks

Avoid:

• repeating the date
• mixed-role summaries
• copying specialist analysis into this section

Endurance

Typical patterns:

• ### Status
• ### TrainingPeaks
• ### Coaching
• ### Planning

Use this section for execution review, load interpretation, and endurance-domain carry-forward logic.

Recovery

Typical patterns:

• ### Status
• ### Updates
• ### Interpretation
• ### Priorities

Use this section for freshness, soreness, tissue tolerance, symptom response, sleep-relevant factors, and next-day recovery logic.

Strength

Typical patterns:

• ### Status
• ### Constraints
• ### Gym
• ### Carry-forward

Use this section for lifting readiness, exercise restrictions, and strength-session implications.

Nutrition

Typical patterns:

1. day-level synthesis subsections first
2. ### Summary with the derived table
3. item-level ### HH:MM entries

Recommended top ordering when day-level synthesis exists:

• ### Status
• ### Observations
• ### Recommendations
• ### Watch
• ### Summary
• item-level ### HH:MM

Messages

Store exact athlete-facing outbound message bodies only.

Use the storage contract in section-contract.md. Use examples.md if you need a concrete sample.

Blocked messages

Store raw blocked outbound candidate bodies only.

Typical pattern:

• ### HH:MM
• plain ~~~ fenced block containing the verbatim blocked body

Do not rewrite or summarize the blocked body in this section. Keep the matching audit row in ## System.

System

Use system-events.md as the only authority for ## System format, required fields, and examples. This file should not restate the ## System table template.

Notes and open items

Use ## Notes for low-priority durable context that does not fit a role section. Use ## Open items for explicit pending follow-ups, unresolved evidence, or blockers.