One routine builder now serves Training and Coach
The Coach branch now uses the same routine-authoring and builder contracts as Training instead of carrying a second editor.
What changed on the branch
Protocol Coach can now create and edit structured routines through the same underlying builder system used by Training. The host changes, but the definition of a runnable routine, the exercise catalog, set logic, validation, and authoring behavior stay shared.
The work extracted canonical exercise data, routine-authoring rules, builder UI, and shared controls into packages that both apps can consume through narrow host adapters.
Why one builder matters
A second editor would have created a quiet product split. A routine could validate in Coach and fail in Training, an exercise could exist in one catalog but not the other, or the same progression rule could behave differently depending on who created it.
The shared builder makes the contract explicit. Coach supplies professional context, server revisions, custom exercises, and assignment workflows. Training supplies the athlete execution environment. Both work with the same routine shape and validation rules.
What the connected foundation adds
The Coach workspace now includes client detail, assignments, plan lineage, template editing, preferences, authenticated resource loading, and the first demo contracts that exercise the relationship between a coach-authored plan and an athlete's recorded work.
This is also an offline-safety decision. The runnable Training copy should remain usable when the Coach workspace or network is unavailable, while later sync can preserve authoritative assignment state without making the workout depend on a live request.
Availability
The connected Coach foundation is implemented on the Coach branch and remains in development. Coach is invite-only and has not been released publicly.
Next
Add consent-scoped context, clearer performance views, and safer entry lifecycle behavior while keeping the shared builder as the single source of truth.