VELOARCHITECT

Time trialists race against a number, not a field. The training block must produce specific power-duration outputs that match the event profile: 8 minutes for a 10-mile TT, 20 minutes for a 40K, 55 minutes for a long road TT. Generic FTP-building plans misallocate load across the wrong durations. Veloarchitect reads each Athlete’s course profile and tailors Adaptive Workout dispatch accordingly.

The time-trialist segment demands protocol-level discipline. Whoop recovery tells the system when supra-threshold work is safe; Mechanical Efficiency tells it whether the Athlete is producing more power for the same cardiac cost than last block; Failure Horizon projects when the Athlete will miss the target output. Protocol 10 — Adaptive Workout — dispatches the interval set calibrated to the event duration, not the event calendar. A 40K Athlete gets 4×10 at 105% FTP; a 10-mile Athlete gets 2×8 at 115% FTP. The system does not collapse the two.

Protocols: Protocol 10 — Adaptive Workout; Protocol 11 — Failure Horizon; Protocol 15 — Indoor→Outdoor Translation

Worked Example — 8-week block for a 40K TT at 282W FTP

Athlete: 38y/o, 282W FTP, 1.61 W/bpm Mechanical Efficiency, 142 indoor sessions in the last 100 days. Target event: 40K TT in 9 weeks, 280m of climbing, expected temperature 24°C. Block 1 (weeks 1–4): 3×40-minute Threshold Sustain at 92% FTP, weekly Z2 endurance, weekly Circadian Window-respected 4×10 VO₂max. Block 2 (weeks 5–7): 2×20 at 105% FTP, 1×40 at 100% FTP, taper compression in week 8. Mechanical Efficiency moves 1.61 → 1.68 W/bpm. FTP test on week 8: 296W (+14W). Failure Horizon projection for race day: 0.91 (clean execution expected). Race-day Execution Precision: 0.94.