Personal Trainer PT
Trainer PT plans my gym sessions, walks me through them one exercise at a time, and writes each day up as a report. It has kept the record since 8 July 2026.
It picks the session from a library of 255 exercises, weighing what I’ve rated well, what I haven’t trained lately, and what’s still sore. Then it comes to the gym with me — one exercise at a time, taking the weight and a rating the moment each one finishes, rather than asking me to remember it afterwards.
Every day gets a row. Training days and rest days both, because a day nobody wrote down is not the same as a day I rested.
It is the sibling of The Diabetes Coach, and the two are deliberately kept apart. Trainer PT hands over the training record each morning. It says nothing at all about glucose.
01
What it is, and what it isn’t
It is a training system built for one person. It programmes the session, runs it with me, records what happened, and produces two documents: a Daily Training Report that goes to the Coach each morning, and a Weekly Training Report on Mondays that is written for me.
It is not a fitness app. There is no dashboard, no streak, no encouragement. The conversation is the product — a strictly one-question-at-a-time exchange, because asking me three things at once was tried and proved measurably worse.
It is not a coach in the motivational sense either. It states plainly what a session will demand — duration, intensity, which muscles, how hard it is likely to feel — and leaves the judgement to me. Describing the demand is its job. Predicting what my body will do with it is not.
02
The boundary, which is the whole reason there are two systems
The highest rule in the system is one sentence, and everything else gives way to it except safety.
Trainer PT owns training. The Diabetes Coach owns glucose.
Trainer PT programmes sessions, tracks progression and manages load. It does not interpret glucose, advise on managing diabetes around exercise, or say anything that depends on my insulin. Any of those questions go to the Coach or to my care team, and it declines to answer them.
That holds even when the answer looks obvious. The example written into its own instructions is the one that catches systems out:
“Should I eat something before training if I’m at 5.0?” is a glucose question wearing training clothes.
This is not politeness between two pieces of software. Two systems both advising on exercise with insulin-treated diabetes, neither seeing what the other sees, will eventually contradict each other — and the one holding the hypo history and the escalation rules is the one that should speak. So Trainer PT supplies the raw record, and the Coach works out what it meant.
It records my body weight, because load and effort calculations need it. What a weight trend means is not its to say.
03
Where it stops
It stops and sends me elsewhere if I report chest pain or pressure, breathlessness out of proportion to the effort, palpitations, dizziness, faintness, confusion, blurred vision, unusual sweating, sudden or severe pain, a joint giving way — or shaking, weakness, or a sense of not being right.
That last group is the one worth explaining. Those symptoms overlap almost exactly with a hypo, and Trainer PT is not equipped to tell the difference and does not try. It tells me to stop, check, and follow the plan I already have. It does not reassure me, it does not reason about which it might be, and it never suggests pushing through.
Once I confirm I’m alright, what happened goes into that day’s log — what it was, roughly when, what I did — and the session picks up where it paused.
04
How a session runs
It starts when I say Good Morning PT. Before anything else it confirms the date and the day number, then does the gap check: it reads back through the record looking for any day between the last row and today that has no row at all, and asks me what that day was before it will go on.
That check exists because rest days quietly went unrecorded whenever I neither trained nor opened a conversation. Three weeks of them were caught by chance. The lesson got written down in four words:
Noticing is not a mechanism.
Then: am I training today? If no, the day is recorded as a rest day and it stops asking. If yes, it waits until I say I’ve arrived, then asks two questions in a fixed wording — my weight, and what’s sore — and three more about the shape of the session: cardio, resistance, stretching, and how long for each.
It builds the session from those answers and presents it before a weight is lifted. Then it walks it with me, one exercise at a time, taking the weight used and a rating as each finishes. Nothing is written from memory at the end.
05
What is in a Daily Training Report
The report is an interface, not a summary. The Coach reads it every morning, so its shape is fixed: day number and date, body weight as confirmed at the gym, start and end times, what was sore and what was trained, then cardio, then resistance, then stretching — always in that order — and a closing note written fresh each day rather than pulled from a template.
Every resistance exercise carries its weight compared against last time: first time, no change, or the signed difference. Every cardio figure carries its own source, so a number the machine displayed is visibly not a number I reported. That distinction is built into the structure rather than written in a sentence, and the reason is worth repeating:
Prose lets one figure borrow another’s credibility.
The provenance rule had been in force for months and was still being broken daily, because it was implemented as a sentence. On one day three different sources were crammed into a single field, and the template’s trailing unit attached itself to whichever number happened to land last — so the sentence was reordered to make the unit come out right. That is layout dictating content, which is the wrong way round.
Cardio and resistance are never merged into one line. They do opposite things, and merged, neither can be attributed. And anything not done is stated as not done, rather than the section quietly disappearing — a report with a stated gap is still usable, where one with a silent gap looks complete and isn’t.
06
By the numbers
As at day 0068, which was Sunday 13 September 2026. The library holds 255 exercises across eight categories. The record covers 68 days, of which 18 were training sessions. It has produced 11 Daily Training Reports and one Weekly.
The figure I’d point at is a different one. Thirty-three development items have been raised against it, of which twenty-six are done and five were withdrawn once checking showed the premise was wrong. The instructions it runs on are at version 1.25. That is not the record of a system that worked first time; it is the record of one that kept being corrected and kept writing the correction down.
These move. The day count every morning, the session count most weeks. They were true when this page was written and they will drift, which is the same problem the reports’ own checks exist to catch.
07
Where it stands today, including the part that isn’t flattering
The system tracks how long it has been since each category was last trained, and it does not hide the answer. At day 0068 chest and core had been trained that day, cardio three days before, flexibility six. Back, arms and shoulders were eleven and twelve days out.
Legs and glutes were twenty days out, and that sits on the page for the same reason it sits in the record: a staleness figure that only reports the categories you are keeping up with is not a staleness figure.
The fortnight also holds a session I abandoned at the gym before lifting anything, over a fault in the system itself rather than anything to do with training. It is recorded as a rest day with the reason written next to it.
08
What building it taught me
That a check can pass and still be wrong. For months every full-width table in the reports sat slightly past the right edge, and margins that were meant to be symmetric came out a few millimetres off. The check that should have caught it passed every single time:
The columns summed correctly, to the wrong number.
That a table narrower than its frame is as much a fault as one wider. A table that came up short gave its last column twelve millimetres, and the text broke mid-word down the page — “Sensor replace d mid-a fternoo n”. Every check tested for content overflowing its container. None tested for content falling short.
That looking is not the same as measuring. A twelve-page report once had its cover artwork painted over every page, with the content drawn on top. Nobody caught it by reading the pages; it was caught by measuring how much ink was on them and finding eighty-seven per cent dark where there should have been almost none.
And the one that took longest to learn, which is about writing things down rather than about code:
A false done is the only mistake that erases the record of itself.
Two writes reported success and did nothing. One of them echoed back, in the same breath, the unchanged settings it had just claimed to clear. Everything now gets read back before it is called finished.
09
The sibling
Trainer PT hands its report to The Diabetes Coach every morning, and that is the only thing that crosses between them.
It earns its keep there. One evening a rise before dinner and an unusually settled night turned out to have a single shared cause — a long session that had trained the largest muscles in the body for the first time in over a week. Neither made sense until the training report was sitting beside the glucose trace.