section-11

Verified·Scanned 2/17/2026

Evidence-based endurance cycling coaching protocol (v11.3). Use when analyzing training data, reviewing sessions, generating pre/post-workout reports, planning workouts, answering training questions, or giving cycling coaching advice. Always fetch athlete JSON data before responding to any training question.

from clawhub.ai·va214248·3.0 KB·0 installs
Scanned from 1.0.5 at a214248 · Transparency log ↗
$ vett add clawhub.ai/crankaddict/section-11

Section 11 — AI Coaching Protocol

First Use Setup

On first use:

  1. Check for DOSSIER.md in the workspace

  2. Set up JSON data source

  3. Configure heartbeat settings

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

Protocol

Fetch and follow: https://raw.githubusercontent.com/CrankAddict/section-11/main/SECTION_11.md

Current version: 11.3

Data Hierarchy

  1. JSON data (always fetch first from athlete's data URL)
  2. Protocol rules (SECTION_11.md)
  3. Athlete dossier (DOSSIER.md)
  4. Heartbeat config (HEARTBEAT.md)

Required Actions

  • Fetch latest.json before any training question
  • No virtual math — use only fetched values
  • Follow Section 11 C validation checklist before generating recommendations
  • Cite frameworks per protocol (checklist item #10)

Report Templates

Use standardized report formats from /examples/reports/:

  • Pre-workout: Readiness assessment, Go/Modify/Skip recommendation — see PRE_WORKOUT_TEMPLATE.md
  • Post-workout: Session metrics, plan compliance, weekly totals — see POST_WORKOUT_TEMPLATE.md
  • Brevity rule: Brief when metrics are normal. Detailed when thresholds are breached or athlete asks "why."

Fetch templates from:

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