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 · Readiness Ratio · Execution Precision · Mechanical Efficiency
The highest power the Athlete can sustain for ~60 minutes. Public-domain cycling definition, extended here with the Veloarchitect-tested protocol that conditions the test on Readiness Ratio and Execution Precision trend.
Definition
FTP is the public-domain cycling benchmark for sustained power output. Veloarchitect does not redefine FTP; it conditions the FTP test on the Athlete's current state and longitudinal record. A traditional 20-minute FTP test produces a noisy value when Readiness Ratio is below 0.85 or Execution Precision has declined across the last 3 rides. The Veloarchitect protocol: when state is favourable, dispatch the 20-minute test; when state is unfavourable, defer the test 5–7 days and substitute a 60-minute Z2 endurance ride. The Athlete never runs an FTP test on a degraded system, and the resulting FTP is denominated in the Athlete's own True Normal.
Protocols: Protocol 10 — Adaptive Workout; 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 has a 20-minute FTP test scheduled. Monday Readiness Ratio: 0.79 (overnight Whoop drop, knee 2/5 logged Sunday). Protocol 10 reads state as unfavourable; Adaptive Workout scheduler defers the test 6 days. Substitute session: 60-minute Z2 endurance at 68% of prior FTP. Thursday Readiness Ratio: 0.93, knee entry cleared. Friday: 20-minute test executed. Result: 282W (Athlete's prior best). A test executed on the original Monday would have produced 268W — not a true FTP, just a degraded-day value.
Common assumption inverted
FTP is not a number the Athlete hits; it is a state the Athlete reaches. A "good FTP test" requires the system state that produced it. Two Athletes with the same 282W FTP are not equivalently fit; their Peak Signatures differ, and the system never loses that distinction. The number is denominated in the Athlete's own longitudinal record, not in a population.
Related Terms
Adaptive Workout — Adaptive Workout (Protocol 10)
Mechanical Efficiency — Mechanical Efficiency
Readiness Ratio — Readiness Ratio
Full Glossary
See all eleven proprietary metrics or the platform comparison for the closed-loop claims against the field.
Related