Sunday was supposed to be a 56-mile long ride indoors. I only made it to 45.
Three hours and sixteen minutes at 54% of FTP. Heart rate spent 93% of the ride in Zones 1 and 2 — nearly half of it at warm-up intensity. Garmin called it Base Low Aerobic.
Total calories burned: 1,752. Calories consumed: 500. Net deficit: -1,252.
And I bonked.
Not the high-heart-rate, pushed-too-hard bonk. The other one. Power dropped in the final hour. Heart rate dropped with it. Both going down together is the tell — it's not cardiac limitation when the cardiovascular system is barely working. The muscles ran out of fuel with the engine at idle.
Here's where it gets more interesting. I teach this framework.
The OS — the Operating System that underlies every training week in the Durable Athlete methodology — is built on three questions that govern daily fueling. They're not complicated.
What did I do yesterday? What am I doing today? What am I doing tomorrow?
Saturday was a three-hour loaded ruck on trail. Then a one-hour gap. Then a CSS swim set — three 650-yard intervals (~1K each) at critical swim speed. Two sessions. High combined demand. By any accounting of the first question, Sunday should have started as a maximum-priority carbohydrate recovery situation.
It didn't.
Here's the wrinkle I didn't solve cleanly. There was one hour between the end of the ruck and the start of the swim. The standard post-effort recovery protocol — 80 to 90 grams of carbohydrate and 25 to 30 grams of protein within 60 minutes of a hard effort — is not executable before an intense swim set. That's a GI incident waiting to happen in the water. So I deferred.
And then didn't execute after the swim.
Which meant Saturday's recovery window closed without the 3:1 protocol happening at all. Which meant the third question — what am I doing tomorrow? — also went unanswered. A 45-mile indoor session on the Lake Placid course demands a carbohydrate-elevated dinner the night before. That's Fueling Forward doctrine. Explicit. Written down. Mine.
It didn't happen.
Three questions. Three misses across 24 hours.
Sunday didn't fail because the fitness isn't there. Spending 93% of a three-hour ride in HR Zones 1 and 2 — nearly half of it at warm-up intensity — confirms the aerobic engine is functioning exactly as it should. It failed because Saturday's two sessions were processed as separate events when the OS treats them as a single metabolic unit. The ruck, the swim, the recovery window, the evening meal, and the Sunday ride are one connected sequence. Miss the middle and the end is already written.
Here's the corrected protocol for a compressed same-day multi-session day when session two is high-intensity aquatic work.
Between sessions, with a gap of 60 minutes or less: a small fast-carbohydrate bridge only — 30 to 40 grams of simple carbs, minimal protein, nothing that loads the gut before the pool. The full 3:1 recovery window (80 to 90 grams carbohydrate, 25 to 30 grams protein) shifts to post-swim. That's the executable sequence for the ruck-to-swim gap.
The Saturday evening meal then becomes the load-bearing Fueling Forward intervention for Sunday. Not a baseline dinner. A carbohydrate-elevated one — deliberately, because Question 3 has a long bike ride as its answer. If you train hard Sunday morning, you eat for it Saturday night.
And during the ride itself: 80 to 100 grams of carbohydrate per hour from the first hour, not as a response to fatigue. By the time you feel the deficit, you're already behind.
The Sunday data isn't a fitness problem. Bonking at 54% of FTP on a ride your device classifies as low aerobic base work is a substrate problem — a 24-hour cascade of missed OS checkpoints that individually looked manageable and collectively emptied the tank before the first pedal stroke.
The fix isn't a new protocol. It's running the one that already exists — including the modification for weekends where the gap between sessions is exactly wrong.
Ironman Lake Placid is in July. The course doesn't negotiate.
0 comments