Classes and generated sessions

Available versus selected

Class programming should be visible for the day because it is useful context. Visibility does not mean commitment.

Select a class only when you want it to shape the plan. Leave its details available when you might ignore it.

Decision rules

• Choose the class when its stimulus fits the week and does not compromise tomorrow's key endurance session.
• Choose a generated supplementary session when the class overworks a recently loaded pattern, stacks too much eccentric leg work, or misses an important movement gap.
• Choose no supplementary work when fatigue, soreness, race phase, or illness makes the extra dose unhelpful.
• Keep key endurance sessions protected. Supplementary training adapts around them, not the other way round.

AI review expectations

The review should explain the intended class stimulus, likely muscle-group cost, and next-day risk.

For generated sessions, it should explain which movement gap it addresses and why the dose is recoverable.

Good guidance sounds like: upper pull, trunk rotation, and grip are under-served, but lower-body run load is high; prescribe low-eccentric pull/core/skill work rather than heavy legs.

Movement coverage strategy

Movement coverage is not a symmetry target. It is a guardrail for avoiding stale patterns and unnecessary overuse.

Full-body movements can be efficient when supplementary sessions are limited, but the app should still avoid repeatedly loading the same tissues before key endurance work.