Drafting a program from RIRLift data

Reference material for an AI asked to draft a training block from a RIRLift pack. The glossary — RIR, effort accuracy, e1RM, hard sets, weighted volume — is on the analysis page.

Nothing here is personal or instructional. The pack works from its own inline text.

What RIRLift actually knows

The pack carries what the lifter has logged, plus the routines they have saved. That is a real and unusually honest picture of how someone trains: observed frequency, observed volume tolerance, the exercises they actually perform, and the effort accuracy with which they execute their own plan.

What RIRLift does not know, and never asks

• Their goal. The onboarding questionnaire's answers build a starting plan and are then discarded — the app does not store a goal, so no pack can carry one.
• Their training age, bodyweight history, age, sex, injury history, or constraints.
• What equipment they own. A pack lists the equipment they have logged work with. That is evidence of use, not a statement of access — a lifter may own a barbell they haven't touched in a month, or train at a gym with far more than they've used.
• Their schedule, beyond how often they have in fact trained.

All of it is worth asking about. None of it should be assumed.

Importing

RIRLift cannot import a program from an AI yet. A draft will be read by a person, not pasted into the app, so plain readable prose serves them better than a machine format. There is no schema to target; if a future version of the app gains an import path, this page will describe it.

Whose program is it

A program drafted from this data is the AI's work, not RIRLift's. RIRLift's own load engine only suggests weights from logged sets. Saying which parts of a draft rest on the lifter's own data and which on general training knowledge lets them judge it — which is the point, because they are the one who has to do it.