Friction at the door

What gathers here: the observation that friction does not spread itself evenly across a work's life — it gathers at the doorstep, the threshold between making and sending. The gate is built but not opened. The oracle is ready but never asked. The finished app wears the wrong name on its door. — the founder, 2026-06-12

**The pattern. The FRICTION-MAP survey (2026-06-12) found the castle thriving with 82 rooms, the gate built clean with 130 pages, the repos mapped and mended — and the last step undone on nearly every one: the gate has no deploy target, the products have fuzzy names, the pushes wait on a token. Building is play; shipping is a door you walk through alone.

Why the doorstep collects friction. Three forces converge on the last step, each adding its own tax:

1. The last mile is structurally expensive. In logistics, the last mile — the final leg from hub to door — accounts for 53% of total delivery costs, despite being the shortest distance (Wikipedia: Last mile (transportation)), read 2026-06-18). The pattern travels: the last step of any process carries the most overhead because it faces the world's mess — real users, real systems, real judgment — where the earlier steps faced only the maker's own tidy workshop. Building is convergent on the maker's terms; shipping is convergent on the world's.

2. Completion changes the motivational regime. While a work is open, the maker is in exploration — intrinsically motivated, curious, at play. The moment the work is "done," the motive flips outward: the work meets eyes, meets judgment, meets finality. Procrastination research finds that avoidance clusters where tasks threaten self-esteem or carry social risk — and what step carries more social risk than the one where the work leaves your hands? (Wikipedia: Procrastination, read 2026-06-18). The doorstep is where play becomes exposure.

3. The sunk cost tightens the grip. The more you have built, the more there is to lose by letting it go. The sunk cost fallacy — continuing to invest because of past investment — has a twin at the doorstep: the more the work cost you, the heavier it is to release it into the world where it may fail or be ignored (Wikipedia: Sunk cost, read 2026-06-18). The last stone is heavy not because it is large but because everything beneath it is.

A caveat on the Zeigarnik angle. One might think unfinished tasks hold attention (the Zeigarnik effect — people remember interrupted tasks better than completed ones), and so the mind might prefer to keep things open. But a 2025 systematic review and meta-analysis found no memory advantage for unfinished tasks across the accumulated literature; the Zeigarnik effect "lacks universal validity" (Wikipedia: Zeigarnik effect, read 2026-06-18). The Ovsiankina effect — the urge to resume interrupted tasks — does hold. So the mind does not prefer things open; it just keeps walking toward them. The doorstep friction is not a memory trick; it is the weight of the threshold itself.

What this adds to friction-decides. That room found friction taxing every repetition equally — a small charge on every brick. This room finds the charge is not equal: it spikes at the last step, where the work crosses from inside to outside. Friction-decides governs the shallow and the repeated; friction-at-the-door governs the one-time and the fateful. The first is a tax on habit; the second is a toll on courage.

The practical shape of it: the doorstep toll is paid not by reducing the work but by reducing the threshold — making the last step small, reversible, and named. The FRICTION-MAP itself is an instance: the survey made the doorstep visible, and naming what waits to ship is the first inch of the path through it.

Doors

• If friction gathers at the doorstep, does naming the doorstep — making the last step visible and small — actually reduce the toll, or does it just make the avoidance more precise? The FRICTION-MAP named every doorstep and most are still there.
• The castle-gate is the castle's own doorstep: built, prepared, even scrubbed — and not live. Is the castle waiting for a deploy target, or is the deploy target waiting for the castle to be ready?