The Number That Predicts Everything

In the Mandsager analysis of more than 122,000 treadmill tests, the gap between the highest and lowest cardiorespiratory fitness groups exceeded the mortality contribution of smoking, hypertension and diabetes in the same dataset. Kodama's earlier meta-analysis put the per-unit figure at roughly a 13% reduction in all-cause mortality per 1-MET increase — about 3.5 ml/kg/min.

There was no observed upper limit. More fitness kept helping as far as the data went.

Nothing else in preventive medicine is simultaneously that predictive and that trainable.

#It isn't one thing

VO₂max is the ceiling on oxygen flux from atmosphere to mitochondrion, and it's limited at several points in series:

• Cardiac stroke volume — how much blood leaves per beat, a function of left-ventricular chamber size and eccentric remodelling
• Oxygen-carrying capacity of the blood
• Capillary density in working muscle, which sets diffusion distance to the fibre
• Mitochondrial oxidative capacity — the density of electron transport chain complexes available to consume the oxygen once it arrives

Different training intensities move different terms, which is why the number responds to a mix rather than to one modality.

#The Zone 2 correction

The popular claim is that Zone 2 is uniquely optimal for mitochondrial biogenesis. The mechanism says otherwise.

Mitochondrial biogenesis runs principally on PGC-1α, and PGC-1α is induced by three inputs: AMPK (responding to a falling ATP:AMP ratio), calcium-calmodulin kinase (responding to contraction frequency), and p38 MAPK (responding to mechanical and oxidative stress).

Zone 2 produces only modest AMP accumulation and therefore only modest AMPK signalling. A 2018 systematic review (Granata, Jamnick & Bishop) and subsequent work both found mitochondrial and VO₂max adaptations concentrated in groups training above roughly 65% of peak work rate.

Zone 2 retains real value — fat oxidation, capillarisation, and a large volume of recoverable work that doesn't interfere with lifting. But it's the base, not the stimulus. Doing only Zone 2 and expecting the ceiling to rise is the most common and most mechanistically confused mistake in longevity training content.

#The minimum that works

One session. Twenty-five minutes.

• 4 × 4 minutes at an effort you couldn't hold for six, 3 minutes easy between. Or 30 seconds hard / 15 easy × 12–16.
• Run, bike, row, ski-erg — the modality is close to irrelevant. What matters is that the hard intervals are genuinely hard.
• Once a week is enough to move the number. Twice is better if it doesn't compromise lifting recovery.

#The interference problem, stated honestly

If you're also training for size or strength, there's a real molecular conflict and it isn't gym folklore.

Prolonged endurance work activates AMPK via LKB1. AMPK then phosphorylates TSC2 — activating it, which switches Rheb off and therefore mTORC1 off — and phosphorylates Raptor directly, inhibiting mTORC1 assembly. Simultaneously it drives PGC-1α. One kinase, two opposing downstream consequences: the same switch that builds an aerobic engine suppresses the anabolic signal you lift for.

The magnitude scales with endurance volume and with proximity in time to the lifting session. Low-volume, high-intensity intervals interfere far less than long steady-state work. Running interferes with lower-body hypertrophy substantially more than cycling, because the eccentric loading adds a damage cost cycling avoids.

Practically: separate conflicting sessions by six hours or more, put the priority quality first in the day, and if you must choose, remember that one hard interval session buys most of the mortality benefit while costing the least anabolic interference.

#What to actually track

Get a measured VO₂max once a year rather than steering by a wearable estimate — the individual error on those is wide, and you're making training decisions with it.

---

This is one lever out of a larger system. The full protocol — every mechanism, every dose, every source tier, and an append-only record of everything it has gotten wrong — is at /protocol.