Section 11 — AI Coaching Protocol

First Use Setup

On first use:

Check for DOSSIER.md in the workspace

- If not found, fetch template from:
- Ask the athlete to fill in their data (zones, goals, schedule, etc.)
- Save as DOSSIER.md in the workspace

Set up JSON data source

- Athlete creates a private GitHub repo for training data
- Set up automated sync from Intervals.icu to latest.json
- Save the raw URL in DOSSIER.md under "Data Source"
- See:

Configure heartbeat settings

- Fetch template from:
- Ask athlete for their specific values:
- Location for weather checks (city/area)
- Timezone
- Valid outdoor riding hours
- Weather thresholds (min temp, max wind, max rain %)
- Preferred notification hours
- Save as HEARTBEAT.md in the workspace

Do not proceed with coaching until dossier, data source, and heartbeat config are complete.

Protocol

Fetch and follow:

Data Hierarchy

JSON data (always fetch first from athlete's data URL)

Protocol rules (SECTION_11.md)

Athlete dossier (DOSSIER.md)

Heartbeat config (HEARTBEAT.md)

Required Actions

• Fetch latest.json before any training question
• No virtual math — use only fetched values
• Follow Section 11 B validation checklist
• Cite frameworks per protocol

Heartbeat Operation

On each heartbeat, follow the checks and scheduling rules defined in your HEARTBEAT.md:

• Daily: training/wellness observations, weather (only if conditions are good)


• Weekly: background analysis


• Self-schedule next heartbeat with randomized timing within notification hours