Three of Six
Week one of MONSTER 2.0 closed at three sessions out of six. Day 3 moved 13,432 kg, landing within 377 kg of the leg day and the chest day across completely different muscle groups. And the one set I recorded closest to failure produced the smallest number on the page.
Week one of MONSTER 2.0 closed at three sessions out of six. That is half the programmed sessions, and it does not need a better label than that.
I treated the first week as a ramp rather than as the programme proper, which is a decision rather than an excuse, and worth stating as one. The three sessions covered the whole body: chest, back and abs on Day 1, legs on Day 2, shoulders and arms on Day 3. I was properly rested the entire week. I did not try to force six sessions into a week that had already become a three-session week, which is the usual way a first week turns into badly recovered work and then into an injury.
Three statements are true at once: complete muscular coverage, adequate recovery, and three programmed sessions not done. None cancels the others out, and the third is a shortfall whatever I call the week. Monday is where the six-day rotation actually gets tested.
The programme itself is in MONSTER 2.0 — The Blueprint. This is the third session logged against it.
Day 3 — shoulders and arms
Sunday 9 August 2026. Bodyweight 105 kg.
Those totals come out of the stats script that reads the log files, not out of my head. I have a rule about never hand-computing tonnage into a writeup, because a number typed from memory is a number that quietly drifts.
This was the first dumbbell work of the block, so the loading convention had to become explicit: tonnage counts total load moved, which makes a pair of 22 kg dumbbells 44 kg. It sounds pedantic. It is the difference between a dataset that is comparable in October and one that is not, because the alternative is that some future entry gets logged per hand and nobody remembers which.
Three sessions, three muscle groups, one number that can't tell them apart
Three completely different sessions and the tonnage lands within 377 kg. A 2.8% spread across chest and back, legs, and shoulders and arms.
That is coincidence, not programming, and the useful conclusion is the uncomfortable one. Read only the tonnage column and these three sessions look interchangeable. They were not remotely interchangeable. The leg day got there in 13 sets. This one needed 28.
The number that at least distinguishes them arithmetically is tonnage per set, and the gap is not subtle: the leg session ran at roughly double either upper-body day, and Day 3 holds the block's highest total tonnage and its lowest tonnage per set at the same time. That is a description of how load was distributed, not a claim about how any of it felt. It is still enough to kill the idea that you can judge a session by how many lines it fills in a notebook.
Useful: same exercise, same loading convention, same rep structure, compared against itself over weeks. Then a change in tonnage genuinely means more or less work got done.
Close to useless: comparing across muscle groups or exercise types. It cannot tell you which session was harder, which got the better stimulus, or which produced more fatigue. Here it could not even distinguish a 13-set leg day from a 26-set chest and back day.
The triceps extension out-tonnaged the shoulder press
The two biggest tonnage contributors on Day 3 were not the presses. Overhead cable triceps extension put up 2,400 kg and the rear delt fly 2,340 kg. Both beat the heavy compound that opened the session, which managed 1,408 kg.
That only sounds strange if you are reading tonnage as a measure of effort. It is not one. The arithmetic just favours repetition: the dumbbell press was four sets of eight at 44 kg effective, the rear delt fly three sets of fifteen at 52 kg, the triceps extension four sets of twelve at 50 kg. More reps at a comparable machine load produces a bigger number. That is all it establishes.
It does not establish that a rear delt fly was harder than a set of eight presses at RIR 2. Anyone who has done both knows it wasn't. Tonnage is a volume measure that people habitually read as an effort measure, and Day 3 makes the gap between those two things unusually easy to see, because the largest numbers on the page came from the isolation work.
The exercise that broke the metric
The cable lateral raise first went into my log as "4x-5", which parses to nothing. Four sets, 9 kg and reps in reserve of 1 were all solid; the rep count was not. Worth saying plainly that reps in reserve got recorded on two of eight exercises, so this is the hardest set I have evidence for, not necessarily the hardest set I did. The first pass of this analysis excluded the exercise entirely rather than estimating it. It was 4 × 15, and putting it back is the most instructive thing that happened to this writeup.
Look at what one exercise did to the session's standing. Before the backfill: 24 sets, 282 reps, 12,892 kg, the lowest tonnage of the block. After: 28 sets, 342 reps, 13,432 kg, the highest. One missing rep field flipped the session from worst to best on the number everyone quotes. That is a lesson about data quality rather than about tonnage itself: the arithmetic was never wrong, it was fed an incomplete table. Both failure modes apply here and they are separate. Tonnage does not measure effort, and incomplete logging makes even tonnage unreliable.
That lateral raise was the closest set to failure I actually recorded — reps in reserve of 1, one rep short — and the most reps of any exercise at 60, and it produced the smallest tonnage contribution on the page at 540 kg.
Because the load is 9 kg. Effort, repetitions and tonnage pointed in three different directions on the same exercise. That is the whole case against reading tonnage as effort, in a single row.
The reps-in-reserve coverage is the milder version of the same problem. One of eight exercises on Day 1, zero of six on Day 2, two of eight on Day 3. Direction right, level still bad. The lateral raise is the proof of why it matters: the only reason I can say anything at all about how hard it was is that I happened to record one number that has nothing to do with load. For the other six exercises I have no idea and no way to get one.
Better logging is not retrospective cell-filling. It is fewer empty cells at the time, which costs about four seconds per set, and this session cost me a full re-run of the analysis to recover four of them.
Three sessions, zero cardio
The programmed stair climber was skipped again. Third session running. That is not a footnote in week one, it is the one unambiguous compliance failure of the block so far, and the progression written into the blueprint has not started at all.
I walked to the gym and back, which the wearable logged inside a 150-minute, 7,288-step day. Genuinely active, and beside the point.
None of it moves cardio adherence off zero for three. Walking belongs in the activity record; the skipped ClimbMill belongs in the compliance record. Letting the first pay for the second is exactly how a programme quietly stops being the programme.
Four things week one taught me about measurement
2. An isolation movement can own the biggest number. The triceps extension produced more calculated tonnage than the heavy shoulder press that opened the session. Rep count drove it, not difficulty.
3. One missing rep field reversed a session's ranking. Without the lateral raise, Day 3 was the block's lowest-tonnage session. With it, the highest. Same session, same effort, opposite conclusion, 540 kg of difference.
4. Precision in one field coexists happily with a hole in another. I can state 13,432 kg to the kilogram while reps-in-reserve covers two exercises out of eight. Precision is not completeness, and the number that looks most exact is usually just the one that was easiest to capture.
What changes Monday
Full six-day rotation, starting with Day 4. Week one showed that three rested sessions can cover the whole body. It did not show that I can hold six in a week, because I did not attempt six. That is the actual test starting now.
Cardio has to begin. Three consecutive skips is a pattern rather than an omission, and the fix is not more walking.
And the rep field needs capturing properly the first time. This one was recoverable because it was the same afternoon; a set from three weeks ago would simply be gone.
Week one: three sessions completed, three not. Full body covered, rested throughout, 39,705 kg moved across 67 sets, and a baseline load recorded for every major muscle group. It also exposed the three things that need correcting before the load goes up — six-day compliance, cardio that actually happens, and cleaner effort logging.
Not a bad week. Just not yet the programme.
Meanwhile, elsewhere in the house
It was Sunday, and the rest of the crew were doing Sunday properly. Table games on the terrace, watermelon for the hydration, a movie afterwards. Somebody in this house understands recovery better than I do.
Which is the part the training log never captures. Three sessions, 39,705 kg and a page of tables measure the work. They do not measure the week that made the work possible, and this week the rest was the half I actually got right.
MONSTER 2.0 — The Blueprint — the six-day programme these sessions are logged against.
The Deficit Beat the Peptides — what the bloodwork said about the cut this training sits inside.
The Best Thing in Animal Pak Is the 100 mg They Took Out — reading supplement labels with the same suspicion I read tonnage with.
