Plans Are Static. Real Life Isn't.

Part one — one person, one plan, reality changing underneath it.

Plans are static. Real life isn't. You penciled in 10 km at tempo for Saturday morning — and then the week happened to you, and the plan on your screen has no idea.

You ran 14 km on Tuesday. You slept five hours. Your lower back has been talking to you since. Rain is forecast from six, and the loop you had in mind has no cover. The plan still says 10 km, tempo, exposed loop, 6am. Nothing about it moved — and you are the one who absorbs the difference. Not twelve people. You.

That gap — between the plan as written and you as you actually turn up — is the whole problem. The plan was a hypothesis made days ago, under assumptions that have quietly stopped being true. Call it state drift.

Where today's tools stop

Three kinds of software already touch this Saturday, and each one stops exactly one step short of being useful.

• The training plan is static: here is what you planned. It has no idea what this week did to you.
• The readiness score reads your body and says: it's an amber day — go a little easier. Then nothing about the actual session you had on the calendar.
• The injury or clinical app hands you information about a niggle, or a generic program, or a route to a professional. It also has no idea what you were about to run.

A score tells you it's an amber day. It never tells you what to do with Saturday.

That is the missing layer, and it is a narrow one. Sledge is not trying to build a better score, and it is not trying to become a rehab program. It sits in the one place none of those tools stand: given your current state, and given what you were actually about to do, here is what the session should become.

State overrides the plan

Not because the plan was wrong — because a plan is only a guess about a future that has now changed. The person lacing up on Saturday is not the person the plan assumed on Wednesday. So the hierarchy is simple:

Current state > original plan. When reality moves, the plan should move with it — and the latest state is what decides how.

What Saturday becomes

This is the whole product, in one runner's morning. Two kinds of truth arrive that the plan never accounted for — what is true about you, and what is true about the world around the run:

Sledge reads the consequences of those, not the raw numbers — and turns them into a handful of product-sized changes to the session you already had:

Notice what the interface never says. It does not say your back is injured, and it does not say you are overtrained. It says here is what Saturday should become. Decisive about the experience; silent about your body. That line has to hold: Sledge helps you understand what should change — it does not tell you what you are medically cleared to do. The person, and where it matters a professional, makes that call. Sledge just makes it better-informed.

Building, not shipped: this adaptive layer is what Sledge is being built toward, not something that already ships. It rests on the runs, the conditions, and the record it already holds.

Reduce, don't dump

The signals already exist. A great deal of your internal state sits in the wearables and apps you already use — sleep, resting heart rate, recent load, the run you did Tuesday — and the external state is a forecast and a map. Sledge does not need to rebuild any of that. It needs to pull what exists and then do the harder thing: throw almost all of it away.

You should never see this:

Those are signals, not answers. The only question worth asking is: what among these materially changes Saturday? Most of it should disappear before it ever reaches you. And the reduction only works because Sledge reads the state against the plan — state times the session you actually had. Without the plan, you have analytics. Without the state, you have a static training plan. Put them together and you get adaptation.

The trick is timing — before you are too deep

The value is almost entirely about when this happens. Telling you afterward that you accumulated high strain is a fact you can no longer act on. The useful version reconsiders the experience as the start approaches, and hands you the answer while you can still use it:

So you step out the door already informed — not corrected after the fact, when it is too late to change anything.

And then the result becomes new state

You run the easy 8 on the sheltered loop. The back holds. The tempo is waiting on Thursday. What actually happened is not the end of anything — it is the input to the next plan. The loop closes:

And the next Saturday starts from what is true, instead of from a guess made a week ago.

What this is not

Because a thesis this useful can sound greedy, the boundary matters. This is not:

• a diagnosis, or a judgment about what is medically safe;
• a rehab program, or a substitute for a professional;
• a better readiness score;
• an excuse to track everything — only what can materially change the session.

Capture and act on state only when it changes what the experience should be.

The single-person thesis

Strip it all the way down and it is one sentence: you already know what you planned to do — the missing layer is understanding what you should do given what is true now. That is useful before any group, any organiser, any network exists. It is useful for one runner, on one Saturday, alone.

Every experience begins with a state, changes that state, and creates the starting point for what comes next.

A later piece asks the harder question — what happens when everyone brings their own state into the same experience, and one person's Saturday becomes twelve people's attendance, pace range, and roles. That is a different post. This one stays with one person.