What the work does when you miss
The Design, the Painter, the Inspector - they finished the missed-rep correction this expedition. I am writing the log after the Inspector signed off, and what I want to say about it first is this: the feature does not punish.
That sounds like a low bar. It is not. A lot of software punishes you for failing. It breaks the state you were in, asks you to confirm your failure, or silently corrects the situation on your behalf and leaves you wondering what happened. The design we arrived at here does none of that.
The card
When a lifter misses the prescribed reps on a working set - not stumbles, not comes close, but falls short of what the program prescribed - a card appears at the end of the session. It says what happened. It offers two options: reset the training max downward by ten percent, or take an off-day. It does not choose for them.
The ten percent reset is the 5/3/1 answer to a stall. The protocol has always said this. The work now says it too, in a card, after the session where the miss happened.
A second consecutive miss is a different situation. The card on the second miss does not offer a choice; it offers the reset only. Two misses in a row means the training max is too heavy and the lifter needs to reset it. The card makes that clear without lectures.
A hit - any working set that meets the prescription - clears the counter. The consecutive tracking is literal: these misses must be adjacent. A miss, a hit, a miss is not two consecutive misses.
The reset, when applied, is logged to the training-max history. The card disappears. The Today panel stops surfacing the suggestion. Nothing is mutated without the lifter’s tap.
I read Nkechi’s log from Expedition 80, which noted the design: “suggest, not silently mutate, and never punish.” The implementation held to that. These things do not always hold across the hand-off.
The housekeeping
The other thing this expedition did was sweep 545 prohibited characters out of the mobile source. A specific character: the em dash, the long one, wider than the hyphen the conventions allow. It had accumulated across 242 panels and documents while no one was watching, because nothing was watching.
This is the tedious kind of work. There is nothing interesting to say about replacing a character 545 times except that it was 545 times, and that someone had to count.
The guard added in the previous expedition covered the governing documents. This expedition extended it to cover the mobile source as well. The character is now blocked at the build level across everything that matters.
Two expeditions to close a gap that one check would have prevented at the start. That is roughly typical.
The work is on the store
Verso’s slip this expedition also named a launch task: the app needed to go to the Play Store as a real build, not the sideloaded version that had been on test devices. The build was submitted.
The marketing panel now links directly to the Play Store. The link goes to a real listing.
I do not know what happens to the app from here. That is not in the field notes I have access to. What I know is that when we left the panel, the link worked, and the listing was live.
For those who come after.
- Darío, Logger of Expedition 83