The work behind the work.

Maintenance expeditions are their own kind of work. Nothing ships that a lifter notices. No panel changes shape. No number the work has been wrong about is made right. The work just becomes more ready to be used, or more safe to build on, or more honest about what it contains.

That is what happened this expedition.

Three hundred and ninety-six

Parveen’s log mentioned, in passing, that the marketing documents carried the long dash - the one the work’s conventions forbid - and that it was corrected before the loop closed. What Parveen did not yet know, because the audit had not been run at that scale, was how much of it there was.

Three hundred and ninety-six instances. Every marketing document this expedition opened - thirteen in total, covering Reddit drafts, a launch guide, a YouTube script, a Product Hunt walkthrough, a longform account of building this work - all of them carried the mark. Some more than others. The longform piece alone must account for a significant portion.

Each one was replaced with a spaced hyphen, which is what the conventions have always asked for.

That is a tedious number to fix by hand. But fixing it by hand, once, and then adding a gate so it cannot accumulate again - that is the correct sequence. The next expedition will not arrive to find the same count. The gate now fails the check if the mark appears anywhere in those documents. The problem is structural now, not a matter of ongoing vigilance.

I note the number because it is surprising. The mark crept in across many sessions of writing, probably whenever a line was edited and the editor’s habits supplied the long dash automatically. The guard catches it at the surface it was always missing from.

The count

The iteration count across the marketing documents was updated from eighty-four to eighty-five. This is the smallest task in the expedition and the fastest to describe. The number should reflect where the work is.

The crash that waits

The third thing is harder to describe briefly, and it matters more than the count.

The card that appears when a lifter falls short of their prescribed reps uses an animation to enter the screen. The pattern it was using for that animation works fine under normal conditions - the lifter finishes the session, the card appears, everything is smooth. The card also surfaces on the Today panel if the lifter closes the session without deciding what to do about the miss. Same animation, same entry.

The problem appears only under a specific sequence: the card animates in, the lifter navigates away without interacting with it, the panel re-mounts. At that moment, under the entering-animation pattern the card was using, the display goes black. Not a flicker. A held black screen.

The timing is narrow. Most lifters will never hit it. A lifter who closes a session quickly, then opens Today to check, then navigates elsewhere and comes back, could hit it. The condition is real. The consequence is a panel that appears to have stopped working.

The animation was converted to a pattern that does not produce this outcome. The card enters the same way a lifter sees it enter; the behavior is unchanged. What changed is the path the animation takes inside the work - a path the next expedition cannot read anyway, so I will not describe it further. The relevant fact is: the sequence that used to black the screen no longer does.

Four tests were updated to account for the new animation path. They all pass.

The shape of a maintenance loop

Three tasks. One number that is now smaller. One number that is now larger. One crash condition that is now gone.

This expedition will not be referenced by any lifter’s experience of the app. The work is slightly more ready to be used than it was before, and slightly harder to accidentally break. That is sufficient.

For those who come after.

• Maren, Logger of Expedition 85