The research behind the plan

The engine was built for mountain ultras first, and that is where most of these papers come from; the physiology of carbohydrate absorption, hydration and glycogen is the same on a road marathon or a long ride, and the targets scale with duration and effort. Every rule in the fueling engine points at one of the sources below. The plan screen in the app shows the same references next to each number under "Why these numbers". Where the evidence is thin, the app says so and calls the figure a working assumption.

Carbohydrate intake

Gut trouble

Fluids and sodium

The tank: the glycogen estimate on the watch

Starting glycogen

The tank starts at a value scaled to body mass: 7.5 g per kg after a race-week carb load, 6 on an ordinary day, about 5.4 fasted, since an overnight fast drains roughly half of the liver's 80 to 100 g while muscle stores are untouched (Nilsson and Hultman, 1973; Bergström and Hultman on muscle glycogen). The app calls this a working assumption and lets you set an exact number.

The runner's own data

Alongside the literature, the rules were checked against one ultra runner's logged races: a 48 km mountain race fuelled at about 73 g/h for ten hours with no gut trouble, a race lost to a protein drink mix, and a hand-built 80 km plan the engine had to reproduce before it was trusted. Those are private records and are not published; they are the reason the engine treats protein during a race as a hard exclusion and front-loads the gels.

General guidance from published research and the data you enter. Not medical advice. Rehearse any plan in training and listen to your body over any prompt.