Running is TrailGenic’s cardiovascular control layer. Walking establishes the low-cost baseline; Rucking changes carried weight on the same course; Running changes speed, run–walk structure, and intensity. Hiking is where those controlled capacities are tested against terrain, altitude, weather, and longer duration.
The record contains three distinct phases: Sessions 1–5 established the shorter base; Sessions 6–14 developed approximately 3.2-mile steady run–walk continuity; Sessions 15–17 were explicitly declared maximum-speed intervals with walking recovery. Sessions 18–21 remain mixed run–walk observations and are not silently relabeled as part of the declared maximum-speed block.
Garmin-estimated running VO₂ max progresses from 45 in S1–15 to 46 in S16–18 and 48 in S19–21: +6.7% from the opening value and +4.3% from 46. The 48 first appears September 10 and remains recorded through September 23. This upward aerobic-fitness signal is central to the longevity interpretation.
| Running window | Recorded dates | Garmin VO₂ max |
|---|---|---|
| S1–15 | Mar 17–Aug 5 | 45 |
| S16–18 | Aug 19–Sep 3 | 46 |
| S19–21 | Sep 10–23 | 48 |
Cardiorespiratory fitness is strongly associated with long-term survival in human cohort research. This makes the direction of the VO₂-max series an important longevity-relevant outcome, assessed alongside hiking workload and cardiovascular response. It is a fitness estimate, not a calculation of years of life gained.
Use the Running series explicitly: the Hiking VO2Max_Garmin field remains 46 throughout, and the workbook does not timestamp each Garmin recalculation. These are device estimates in mL/kg/min; the source fields are preserved separately.
Protocol progression is retained: S1–5 average 2.42 miles, S6–14 approximately 3.16 miles; S15–17 are maximal intervals and S18–21 mixed run–walk. Raw pace and whole-session HR are interpreted within these protocols. Cardiorespiratory fitness and mortality — primary study.
Running is not the environmental experiment. Its value comes from repeating the same flat route while run share, interval design, pace, power, cadence, heart rate, training effect, stamina, and recovery change over time.
The interval block recorded lower average heart rate alongside a larger walking-recovery share, while wearable-estimated anaerobic effect and exercise load were higher. This is why average HR cannot be interpreted without protocol structure.
Running contributes the cardiovascular-intensity layer: can a controlled course accept a harder protocol without confusing whole-session averages with adaptation?
Historical window: S15–19 raised maximum HR and device-estimated anaerobic effect versus S6–14. S17–20 had four consecutive not-ready flags; S21 returns to a ready flag. These contextual labels are not independently timed recovery measurements. S15–17 remain the declared maximal-interval block, distinct from mixed S18–21.
That is a protocol-phase boundary, not evidence that later running was “worse.” It shows why intensity tolerance must include recovery cost and return capacity. TrailGenic compares like with like and does not use weather as a causal explanation on this controlled course.
This N=1 record does not prove longevity benefit. It contributes a structured benchmark for learning when cardiovascular intensity expands capacity and when the next useful action is consolidation rather than escalation.
| # | Date | Distance | Run / Walk | Avg / Max HR | Drift | Load | Protocol |
|---|---|---|---|---|---|---|---|
| 10 | Jun 3 | 3.16 mi | 35:24 / 4:55 | 148 / 163 | −1.5% | 51 | Steady run–walk |
| 11 | Jun 10 | 3.17 mi | 36:12 / 3:49 | 152 / 162 | +1.0% | 53 | Steady run–walk |
| 12 | Jun 17 | 3.16 mi | 37:23 / 0:07 | 155 / 170 | +3.2% | 65 | Continuity benchmark |
| 13 | Jul 15 | 3.16 mi | 39:11 / 2:59 | 157 / 167 | +4.0% | 51 | Steady run–walk |
| 14 | Jul 20 | 3.17 mi | 33:08 / 3:50 | 154 / 167 | −3.0% | 77 | Steady benchmark |
| 15 | Aug 5 | 3.19 mi | 19:13 / 21:43 | 144 / 175 | +2.0% | 75 | Declared max-speed intervals |
| 16 | Aug 19 | 3.18 mi | 15:29 / 24:38 | 150 / 172 | −1.5% | 104 | Declared max-speed intervals |
| 17 | Aug 26 | 3.15 mi | 15:01 / 25:18 | 145 / 171 | −2.5% | 96 | Declared max-speed · not ready |
| 18 | Sep 3 | 3.17 mi | 22:26 / 15:08 | 148 / 180 | +4.5% | 87 | Mixed run–walk · not ready |
| 19 | Sep 10 | 3.15 mi | 17:55 / 22:34 | 146 / 174 | +5.0% | 66 | Mixed run–walk · not ready |
| 20 | Sep 17 | 3.23 mi | 17:01 / 22:13 | 148 / 178 | −2.0% | 79 | Mixed run–walk · not-ready flag |
| 21 | Sep 23 | 3.19 mi | 19:36 / 18:29 | 146 / 168 | +4.5% | 67 | Mixed run–walk · ready flag |
Average power, cadence, heart rate, pace, and drift are whole-session measures and include walking recovery.
S21 covered 3.19 miles in 38.2 minutes, or 11:58 per mile. Versus S20, time per mile fell 1.6%, average HR fell 148 → 146 bpm, max HR 178 → 168, device load 79 → 67, and anaerobic Training Effect 0.9 → 0.0. Effort stayed 3/5 and aerobic effect was 3.0.
Running share increased from 43.4% to 51.5%, calculated from the recorded run and walk durations. Whole-session pace, HR, power, and cadence still include walking. Corrected drift rose from −2.0% to +4.5%, so the response is mixed rather than uniformly improved.
Interpretation: S21 is a favorable return within the mixed run–walk phase, with a ready flag after four not-ready flags. Sleep context is score 80 and 399 minutes. One session cannot establish improved running economy or completed recovery; the next step is replication of this declared dose with timed follow-up.
Context: route, entering sleep, symptoms, prior training, and fasted state. Dose: declare run–walk structure, interval count, work duration, recovery duration, and target intensity where recorded. Missing interval details must not be reconstructed from whole-session averages.
Response: retain work and recovery splits when available, alongside whole-session HR, pace, and device estimates. Follow-up: link recovery observations and the next comparable protocol. The existing ready/not-ready flags are contextual classifications, not independent physiological clearance.
Adaptation question: does the response change when the same interval dose is repeated? Compare within declared phases before comparing across phases. The current record does not establish a cardiovascular threshold or isolate the effect of intensity.
Original asset: protocol-labeled sessions, longitudinal comparisons, and an explicit consolidation rule. Reviewed September 24, 2026 by Mike Ye and Ella; release 2026-09-24.2. Current selected data are embedded as JSON.
Recovery windows · Measurement limits · Baseline protocol
Source: September 24 master workbook. Mike Ye, field record; Ella, interpretation. The unexplained numeric 48 in the S20 and S21 HR Drift Audit row is excluded from physiology and drift calculations. Corrected drift comes from its named source row. Timed post-session recovery is not supplied.
For Mike’s next comparison, retain the declared running structure and assess the rolling VO₂-max direction, comparable pace/HR response, effort, and follow-up. The accumulated 45 → 46 → 48 series supports aerobic adaptation; the latest run updates that trajectory rather than carrying the conclusion alone.
Walking is the baseline control. Rucking applies progressive carried load to the same course. Running applies cardiovascular intensity. Hiking then tests transfer under terrain, altitude, weather, duration, mechanics, and judgment.