Presets and progression got deeper

Shipped

• Added more source-backed preset and program coverage, including PHAT-style and Phrak Greyskull-style additions.
• Added Wendler and Madcow-style anchor modeling where the routine logic needs stable reference numbers.
• Added AMRAP targets and shared load anchors so progression can express more than fixed straight sets.
• Added staged miss ladder support and top-of-range rep progression for routines that do not progress in one simple jump.
• Hardened manual reseeding so a lifter can correct starting values without breaking the progression record.
• Added public preset resource coverage so the site can explain what the app supports without overclaiming.

Why

The difference between a workout tracker and a routine compiler shows up in progression.

It is easy to store "3 sets of 5." It is harder to model what should happen when the last set is AMRAP, when the next weight depends on a rep range, when a missed target has staged consequences, or when a routine needs a training max rather than a raw one-rep max.

That is the work behind this release. Protocol is getting better at representing routines as logic, not just rows in a table. More presets matter, but the larger step is that the app can now describe more of the rules that make those presets worth running.

The public resource work follows the same boundary. Protocol can explain supported routines and setup paths, but it should not pretend to own programs it did not create.

Notes

• Source-backed does not mean Protocol owns the original program.
• Some routines are represented as app-compatible interpretations, not official versions.
• Manual reseeding is for correcting progression inputs, not rewriting completed training.

Next

• Keep expanding routine support where the logic can be represented honestly.
• Keep public preset pages aligned with what the Training app can actually run.
• Keep progression rules explicit enough that a lifter can understand why the next workout changed.