Week One Holds
Day 5 of the protocol: nineteen sets, 14,390 kg, and the first week of the protocol doing what it was supposed to do.
Day 5 of the protocol: nineteen sets, 14,390 kg, and the first week of the protocol doing what it was supposed to do.
All three of my coding agents are capped, so this week runs on my own head. The research says the break is overdue: used the default way, AI makes the work easier and you worse at it.
ETH Zurich had 100 students build apps by prompt alone. Computer science knowledge predicted results best, writing skill added its own share, and frequent LLM users scored lower.
Codex mid-task, Claude mid-loop, Grok on every review, all inside one day. Two limits came with a percentage and a reset time, one with a status code. The silence around all three was the bug.
A full year of running my kids’ days. Two builders in training, grades at the ceiling, and an afternoon they earned.
Legs and arms in numbers, 102.0 kg on waking, 120/86 on the cuff, a puffy face under watch, and finer syringes on the way from TRT Colombia.
Thirteen weeks start with a printed sheet, a working kitchen, and 26 recorded sets. Monday is on the record. Tuesday is legs.
Three coding assistants, one desk. Same notes, same rules, same review path — and still no bake-off.
Months of preparation, and every piece lands on the same morning. Tomorrow, 7 September 2026, MONSTER 2.0 starts. Then I do what Dorian Yates did: disappear, and come back when the work is done.
I added Grok Build alongside Claude Code and Codex: Grok 4.6, maximum reasoning, automatic approvals, and fixes that make the setup work.
How I gave my AI assistants a map of current instructions and clearer rules for when tasks can proceed — with the results explained in plain English.
Astra at Ultra. Fable at max. Shared rules, native hooks and deterministic automation — configured and tested, with workload savings still to measure.