The outcome you are walking toward
A diligence briefing you can give without collapsing Helix into "another membership app." You leave able to name what Helix owns as the fit vertical orchestrator, how it sits on Business OS, which public docks carry the substrate hops, and what is still staged or survey-dependent — without inventing retention rates or shipped coverage you have not seen.
Helix is an orchestration, not a point tool
Helix is the adaptive Training Intelligence OS for multi-location clubs and franchise networks. The public silo is MCV.FIT — Helix. Category-level posture only: membership-ops systems manage billing and sales; plan-apps deliver static programs; camera tools analyze in isolation. Helix is designed to fuse equipment telematics, multi-modal tracking, real-time feedback, and continuous progression / retention forging into one multi-tenant franchise organism — the outcomes layer on the shared substrate, not a bolt-on dashboard.
If a briefing treats Helix as a standalone SaaS SKU beside Business OS, ask how a single critical floor loop crosses sensing, interconnect, events, judgment, action, and forging without a second integration project per hop. The signal-order walkthrough is Walk the six-system substrate chain.
What Helix specializes (honest domains)
Public depth on the fit silo organizes around feature domains — use them as diligence vocabulary, not a feature scorecard:
- Member progression and retention — Journey DNA, form-verified progressive overload, adaptive programming, predictive retention flags, milestones. The operating record that keeps membership health honest is oriented by the fit membership health loop.
- Equipment and floor intelligence — occupancy, automatic workout logging, predictive maintenance, and MCV Axon as the fit-specific equipment-telematics specialization of Mesh (not a separate platform product page).
- Real-time feedback — camera form cues to member and trainer in the moment; near-PR alerts; ghost-trainer guidance between sessions; occupancy signals for staffing.
- Trainer and contractor economy — multi-tenant rosters, form review queues, performance scoring into skill forging, revenue attribution.
- Franchise — live topology, cross-club benchmarking, protocol propagation from strongest performers, HQ view of the network. Network learning itself is Franchise OS territory — Tell Business OS from Franchise OS.
Named-vendor battle cards stay internal. Public differentiation stays category-level.
Helix Coach — primary agent on the floor
Helix Coach is the named primary agent of the fit vertical. Mandate: real-time form quality, progressive overload, member Journey DNA, retention risk, and coaching cues — keeping members progressing safely. Style: precise, encouraging, relentless about quality of movement. It is designed to live inside floor loops (check-in, form deviation, near-PR effort, retention risk) alongside the trainer — not as a next-day report the member opens in an app.
Authority still sits on the shared floor: irreversible classes stay gated; brand scope fails closed; reconstructability lives in the audit trail. Counsel walks that story through Verify what an agent is allowed to do and governed agent boundaries.
Substrate docks Helix depends on
Helix is a specialized orchestration on the MCV substrate. Public docks you can open in a briefing:
- Mesh — physical interconnect; Axon specializes Mesh for equipment telematics. Interconnect fabric is not data fabric.
- Synapse — real-time loops between floor nodes.
- Forge — outcomes that turn experience into better playbooks and skills under governance.
- Pulse / Cortex / Aria complete the chain narratively; product docks for Mesh, Synapse, and Forge are the ones to name aloud first.
Composition of kits, agents, verticals, and Franchise OS is Name what the organism is made of.
Hardware and offline — survey before BOM
The physical posture for one Helix club is Spec the hardware for a Helix club: edge node, vision kit class, access, lockers and displays, kit tiers — all reference configurations finalized per site survey. Offline resilience is mandatory for always-open clubs; the careful public contract is Read the offline contract your locations run on. Where capability is staged rather than generally shipped, public copy says "designed to."
How to use this leaf in a briefing
- Open the silo first: MCV.FIT — Helix.
- Name Helix as vertical orchestrator on Business OS, not as a membership billing replacement.
- Walk Mesh → Synapse → Forge docks before any demo of "AI coaching."
- Push autonomy claims back to gates and evidence — never to a slide metric.
- Separate location runtime from network learning (Business OS vs Franchise OS).
- Pair with the hospitality sibling when the portfolio spans F&B: Brief Ember without mistaking it for a POS stack.
Non-goals for this leaf
- No retention percentages, uptime guarantees, or invented customer logos.
- No named-vendor battle cards or certification badge theater.
- No claim that every Axon integration path or vision zone ships at equal maturity on day one.
When Helix is clear, continue composition via organism composition and counsel review via diligence resources.