Progress log
Plan Engine versions
The training-plan engine's own version history — separate from the app release version, so we can refer to exact engine behaviour. Currently on Plan Engine v0.10.
v0.10
Truer weekly load from the intensity you'll actually ride
Latest 2026-07-13- Improved The engine now sizes each week's training load from the real intensity of that week's mix — an easy endurance week carries far less load per hour than a threshold-heavy one — instead of one flat average. Your weekly hours are honoured more precisely and hard days are no longer quietly over-sized against a mixed-week guess.
v0.9
The engine shows its thinking
2026-07-13- New Each week on the plan now shows the coach's intent at a glance — its focus (Aerobic, Threshold or VO₂) and whether the week pushes, holds or eases off — which the engine had been deciding silently.
- New A "why this plan looks the way it does" trail spells out the reactive adjustments the engine makes on top of the base plan: hard sessions eased after real fatigue, days pulled back to the recovery floor, the lead-in to arrive fresh, and two-a-day splits — each with a plain-language reason.
v0.8
Weekly load lands on your real hours
2026-07-09- Improved Weekly hours are now a two-sided budget: the engine trims as well as pads so the plan lands on the time you actually have, and the build progression shows up as a gentle volume ramp rather than an ever-growing load.
- Improved Time-crunch mode was reworked to use the whole week — weekends included — for quality without ever stacking two hard days back to back.
- Changed Adaptive day-to-day re-tuning is now opt-in: every plan is built complete and safe on its own, and adaptation is a deliberate choice on top.
v0.7
The AI can shape your week, and a smart run-in to the start
2026-07-09- New An opt-in expert setting lets the AI coach set each week's emphasis and whether it pushes, holds or absorbs load — reshaping the deterministic plan within safe bounds, never authoring it from scratch.
- New When a plan starts a few days out, the engine bridges today to the start with easy or priming rides so you arrive fresh; these lead-in rides sit outside the plan's own load.
v0.6
Every session explains itself, in a coach's words
2026-07-09- New After the plan is locked in, a coaching pass writes a short, structured rationale for each session — the headline, why it's here now, how it should feel and what to focus on — grounded in real facts from your data rather than filler.
v0.5
The engine honours an expert macro-cycle rhythm (2:1 / 3:1 / auto)
2026-07-09- New Expert plans can pick a 2:1 or 3:1 build-to-recovery block, or let the engine recommend the macro rhythm from current fitness, fatigue, weekly hours and chosen hardness.
- Improved Week-role placement now honours that macro-rhythm choice across both rolling fitness blocks and race builds — including a true third build week before recovery when 3:1 is chosen.
v0.4
The engine follows your chosen training window end to end
2026-07-09- New Plan creation now takes a start date and a length — fitness or maintenance blocks of 3, 6 or 9 weeks, or a custom range up to 9 weeks.
- Improved The engine carries that timing window through the whole generation: it scales partial weeks correctly and passes the start and end dates into the final coaching pass.
v0.3
The engine shapes the plan around how hard you want to train
2026-07-08- New Plan generation now takes a training-hardness setting on a 1–5 scale, from easy and recovery-friendly to maximum load.
- Improved The engine uses that hardness to shape weekly load, hard-session density, adaptive recovery and the final coaching pass — all inside the same available training hours.
v0.2
The engine now reads cleaned 30/90/180-day power windows as its capability baseline
2026-07-08- Changed The rider snapshot now builds its planning capability from a cleaned recent power profile instead of leaning mainly on the profile FTP field. It reads 30 days as current form, 90 days as stable current level, and 180 days as longer-term potential.
- Improved Limiter targeting now prefers the rider's current power-profile phenotype when real ride data exists, so the engine's hard-session emphasis follows the recent curve more closely.
- Improved Race-target gap analysis now compares the current 30-day level against the longer 180-day ceiling at the key event duration, so the engine can see where the rider is now versus what they have recently shown.
v0.1
Baseline Plan Engine snapshot
2026-07-08- New Plan Engine now has its own version stream, starting at 0.1, so we can refer to engine behaviour separately from the Moveee app release version.
- New Version 0.1 captures the current engine baseline: rider-state snapshotting, race/fitness/maintenance periodisation, week-role placement, TSS allocation, workout block generation, fatigue guardrails, double-day splitting, Strava retune, and AI review/polish layers.
- New A snapshot archive was created so this engine baseline can be restored or compared later.