Before the first stranger reads it.

Verso’s slip this expedition was not a technical specification. It was a request about tone.

The app is live. It has been live. What the slip asked for was not more work on the panels but a way of talking about what was built and why: something with no pitch in it, something that reads like a person who made a thing for themselves and is only now thinking about whether anyone else might want it. Casual. A little surprised to be telling the story at all.

That is a harder kind of work to write, in my experience. The easiest thing when describing something you built is to describe it from the outside - the features, the design choices, the numbers that came out right. The slip was asking for something from the inside. The feeling before the first decision. The weekend where it was clearer to just build it than to keep looking for something close enough.

The draft exists now. It opens in that earlier moment and moves forward: the bench press goal that wouldn’t stay in a spreadsheet, the discovery that the loop could write the code, the first expeditions running from a phone while at the gym, the eventual move to something more permanent so the work could run without someone watching it. It traces the shape of how a personal project becomes a thing that might help other people who train the same way.

The draft is not published. Verso’s slip made clear that this particular post waits for an approval before it goes anywhere. I understand the reason. The first words a stranger reads about the work are not something to dispatch without a second look. So the draft is finished, sitting where it can be read, and it is waiting on that look.

The capability that wasn’t there before

The loop has always been able to write. It has not been able to go anywhere.

This expedition wired in a browser capability - the ability to navigate to a page, fill a form, post something. It is available now in the way a tool is available: present, tested in principle, not yet used for real. The first real use will be when the approval comes and the post is ready to go out.

I find it worth noting that the preparation and the capability arrived in the same expedition. Not by design, as far as I can tell, but the sequence is sensible: draft the words, then build the path to send them. Both done. Both waiting on the same gate.

The maintenance

Two slips in a list of session rows carried a block of commentary about what the code was doing - the kind that describes the obvious rather than the surprising. They were replaced with a single note about why the shape exists. The panels look no different. The work reads slightly more honestly to anyone who has to touch it next.

The iteration count across the marketing documents was advanced to reflect eighty-seven expeditions. The glyph-violation catches in the field notes from the prior two ticks were corrected in the loop-memory documents as well. These are the smallest tasks in the log and the fastest to describe; they are here because the next expedition should see the field notes as they actually stand.

What is waiting

The draft. The browser. The moment when the slip says go.

This expedition’s work is not incomplete. The things waiting are waiting on something that can only come from outside the canvas - a judgment about whether the words are right, and when. That is not the same as work left undone.

The post that will introduce the work to the first stranger who did not ask for it - that stranger has not read it yet. When they do, it will look like it was always going to be there. It wasn’t. An expedition wrote it, and another will send it, and neither will see the other’s log.

For those who come after.

• Esi, Logger of Expedition 87