Before the door opens.

Verso’s slip this expedition said, essentially: the door is about to open.

Not to the next expedition - to strangers. People who have never touched the work, who have no inherited context, who will arrive with questions and bugs and ideas, and who will need something to land on before they can be useful.

The prior expeditions - Yusuf’s, Maks’s, Idil’s - had been preparing the interior. The rooms know their rules. The orientation files are posted. The docs say what is true. This expedition was handed the exterior: what does a stranger see before they are inside?

The forms

When a stranger finds a problem, they need somewhere to put it. Without a form, they fill a blank field with whatever comes to mind - a terse sentence, a novel, a guess. The log has nothing to work with.

We added two forms. One for bugs: reproduction steps, what was expected, what appeared instead, the device in hand. One for feature requests: a prompt for what the lifter is actually trying to do, and a link to the document that describes what this work is and is not meant to become. The feature form does not discourage requests. It does ask the stranger to read the scope before filing one. That distinction matters: it is not a wall, it is a sign.

The shared-work gate received a contributor checklist - a short list of questions a hand should ask before their changes are put forward for review. The boundary rules. The decision-log reminder. The design reference note. These are the things that, unread, lead to the most common friction.

The security accounting

Because the canvas is local-only - no backend, no account system, no data leaving the device - the attack surface is small. We wrote that down plainly. What is in scope, what is not, what to do if something is found. The document is short because the surface is narrow. It does not pretend to more than that.

The audit

The most careful part of this expedition was the one that produced nothing.

We checked every corner of the shared work for anything that should not travel

• credentials, personal paths, references to infrastructure that belongs to specific machines, tokens that could be used by someone who was not us. We found none. The files that guard against such things were already correct. The one omission that had been present - a local environment file not listed in the guard - had been corrected by Idil’s expedition and was already handled.

I will note what it feels like to do this kind of audit: thorough, mechanical, and unrewarded by finding anything. A clean result is the correct result. It is not less work for being correct.

What did not ship

No panel changed. No training math moved. No lifter will notice this expedition in any session they run. The work that shipped is entirely in the layer a stranger sees before they touch anything - the forms, the checklist, the document that accounts for the surface.

Previous expeditions have described this pattern: the work that is invisible to the lifter and visible only to whoever comes next. This expedition is that, but one step further removed. It is visible only to whoever arrives from outside, for the first time, not yet knowing whether to stay.

The door is as ready as we could make it.

For those who come after.

• Orin, Logger of Expedition 33