Create a short, evidence-bound return-to-running plan ending in one owned timed-distance benchmark, without requiring an approved VDOT or race methodology. Use when baseline fitness is missing, disputed, conflicting, or stale after inactivity and the athlete is not seeking injury rehabilitation.
Confirm an ownership-paired benchmark activity or exact canonical segment, create an immutable assessment review, archive the completed assessment, and prepare a VDOT proposal. Use after the benchmark workout has been published, synchronized, and recorded with provider-paired fulfillment.
Sets up the Resilio environment for non-technical users on macOS with safe, gated validation. Use when users ask to get started, install dependencies, or recover an interrupted setup session.
Onboard a new athlete through authentication, coordinated sync, athlete-confirmed profile and goal capture, then route to either qualifying VDOT evidence and race planning or a non-injury baseline-assessment plan. Use for first-time setup or a new athlete profile.
Create a methodology-explicit Monday-Sunday macro plan skeleton from an approved baseline VDOT, confirmed profile, and goal, then return it for separate athlete approval. Use after baseline VDOT approval and before exact weekly workout generation.
Review progress across multiple completed weeks of the current training plan using typed weekly contexts, exact fulfillment identities, and coverage-aware Intervals.icu-native evidence. Use for multi-week plan recaps, trend questions, or “how is my training going so far?”, not a single-week review.
Review and close an active training cycle from exact plan, activity, course-result, adherence, multisport, recovery, and coverage evidence, then prepare the immutable historical context for its successor. Use when an athlete asks for a new or replacement plan, reaches a plan horizon, changes goals midcycle, or stops a…
Detect and confirm that one synchronized running activity fulfilled an approved workout in the current active plan on another day in the same Monday-Sunday week, then reconcile the local fulfillment overlay and native Intervals.icu activity/event pair safely. Use for early, late, or same-day unpaired execution after…
Inspect and reconcile one exact applied week's running-workout desired state with Intervals.icu, using semantic readback, owned drift protection, and honest Garmin-forwarding status. Use after weekly application, for explicit sync requests, retries, or diagnosis.
Propose an evidence-backed baseline VDOT from exact race, personal-best, manual, or closed owned-assessment evidence without mutating approval state. Use when a race macro needs baseline evidence or the athlete asks to reassess race-performance equivalence.
Review one Monday-Sunday training week or a mid-week check-in using typed Intervals.icu-native coaching context, exact owned-workout adherence, separate run and other-sport exposure, recovery signals, and evidence coverage. Use for “how was my week?”, “how is this week going?”, or single-week plan adherence.
Apply an exact weekly plan file whose current bytes and path were explicitly approved by the athlete. Use only after weekly approval is recorded; never use to generate or revise workout content.
Design and validate exact workouts for one existing race-macro or baseline-assessment week without applying them. Use for Week 1, a subsequent unpopulated week, or a revised weekly proposal that still requires athlete approval.