Programming Philosophy

A workout is not one thing. It is an ordered set of blocks, each with its own job, and most days use four or five of the nine kinds alongside. The blocks are reusable: a strength piece written once can be programmed again three weeks later against the same numbers, which is what makes progression something you can look up rather than something you have to remember.

Two things get decided before a single movement is chosen — the time domain and the rep volume. A session is written to land in a duration bucket (a minute to five, five to ten, ten to twenty, twenty and up, or a heavy day with no clock at all) and to a rep range of low, medium or high. Picking movements first is how a month accidentally becomes six versions of the same twelve-minute AMRAP.

Only then do the movements go in, and they go in by pattern rather than by name. Squat, hinge, upper-body push, upper-body pull, core: the block gets built out of the patterns it owes, and the specific movement is the last choice made, not the first.

Loads are written the same way — as a prescription rather than a number, so a percentage of your own best lift resolves to your weight and not somebody else's. Everything scales. The session is the shape of the work; where you meet it is yours.

Every movement in the library carries its modality, its movement pattern and the muscle groups it trains. That means a stretch of programming is not just a stack of workouts — it is a distribution, and a distribution can be added up.

The default window is the trailing 28 days, with a 7-day and a 90-day view beside it. Anything longer than a quarter stops describing current programming and starts describing history. Rolling that window up produces the shares alongside, and a fixed set of limits runs over them. Those limits live in code rather than in a settings form, so changing one is a deliberate edit with a test attached instead of a slider that can be quietly detuned until nothing ever warns.

On top of the arithmetic, a written review reads the numbers back — the part the limits cannot see: how the axes interact, the shape of the window over time, and which of several findings actually matters most. It reasons only from the computed report and has to name the figure it is reading. Where something is not measured, it says so rather than guessing.

The same arithmetic runs forwards. Before a block goes out, the coming days are rolled up the same way and measured against the gym's own recent cadence rather than an assumed seven-day week — so a gap gets closed while it is still a plan, instead of after it has been trained.