Skip to content
IronShift
The system
Article 03 · The system

What the AI reads.

Every input below feeds into next week’s prompt. Nothing you log is decorative.

  • Set-by-set logs (weight × reps × RPE) — the raw record of what you actually did. Drives progressive overload decisions.
  • Overall session RPE — your effort read at the end of each session.
  • Per-session feedback chips — the “weights too light,” “pace too easy,” “felt strong” signals you tapped at completion.
  • Free-text notes — anything you typed at session completion gets passed verbatim into next week’s prompt.
  • Weekly reflection — the “how did this week land” card. Three buckets (low / medium / high) plus optional notes.
  • Strava activities — when synced and auto-linked to a prescribed session, the AI sees your actual distance, derived pace, average HR, and max HR.
  • Extra activities you logged — anything off-program counts toward total weekly volume.
  • Injury notes, equipment sets, conditioning preferences, schedule, session duration windows, calendar overrides, VDOT, max HR, 1RMs — every settings input gets re-read every rebuild.
Related
The weekly rhythmYour program rebuilds every Saturday at 8 AM, reading everything you logged the prior week. The current week stays put; past weeks become read-only history.Per-session feedback chipsTap-to-select chips at session completion. Each chip is a structured signal the AI can act on next week — “weights too light” on Tuesday means heavier Tuesday next week.
IronShift