What turns your running data into your next run?

01 · The problem

The data piles up and never answers today’s question

The data piles up in GPX files and Strava exports and never answers the one question asked before leaving the house.

02 · Why now

One runner, 70 days, and an archive already sitting in exports

This is one runner chasing a sub-18 5 km in 70 days, and the archive is already there in GPX files and Strava-style exports. Nothing outside changed. The open question is whether anything reads that history back and changes tomorrow, and whether an app that never built it will let it out at all.

03 · The idea

A coach that reads yesterday and writes tomorrow’s run

It sets the plan, learns what you actually did, and adjusts tomorrow’s run.

04 · Who it’s for

Built for one runner chasing one 5 km goal

A runner training alone, with a watch full of exports and nobody reading them.

05 · Instead of

It refuses the feed that keeps the big apps sticky

A public feed, kudos, and an audience.

06 · What it would take

The plumbing is done, the coaching logic is the work

It runs today on a Worker, a KV namespace, static pages and a route map, which is enough for one runner. Making it anyone else’s means reading a stranger’s history out of an app that was never built to share it, and standing behind day-to-day adjustments for a body I know nothing about.

07 · What would prove it wrong

A runner who stops going out with nobody watching

If the plan keeps being written and the runs stop happening, the adjustment was never what held anyone to it, and the feed and the kudos were doing that work all along. The same holds if the daily changes turn out to be noise dressed as coaching.