Context before conclusions.
Pace means something different on heat, hills, mud and tired legs. 2537M keeps those differences visible.
2537M turns completed runs, route, elevation, body signals and fueling practice into a training plan that keeps learning.
Pace means something different on heat, hills, mud and tired legs. 2537M keeps those differences visible.
Repeated, comparable runs matter more than a single number. Missing evidence stays missing.
Connections are optional, recommendations are explainable and health data is never used for advertising.
2537M connects what the watch records with what only the runner knows, so tomorrow’s decision reflects the full training story.
Start with this week’s work, today’s session and the action that matters now.
Put route, pace, heart rate, time and elevation into one usable run record.
Measure grade, climbing, descending, power hiking and run-to-hike transitions.
Keep actuals intact and adjust future sessions from the training you really completed.
Compare recent load with your established pattern and see the change over time.
Shape carbohydrate and fluid targets with completed runs and recorded GI response.
Calculations, safety gates and plan limits stay deterministic. The intelligence layer explains the approved decision using a compact evidence packet—not an uncontrolled dump of health data.
Activities, heart rate, sleep, HRV, elevation, weather and runner-entered feedback retain their source and timestamp.
Rolling load, durability, comparable-run trends and readiness components are labelled as estimates with confidence.
Plan adaptations explain the evidence used, respect ceilings and never treat a missed session as training debt.
2537M requests only the runner-authorized data needed to understand training, recovery and progress. Connections are read-oriented and can be revoked by the runner.
Completed workouts, duration, distance, route, elevation, heart rate, cadence, laps and available environmental context.
Used for the training record, rolling volume, load context and comparable-run analysis.Sleep, resting heart rate, HRV, daily activity and basic profile information when the source makes them available.
Used as supporting trends—not diagnosis, treatment or a definitive readiness verdict.Historical and newly available activities synchronized after the runner connects an account.
Used to avoid starting from zero and to preserve an existing training plan wherever practical.Account authorization uses provider-approved OAuth flows. Tokens stay on the server, access is limited to the approved scopes, and imported records retain source provenance. A runner can disconnect a provider and remove 2537M’s access.
2537M is currently being developed for iPhone, with a portable data model designed for future Android support.