Methodology

The Training Science Behind Joules: How an AI Actually Coaches a Season

"AI cycling coach" sounds like a chatbot guessing. It shouldn't be, and good ones aren't. Here's the actual methodology underneath Joules — the periodization models, the intensity math, the load-to-recovery logic, and the honest places it stops — so you can judge it the way you'd judge any coach: on the reasoning, not the marketing.

If you've used a raw chatbot for training, you know the failure mode: confident, generic, and amnesiac. It restarts you every week instead of progressing you. The fix isn't a smarter model — the frontier models already know more training science than most riders. The fix is giving the model a coach's structure: an explicit knowledge base to reason from, a periodized plan to work against, real load math, and a feedback loop. That's what this post is about.

It plans from an explicit knowledge base, not from memory

Joules reasons against a structured cycling-science reference covering energy systems, adaptation timelines, periodization, intensity distribution, progressive overload, tapering, and discipline-specific prescription. That matters because it pins the coaching to known physiology rather than whatever the model happened to absorb. A few of the load-bearing ideas:

It chooses a periodization model — it doesn't have one default

The first real coaching decision is structural: how to shape the season so you arrive ready on the right day. Joules selects the model from your situation rather than forcing everyone through the same template:

Phases then get real durations and intent: a base phase of 6–12 weeks at high volume and mostly easy intensity; a build phase that raises specificity and adds threshold/VO2max work; a short, sharp peak; and a taper. Training specificity increases as the event approaches — that progression is the whole point of a plan.

Intensity distribution: mostly easy, on purpose

How your weekly time is split across intensities is one of the highest-leverage choices in training, and the evidence favors keeping most of it genuinely easy. Joules works from the three standard distributions and matches them to your available hours:

The recurring mistake it's built to avoid is the "grey zone" trap — riding the moderate-hard middle so often that the easy days aren't easy and the hard days aren't hard. Zone 2 at the aerobic threshold is where mitochondrial density and lactate clearance get built, and it's protected accordingly.

The load math is the industry-standard kind

Coaching runs on measured stress, and the measurement has to be trustworthy. Joules computes Training Stress Score (TSS) using the Normalized Power algorithm — the same method behind TrainingPeaks and Intervals.icu — rather than a naive average, so variable-intensity sessions are scored accurately and line up with the numbers you already read elsewhere.

When the coach prescribes an indoor session, a workout solver builds the actual intervals to hit a target TSS within the right intensity band, using explicit zone bands and rest ratios and respecting how anaerobic work capacity (W′) depletes and reconstitutes during recovery. Every structured target is written as a percentage of FTP, so when your FTP moves, the whole plan recalibrates automatically. Don't have a current FTP? It can prescribe a ramp test first.

Progression and recovery are prescribed, not accidental

Getting harder is easy; getting harder sustainably is the craft. The rules Joules works within are the conservative, well-supported ones:

Tapering follows the same evidence: drop volume 41–60% over roughly 8–14 days, hold intensity, and you can expect a performance bump on the order of a few percent. How fresh you arrive is tuned to the race's priority — sharper for an A-race, less so for a training-stimulus B-race.

The feedback loop is the part a static plan can't do

A plan you can't deviate from isn't coaching. Each Joules week is written with an explicit intent — build, recovery, peak, or taper — and a target load. Once your rides come in, the week is graded against what you actually did, and the next week is shaped by that result together with your fatigue-and-freshness trend (CTL / ATL / TSB) and your own post-ride reflections. Build weeks get harder on purpose; recovery weeks pull back on purpose. Nothing drifts.

Crucially, the load metrics are treated as instruments, not prescriptions. CTL, ATL and TSB point at directional risk — "you're digging a hole," "you're fresh enough to race" — but the literature is clear that individual response varies by 30% or more, so they inform the decision rather than dictate it. Your own history at a known freshness level beats a textbook number every time, and the coaching is built to defer to it.

The honest limits

A methodology piece that only lists strengths isn't honest. Here's where an AI coach — Joules included — genuinely stops:

The takeaway

The interesting question was never "can an AI talk about training?" — it always could. The question is whether it coaches from a defensible method: a periodization model chosen for your season, an intensity distribution that protects the easy days, load math the rest of the industry uses, conservative progression with real recovery, and a feedback loop that adapts to the rides you actually do. That's the bar Joules is built to clear — and to be candid about where it doesn't.

Want to see the method produce something concrete? Read a real Joules training week, day by day, or build a sample week yourself in your browser — no account or connector needed.

Judge it on the output.

Joules is an MCP app that gives ChatGPT and Claude a cycling coach's brain — it interviews you, builds your season, plans every week, and grades each week against your real rides. Device-free. Free while Joules is in beta.

See how Joules works