Working backwards from a hundred

Most training plans answer one question: what are you racing, and when? It's a good question. It just has a horizon of about eight months, and you are — with luck — planning for another forty or fifty years.

Peter Attia's Centenarian Decathlon is a framing device for the other horizon. Name the physical things you want to be able to do in the final decade of your life, specifically. Then work backwards from there to what you should be training now. Not "stay healthy." Not "age well." A list of tasks, with verbs in them.

It's a genuinely good idea that tends to get filed in the wrong drawer. It shows up as a wellness section — a separate longevity plan sitting politely beside the real training, mostly consisting of mobility work and things you already know. And so it gets skipped, because when the training week is tight, the thing labelled "longevity" is the first thing to go.

For an athlete who is still racing, that split is a mistake. The decathlon isn't a parallel plan. It's the constraint the racing plan runs inside.

Backcasting, and the margin problem

The mechanics are simple. Pick a target age. Name the tasks. Work out what capacity each task requires. Then work out what capacity you need today for that to still be true then.

The last step is where it gets uncomfortable, and where the whole framework earns its keep.

Physical capacity declines with age. How fast is a genuinely contested question — the ranges in the literature are wide, they differ by quality, and they depend enormously on training status, which is the whole point of doing anything about it. So this isn't a calculation you should pretend to do to two decimal places.

But the direction is not in doubt, and the direction alone is enough to produce the insight:

The task doesn't get easier. Your capacity gets smaller. So the requirement isn't "be able to do it now" — it's be able to do it now with enough margin left over to survive the decline in between.

Getting off the floor unassisted at eighty-five isn't trained by being able to get off the floor at fifty. Everyone can do that at fifty. It's trained by having enough leg strength and hip mobility at fifty that decades of drawdown still leave you above the line. Carrying a grandchild up a flight of stairs at eighty isn't a mobility problem. It's a strength reserve problem, and reserves are built in your forties and fifties, at loads that look excessive for the task and are exactly right for the horizon.

That's the reframe. The Centenarian Decathlon isn't a gentler kind of training. It's an argument for heavier, more deliberate strength work than a pure race schedule would ever justify — because the race is a deadline and the decathlon is a balance sheet.

Make it a list, with dates on it

A decathlon item that isn't testable is a wish. The discipline of the framework is that each item gets specific enough to be scored, and gets an actual test date, the way a race gets one.

Compare:

The right-hand column can be programmed for and tested against. The left-hand column can only be felt guilty about.

Five to eight items is plenty. They should be yours — the actual life you're planning to have, not a generic list — and at least a couple of them should be things you'd be slightly embarrassed to fail at today. If every item is comfortable, you've written a description of the present rather than a target.

Then give each one a test date. Not the age in the item — a date in the next twelve months when you'll check where you stand relative to the trajectory. A decathlon item you never test is indistinguishable from one you never had.

Why they belong on the same calendar

Here's the structural claim, and it's the whole reason this ends up in a periodization engine rather than a journal.

A decathlon target and a race are the same shape. Both are a dated goal, in a nameable discipline, with a target metric and a priority. A 70.3 in June and "deadlift 1.5× bodyweight for 5 at 60" differ in their time horizon and in nothing else that matters to a planner. Both should be co-equal anchors that blocks get sequenced around — not a race calendar with a wellness appendix.

Put them on one calendar and three things happen that don't happen otherwise.

The decathlon starts winning arguments. A pure race schedule has no reason to programme a hypertrophy block. Racing rewards being light and aerobically deep; muscle mass is, to a triathlon calendar, mostly cargo. The decathlon has the opposite view — muscle and bone are the reserve that everything in the final decade draws on — and once it's on the calendar as a dated anchor, "eight weeks of hypertrophy in January" stops being a nice idea and becomes a block with a reason.

Conflicts become visible in advance. When a race build and a strength target want the same eight weeks, you find out in November instead of in March. And the resolution is usually available, because they rarely want the same eight weeks — they want eight weeks each, in an order somebody has to choose.

The cost of a season becomes legible. This is the one I'd argue matters most for masters athletes. Some races are worth a tendon. Most aren't. When the only thing on your calendar is the race, every decision defaults to the race. When there's a fifty-year target sitting next to it, the question "is this build worth what it's going to cost me?" has something concrete on the other side of the scale.

Racing now is how you train for it

The nice part of all this — the part that makes it a coherent plan rather than a compromise — is that the two horizons want overwhelmingly the same things.

The decathlon wants strength reserve, muscle mass, bone density, aerobic capacity, connective-tissue resilience and the ability to keep doing hard things for a long time. That is a description of a masters endurance-and-strength athlete's training year. It's not adjacent to it. It's the same list.

Racing is what gives that list structure. A dated event forces genuine intensity, real progression, tapers, and the honesty of a result. "Train for longevity" with no event on the calendar decays into comfortable maintenance within about two months, and comfortable is precisely the thing that doesn't build reserve.

So the sequence runs in one direction, and each level sets the terms for the one above it:

this week's block → this season's races → the decathlon at 100.

Racing now and lasting later were never competing plans. Racing is the training method. The decathlon is what it's for.

Where the framework runs out

Worth saying plainly: nobody has run the trial. There is no evidence base establishing that a specific list of tasks at ninety is best served by a specific plan at fifty. The components are well supported — strength training preserves function and bone, aerobic capacity tracks with healthspan, muscle mass matters more the older you get — but the backcast itself is a reasoning device, not a finding.

That's fine, as long as it's held honestly. The framework's value isn't predictive precision. It's that it makes a fifty-year horizon concrete enough to argue with, and puts something on the other side of the scale when a race build wants more than it should get.

Pick your list. Put dates on it. Then let it argue with your race calendar — and take the argument seriously, because it's the only voice in the room representing the person you'll be at eighty.