Routine setup has a new request path

Shipped

• Added a public routine conversion page for lifters who already have a spreadsheet, notes file, or written plan.
• Made the request path separate from the in-app Builder, so someone can explain the routine before deciding whether Protocol is the right place to run it.
• Kept the promise narrow: selected requests may be reviewed, but routine conversion is not guaranteed.
• Connected the page back into the existing Resources flow instead of hiding it as a support-only option.

Why

Not every serious routine starts as a neat app preset.

Some lifters already have the plan they trust. It might live in a spreadsheet, a coach note, a PDF, or a few weeks of copied training blocks. The awkward part is not belief in the routine. The awkward part is turning that routine into something executable without spending the first session rebuilding every day by hand.

The new request path is for that moment. It gives someone a public place to say, "this is the plan I am trying to run," without pretending every spreadsheet can be converted automatically or instantly.

That distinction matters. Protocol is still a routine compiler, not a magic import box. The app should make routine setup easier, but it should not blur the line between a structured request and a finished training plan.

Notes

• The page is meant for routine setup friction, not medical, nutrition, or coaching advice.
• Submitting a request does not guarantee that a routine will be converted.
• Imported or converted routines still need review before they become something a lifter should execute.

Next

• Keep watching where routine setup gets stuck: presets, imports, blank Builder starts, and request paths.
• Use those signals to decide which routine families deserve first-class setup support next.