Elite coaching, powered by your biometrics.
Synchronizing biometric stream...
Calibrating structural models...
Stabilizing neural uplink...
Awaiting data packet finalization
The Architect is an independent analysis tool and is not affiliated with, sponsored by, or endorsed by Zwift, Inc. or Rouvy or Whoop. Zwift, Whoop and Rouvy are trademarks of their respective owners. Support for .zwo and .fit files is provided for data interoperability and personal performance analysis only.
© 2026 VeloArchitect. All rights reserved.
Powered by Biometrics from WHOOP
Glossary · VO₂max · FTP · Failure Horizon · ZWO→FIT Delta
The protocol Veloarchitect uses for 3–5 minute supra-threshold intervals at 106–120% FTP. The dispatch is calibrated to the Athlete's Failure Horizon projection and ZWO→FIT Delta history, not a fixed-library template.
Definition
VO₂max Repeats is the supra-threshold lever Veloarchitect owns — 4×4 (Norwegian), 30/30, and 5×5 variants all belong here. Standard library prescriptions (TrainerRoad's Sweet Spot Base, Athletica's fixed-library VO₂max) fix the interval duration, intensity, and rep count in advance. Veloarchitect dispatches VO₂max Repeats against the Athlete's Failure Horizon projection: an Athlete with a 96-hour projection receives a 4×4 at 110% FTP; an Athlete with a 48-hour projection receives a 3×3 at 108% FTP; an Athlete with a 24-hour projection does not receive VO₂max work at all that week. ZWO→FIT Delta on the final interval is the per-session dispatch read. The dispatch is logged against the Athlete's 100-day True Normal so the longitudinal VO₂max Adaptation Rate — the velocity signal protocols read across weeks — confirms the supra-threshold block is producing adaptation rather than degradation.
Protocols: Protocol 11 — Failure Horizon; Protocol 10 — Adaptive Workout
Closed Loop
The metric traverses the closed loop: Intent is the .zwo prescription the system computed against the Athlete’s True Normal. Telemetry is the .fit recording of the executed session. Adaptation is the longitudinal movement of the metric itself, logged against the True Normal and feeding back into the next day’s prescription via Protocol 10 (Adaptive Workout).
Worked Example
Athlete: 38y/o, 282W FTP, 1.61 W/bpm. Week 1 Failure Horizon: 72h. Adaptive Workout dispatches 4×4 at 110% FTP. Interval 4 average: 287W (102% FTP, drift −21W). Week 2 Failure Horizon collapses to 24h (Whoop recovery drop 18%, HRV Decoupling −6%). Adaptive Workout dispatches zero VO₂max work in week 2; Threshold Sustain at 88% FTP is the highest-intensity session dispatched. Week 3 Failure Horizon rebounds to 68h. 4×4 returns at 108% FTP. Mechanical Efficiency held flat across the 3-week window.
Common assumption inverted
VO₂max Repeats is not "the hard session." The protocol dispatches only when the Athlete's Failure Horizon projection permits it; the Athlete who treats VO₂max as a weekly staple overrides the projection. Veloarchitect's library does not produce VO₂max work on demand — the dispatch is gated. An Athlete with a Failure Horizon of 24h who takes a VO₂max session from a generic library will produce Adaptation Rate collapse within 2 weeks. The protocol respects the projection; the Athlete does not negotiate the projection.
Related Terms
Failure Horizon — Failure Horizon
Execution Precision — Execution Precision
ZWO→FIT Delta — ZWO→FIT Delta
Full Glossary
See all eleven proprietary metrics or the platform comparison for the closed-loop claims against the field.
Related