The roadmap needs product-truth labels
Protocol is tightening how it talks about live Training behavior, in-development Coach work, and research around future modules.
The boundary
Product direction becomes less useful when every idea is written like a launch announcement. Protocol needs room to show where it is going, but the reader should always know whether the work is live, in development, or still being researched.
Training is the live product. It runs structured routines, target loads, completed and missed work, substitutions, history, and progression context. Coach is an in-development professional layer. Supplements is a planned, research-gated module around choices a person has already made.
Why we are tightening the language
Future-facing copy often becomes vague at exactly the moment it needs precision. A coach workspace can sound complete when only the architecture exists. A supplement tracker can drift into recommendation language when the intended job is organization, history, and supply. A founder note can make a confident thesis while still stating what evidence is missing.
Protocol's public writing will now carry those distinctions close to the claim. The availability reset should appear before a planned workflow is described in detail, and the mechanism should be concrete enough for a cold reader to understand why the direction matters.
The editorial test
Every important update should answer five questions: what changed, why it matters, how the workflow behaves, what is true today, and what remains unresolved.
This also changes the tone. We want fewer abstract feature lists and more of the actual work: the missed set a coach has to interpret, the imported routine that must receive a fresh local identity, or the inventory count that should stay correctable instead of becoming a health claim.
Next
The Updates timeline and social drafts will use the same product-truth boundary so a teaser can create interest without borrowing certainty from a future release.