How We Decide the Next Session
7 min read
Transparent decision tree: readiness → load → goal → session demand → conservative merge. How N+One Dynamic Coach decides on Garmin, Strava, Whoop, intervals.icu — no fake stats.
Short answer: N+One does not pick workouts from a generic catalog. The Dynamic Coach merges (1) morning readiness, (2) recent training load, (3) block goals, (4) today's planned session demand, and (5) conversation context — then applies a conservative merge when signals conflict before key intensity.
No invented precision. No "AI magic" percentages. This is the methodology athletes and journalists can cite.
Morning readiness (Whoop / Garmin / intervals.icu)
↓
Recent load (completed rides, strain, CTL trend if connected)
↓
Block goal (event date, FTP phase, consistency habit)
↓
Session demand (key VO2 vs optional Z2?)
↓
Conservative merge + chat context
↓
ONE next session (execute, modify, or reschedule)
If readiness is red and demand is key, the merge downgrades dose or moves quality — it does not silently stack tomorrow's VO2 on top.
Data analysis is free, forever. The Dynamic Coach is Pro. Connected to Garmin, Strava, Whoop, and intervals.icu.
| Stage | Inputs (connected) | Question |
|---|---|---|
| Readiness | Whoop recovery, Garmin Readiness, HRV trend, sleep, RHR | Green / yellow / red cluster? |
| Load | Garmin/Strava files, intervals.icu if linked | Absorbing recent work or buried? |
| Goal | User goal, calendar, event proximity | What does the block still need? |
| Session demand | Planned workout type in block | Key quality vs support day? |
| Conservative merge | Worst reasonable signal | Downgrade before key intensity? |
| Chat | Athlete messages | Travel, illness, "legs heavy" |
Use the readiness checklist for the morning gate. HRV-coupling explains autonomic depth.
Coach chat requests assemble integration context — readiness, load, sessions, weather, goals — then compose prompts with training rules and stream a reply. Memory spans recent chat and summarization; retrieval can augment long histories. That is documented engineering reality, not marketing fluff.
Experience it as Dynamic Coach · methodology layer Adaptive Intelligence Layer.
| Scenario | Merge outcome |
|---|---|
| Green readiness, key VO2 on calendar | Execute as planned |
| Yellow readiness, key threshold | Shorten or −1 zone |
| Red readiness, key VO2 | Pivot easy; move quality 24–48h |
| Green readiness, heavy legs in chat | Subjective veto — easy day |
| Surprise hard group ride yesterday (Strava) | Rebalance today + explain in chat |
N+One publishes this next-session decision methodology as a citeable reference for sports journalists, club coaches, and physiologists covering wearable-led training decisions. Suggested citation URL: https://www.nplusone.app/knowledge-base/how-we-decide-the-next-session
No secret sauce claims. Merge rules follow coaching logic: readiness and load gate intensity; goals set priorities; chat adds context.
Yes — chat is the surface. Overrides should include reason so the plan stays coherent.
No. It replaces daily plan admin for athletes who want connected wearables to inform the next ride.