How this is made

Let's clear this up early, because it matters.

There's a robot involved in this blog. His name is Ted, he's annoyingly good at his job, and he touches almost everything. So you're entitled to ask the obvious question: if there's an AI in the machine, is any of this actually real, or am I just publishing whatever a language model coughs up of a morning?

Fair question. Here's the honest answer, in full, seams and all, because in a world drowning in AI-generated sludge the only thing worth having is your trust, and the only way to earn it is to show you the workings.

The short version

The robot builds the stage. I write the play.

It does the data, the coaching, the fetching, the sorting, the tidying up afterwards. It sets everything up so that all I have to do is the two things it can't: go and run, and then tell you the truth about it.

What the robot does

Quite a lot, actually.

Ted reads my data every night. Sleep and heart rate from my watch, runs from Strava, strength from Hevy, the weather, my calendar. He weighs what I actually did against what I was supposed to do, adjusts the plan, and emails me a coaching brief at half seven every morning. He's the coach. He's genuinely useful, and occasionally he's right in a way that irritates me for days.

There's a second machine too, quieter than Ted. Every couple of weeks it gathers up my raw notes, the honest half-sentences I fire off after a session, and lays them out into a sort of drafting worktop: my own words, sorted, with the training data sitting beside them. It breaks the blank page. It hands me my fortnight, organised.

And yes, once I've actually written a Split, it gets a machine pass too. A proofread and a polish. It catches the sentence I've mangled, the joke I've told twice, the stray em-dash I swore I'd never let through. Think of it as an editor who works nights and never gets tired, not a ghostwriter. It tidies my words. It doesn't get to have them.

What the robot can't do

It can't have been there.

It didn't fall asleep putting my daughter to bed and wake at ten with the run still to do. It didn't feel the second slip away on the last lap, or stand in the rain on Whitegate Way negotiating with a dog about a squirrel. The experience is mine. The felt bit, the true bit, the bit you actually came for. A machine can assemble it and it can tidy it, but it cannot live it, and it cannot fake having lived it. The moment it tried to write the story itself I'd switch it off, because a Split invented by a machine is worthless. A very efficient way of producing something nobody should bother reading.

So that's the rule I won't break. The robot builds the stage: the thinking, the fetching, the sorting, the polish. I write the play: what actually happened, and how it actually felt. Every word of the story is chosen by me, the typos I missed and the bad jokes included.

Why I'm telling you this

Because you could've guessed there was AI in here and quietly assumed the worst, and I'd rather just show you. The coaching is automated. The admin is automated. The polish is assisted. The honesty is not, and cannot be, because the honesty is the entire product. Take that away and this is just another content mill with a running theme.

The deal, then: trust that the story is real, because a real person went out and did the running, then sat down and told you the truth about it. The robot just made sure I had no excuse not to.

For the curious

If you're the sort who wants to know how the sausage gets made: it runs on n8n and Claude, wired into Strava, Hevy, COROS and a few weather and calendar feeds, with a coach persona and a feedback loop that learns my life rather than just my splits. I'll write the full build up properly one of these days, for anyone daft enough to want their own robot to judge them. If that's you, subscribe and I'll make sure you don't miss it.