Athlete summary
After a planned ride, Koyaro scores how closely you rode what was on the calendar — not how “good” the ride was physiologically. A hard race that replaced an endurance day can be a great session and a low compliance score.
What each number means
| Metric | Meaning | Formula (catalog) |
|---|---|---|
| Effort compliance | Blended match of load / intensity / duration vs plan | Planning completion blend |
| TSS ratio | Actual TSS ÷ planned TSS | actual_TSS / planned_TSS |
| IF delta | Actual IF minus planned IF | actual_IF − planned_IF |
| Duration ratio | Actual duration ÷ planned duration | actual_duration / planned_duration |
| Interval execution | Share of work-interval seconds inside the target band | Time-in-zone across work steps |
| Last-rep fade | Power drop last work rep vs first (positive = faded) | (first − last) / first × 100 |
| Surge count | Power spikes above target during work intervals | Threshold crossings |
| Plan compliance | Share of recent planned sessions completed as scheduled | Completion rate |
Planned TSS itself is a whole-ride Coggan score — see Planned session TSS/IF from workout structure.
What this is not
- Not durability / last-rep fade as a physiology test (see Fatigued Critical Power and W′ after prior work, High-intensity repeatability after work, and Resilience / durability training — race-pace under fatigue).
- The LLM must cite these catalog keys — it does not invent a compliance %.
Citations
- Allen & Coggan TSS/IF as the load terms inside the ratios.
- Execution / fade / surge counters are engine planning heuristics (
domain/planning/completion,domain/planning/execution) — documented here so chat and the UI share one article ID.