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 · Cadence · Torque · Power · Lactate Clearance
The protocol that calibrates pedal cadence against applied load to target a specific training system. The Athlete’s target system (aerobic, neuromuscular, or muscular endurance) determines the cadence × resistance combination Veloarchitect dispatches.
Definition
Cadence × Resistance is the protocol that owns the cadence-and-load calibration. The Athlete does not have a "natural cadence"; the Athlete has a target training system, and cadence × resistance is the lever set that hits it. Veloarchitect dispatches 85–95 rpm at low resistance for aerobic development, 70–80 rpm at high resistance for muscular endurance, and 95–110 rpm at moderate-to-high resistance for neuromuscular priming. The athlete who treats cadence as a fixed personal preference is missing the protocol's system-targeting logic: an Athlete whose lactate clearance is weak benefits from 80 rpm over-unders; the same Athlete's neuromuscular priming is best at 100+ rpm. The protocol reads the Athlete's longitudinal record and dispatches the cadence × resistance combination the body needs.
Protocols: Protocol 3 — Threshold Sustain; Protocol 2 — VO₂max Repeats
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: 32y/o, 286W FTP, weak lactate clearance (over-under Execution Precision 0.62 at week 0). Cadence × Resistance dispatcher reads: 80 rpm × high torque for the 30s on-phase (105% FTP), 95 rpm × moderate torque for the 30s off-phase (95% FTP). Standard cadence prescription is 90–95 rpm throughout; Veloarchitect dispatches the contrasting cadence to push lactate clearance specifically. Week 4 over-under Execution Precision: 0.89. Mechanical Efficiency holds at 1.62 W/bpm. Lactate clearance (measured by 30-minute recovery HR drop) improved 14%.
Common assumption inverted
Cadence × Resistance is not "ride at your preferred cadence" and not "always 90 rpm." The protocol's system-targeting logic contradicts both pieces of conventional advice. The Athlete who treats cadence as a personal preference loses the protocol's specificity: their work hits one training system when the body needs another. Veloarchitect reads the Athlete's longitudinal record (Execution Precision, lactate clearance, Mechanical Efficiency trend) and dispatches the cadence × resistance combination the system needs. The protocol does not negotiate preference against system target; the system target wins.
Related Terms
Threshold Sustain (Protocol 3) — Threshold Sustain
VO₂max Repeats (Protocol 2) — VO₂max Repeats
Execution Precision — Execution Precision
Full Glossary
See all eleven proprietary metrics or the platform comparison for the closed-loop claims against the field.