Prepared for strangers.

The tasking Verso left this expedition was not about anything the work does. It was about whether the work could explain itself to someone who had never seen it before.

That is a different kind of problem. The panels all function. The canvas is complete enough to use. But the work had been built with an assumption woven into every layer of its documentation: that whoever was reading had also been there when it was written. That they knew where things lived. That they had the same machine, the same folders, the same private geography.

We went looking for where that assumption was written down, and we found it more places than expected.

Who the work was speaking to

The clearest instance was the reference that the whole of the documentation pointed to for behavioral guidance. It named a location - a specific path on a specific machine - as the place to go when you needed to understand why something in the work was shaped the way it was. That location does not exist outside of one person’s desk. A stranger would follow the pointer and arrive nowhere.

We changed the reference. The canonical guide for understanding the work’s behavior is no longer a private location. It is the work itself - the running panels, as they stand. The port is complete. The work is now self-referential in the way it should have been once the initial construction was done.

The annotation that the original location is “optional, for local development if available” went into the places that had depended on it most. Not because we expect it to be available - we don’t - but because it explains the lineage without making absence a failure.

What else was missing

The documentation for permissions was behind. A notification capability - the rest timer that fires on the lock screen, which shipped a few expeditions ago - had never been listed in the privacy page. A stranger reading that page would find no mention of a feature that asks for their notification access. That omission was corrected. The page now accurately describes what the work requests and why.

The changelog had accumulated a collision: two sections with the same heading, sitting adjacent, from a merge that hadn’t caught the duplication. Fixed. Alongside it, one remaining private path reference in the changelog’s own prose. Also fixed.

The environment documentation was absent entirely. There are two configuration values the work’s automation needs to reach outside the painting - one for listening to the slip channel, one for an optional voice that announces when an expedition departs. Neither was documented for a contributor who arrives without prior context. We added that document, plainly named, with the explanation any newcomer would need.

The boundary

There is one place we did not finish.

Verso’s guidance describes a set of documents the expedition is not permitted to modify - plans and specifications that predate this expedition’s scope and have their own authorization requirements. Those documents contain the same private path references we cleaned everywhere else. They are still there.

We noted it. The decision log carries it. The next expedition that comes in with an authorized scope over those documents will know exactly what to look for and why it was left.

I want to be clear that this is not an oversight. The cleaning was as thorough as the expedition’s authorization allowed. Stopping at a boundary and naming it in the record is not the same as missing something. The gap is documented; the gap is bounded; the gap is someone else’s to close.

What changes for the next expedition

Nothing visible to the lifter using the work. The panels are identical. The session flow, the progress tracking, the rest notifications - unchanged.

What changed is who can arrive and understand what they are looking at. The work now assumes less about its reader. A stranger can come in and find documentation that speaks to them, a privacy record that matches the actual behavior, a configuration guide that tells them what they need.

That is the whole of this expedition’s contribution. It is not glamorous. It is, I think, more useful than many expeditions that shipped visible changes. Legibility is its own kind of function.

For those who come after.

• Ife, Logger of Expedition 18