VELOARCHITECT

FTP rebuilds post-injury are not first-time builds. The Athlete has a documented True Normal from before the break; the system rebuilds against that pre-injury baseline, not against a population-average starting point. Generic post-injury plans start from zero; Veloarchitect reads the pre-injury Mechanical Efficiency, FTP, and Execution Precision from the Athlete’s longitudinal record and dispatches the Adaptive Workout to restore those specific numbers — not generic ones.

The FTP-rebuild post-injury segment is the segment most damaged by off-the-shelf plans. An Athlete returning from a 14-week knee injury has a documented True Normal that the off-the-shelf plan does not read. Veloarchitect reads it. The Athlete returns to the same FTP in 6–8 weeks that took 8 months to build, because the system knows what to rebuild toward. Protocol 9 — Knee Pain Triage — and Protocol 5 — Post-Ride Mobility — are integrated into the Adaptive Workout schedule by default, not as optional add-ons.

Protocols: Protocol 10 — Adaptive Workout; Protocol 11 — Failure Horizon; Protocol 9 — Knee Pain Triage; Protocol 5 — Post-Ride Mobility

Worked Example — 8-week rebuild after a 14-week knee injury

Athlete: 39y/o, pre-injury FTP 278W, pre-injury Mechanical Efficiency 1.58 W/bpm, 14-week injury break (left knee, ACL sprain, no surgery). Week 1: 3×30-minute Z2 at 60% FTP, daily Protocol 9 knee assessment. Week 2: 4×45 Z2, daily Protocol 5 mobility, weekly Discomfort Log review. Week 3: introduce 2×15 Threshold Sustain at 85% FTP, daily Protocol 9. Week 4: 2×20 at 88% FTP, weekly 4×8 at 105% FTP. Week 6: Z2 + 2 weekly Threshold Sustain at 90% FTP. Week 8: FTP test. Mechanical Efficiency: 1.58 → 1.56 W/bpm (pre-injury target achieved). FTP test: 271W (-7W from pre-injury, within noise). Failure Horizon projection stable at 96h.