Protocol Coach becomes a separate workspace
Protocol Coach is taking shape as a separate professional workspace connected to the same structured Training system.
The direction
Protocol Coach is becoming a separate workspace for professionals who need to assign structured training, review what happened, and make the next decision without rebuilding the week from messages and screenshots.
The separation is deliberate. A coach needs roster, client, assignment, and template workflows. An athlete needs today's training, the active plan, and control over what is shared. Forcing both jobs into one navigation model would make each product harder to understand.
What exists on the Coach branch
The foundation now includes a dedicated Coach app shell, client and assignment surfaces, template routes, authenticated server boundaries, and the first shared domain contracts for access and plan assignment.
Training remains the execution environment. Coach connects to that environment through explicit contracts rather than copying the workout engine or creating a second definition of a routine.
Why this shape matters
Coaching software often begins with a large dashboard and works backward toward the actual decision. Protocol is starting with the handoff: what the coach assigned, what the athlete received, what work was completed, and what context the athlete chose to share.
The workspace should prepare that evidence while the coach retains responsibility for the programming call. It should also remain useful when a client trains offline, when a plan changes, or when the relationship ends.
Availability
Protocol Coach is in development on the Coach branch. It is not a public release, and access remains invite-only while the product, consent, lifecycle, and commercial boundaries are validated.
Next
Turn the workspace foundation into a connected flow for invitations, assignments, plan history, and client review without weakening the local-first Training product.