Methodology Series — Part 2 of 6

The Physiology of Readiness

Why "Are you fit?" is the wrong question — and how MountRoutes builds a mathematical model of your actual readiness.

🧬

The Core Principle

Most fitness apps ask “are you fit?” and let you say yes. That’s dangerous on a mountain. This page explains how our audit actually works: we ask you specific questions about your lungs, your knees, your altitude history, and your training — and turn your answers into a real measurement. Then we compare it against the exact demands of the route you’re considering.

The Danger of "Fit Enough"

If you ask a hiker, "Are you fit enough for this trek?", they will almost always say yes. Humans are notoriously bad at self-reporting their own physical capabilities. A person who runs 5 kilometers every morning might assume they are "very fit," completely unaware that their knees lack the structural integrity to carry a heavy backpack down a steep, rocky descent.

Fitness is not a single bucket you fill up at the gym. It is highly specific. Therefore, the Am I Fit audit doesn't ask if you are fit. It asks highly specific, carefully engineered questions about your physiology, your past experiences, and your current capabilities.

The Three Layers of the Audit

Every answer you provide undergoes a precise transformation through our three-layer architecture. We do not sum your answers into a generic score. Instead, we build a multi-dimensional physical profile of you across all five pillars: Aerobic, Joint & Muscle Impact, Altitude Exposure, Technical, and Resilience.

Layer 1

Feature Vector (What we know)

"I get winded climbing 4 flights of stairs." This is what you told us.

Layer 2

Capability Vector (What your body appears capable of)

The engine translates your raw data into a mathematical capacity. In this case, it estimates your Aerobic Capacity at 50%.

Layer 3

Confidence Vector (How certain we are)

How certain are we about that 50%? If you don't wear a smartwatch and we have no objective heart-rate data to verify your claim, the engine reduces its confidence in your score, downgrading your final readiness grade to protect you.

Physiological Risk Multipliers

Once your baseline is established, our algorithm applies strict mathematical penalties based on known physiological risk factors. These multipliers don't just reduce your overall score—they specifically target the biological systems they affect.

  • Smoking mathematically reduces your Aerobic capacity due to lowered VO2 max.
  • Age applies a penalty to Cumulative Fatigue, simulating the metabolic slowing of overnight recovery.
  • High BMI acts as a strict multiplier against your Structural capacity, simulating the exponential increase in joint impact during steep descents.

Interactive Demonstration — Tap to apply risk multiplier

Structural Capacity

Base Score Calculation

100pt75pt
No joint pain reported+1.0x
BMI > 30 (Obese) Risk Multiplier×0.75

Exponentially increases severe joint impact during steep 1,500m+ descents.

* Our physiological risk multipliers are research-informed, inspired by peer-reviewed sports physiology research. For example, the effect of high BMI on load-bearing biomechanics during descents is documented in PMID: 15986358, and the suppression of VO2 Max by smoking is documented in PMID: 15260039.

Advanced Cardiac Modeling

The Concordance Check & HRR Flags

For users who provide smartwatch data, we run a Concordance Check between how hard you felt the stair test was (subjective) and what your Heart Rate Reserve (HRR) shows (objective).

If your heart rate recovered perfectly, but you felt exhausted, our engine diagnoses a Muscular Deconditioning gap, not an Aerobic gap. It adjusts your advice to focus on leg strength rather than running.

We also look for Heart Rate Recovery (HRR) Clinical Flags. If your heart rate drops by less than 12 BPM in the first minute after intense exercise, the engine automatically flags a higher susceptibility to altitude sickness due to poor autonomic function, and mathematically reduces your high-altitude safety margin.

The Confidence Engine

Perhaps the most sophisticated part of the MountRoutes algorithm is that we don't just measure your capability—we measure our certainty about your capability. We call this the Confidence Vector.

If you tell us you went to 15,000ft once and felt fine, the engine will give you a solid Altitude capacity score. But, it will record that score with low confidence, because altitude sickness is notoriously fickle on single attempts.

If you tell us you've been above 15,000ft five times with zero issues, your physical altitude score remains exactly the same. However, our certainty in that score skyrockets, significantly reducing your hidden risk variables.

Scenario: 5+ successful trips above 15,000ft
95%Confidence

"I have been to 17,000ft multiple times with absolutely zero symptoms of AMS."

Demand-Capability Matching

When you compare yourself against a specific route, the engine does not perform a simple mathematical subtraction. It performs a Capacity Fulfillment calculation. It compares each demand against your corresponding capability independently.

If you have massive leg strength but poor altitude tolerance, your leg strength does not "cancel out" your altitude risk. The engine detects every individual bottleneck and categorizes them into two distinct types:

Trainable Gaps

Deficits in your Aerobic capacity, Leg Strength, or Resilience. The engine tells you exactly how many weeks of gym work or running you need to safely close the gap.

Fixed Gaps

Deficits in Altitude History or Technical Experience. No amount of gym work will save you here. The engine tells you what real-world prior experience you must acquire.

Curious what gaps you have? Run your audit

Surviving vs. Thriving

Many hikers view fitness as just a barrier to entry—training just enough to drag themselves to the summit. This is a highly dangerous mindset.

If you are operating at 100% of your maximum physical capacity on a perfectly clear day, what happens when a sudden snowstorm hits? What happens if you get slightly sick, take a wrong turn, or have to carry an injured partner's backpack? You have zero reserves left. Your safety margin is zero.

The goal of the MountRoutes engine is not to gatekeep the mountains. The goal is to ensure you have a Safety Margin. When you take the time to close the specific gaps our engine identifies, or when you use our Alternatives Engine to find a route that perfectly matches your current baseline, the experience transforms.

"You stop merely surviving the mountain, and you start enjoying it."

The mountains are unforgiving. Our algorithm ensures that when the unexpected happens, you have the reserve energy to handle it, appreciate the views, and come home safely.

Read Previous — Part 1

Mountain DNA

How we derive the 5D fingerprint of every route.

Difficulty Guide

Read Next — Part 3

The Match Engine

See exactly how your fitness vector collides with a mountain's demand.

The Match Engine

Stop guessing. Start measuring.

Take the 3-minute physiological audit and let the engine calculate your exact safety margin for any trek in the Himalayas.

Take the Audit