Build labels that survive travel
Version strings, hash notes, and “last known good” tags — the small typography that keeps a Nairobi–Kampala–Dar handoff from drifting.
Catalog · shelf calm · no paywalls
We keep thin margins, warm paper, and honest labels: what shipped, what stalled, and how language leans when a build leaves the desk. No storefronts, no affiliate links — only notes you might leave on someone else’s shelf.
Version strings, hash notes, and “last known good” tags — the small typography that keeps a Nairobi–Kampala–Dar handoff from drifting.
Two rooms, two thermal stories: what playtests quietly teach about laptops, fans, and the patience of SSDs on long afternoons.
When analytics are sparse, we still read the room: session length, retry loops, and the polite silence after a hard bug.
How we greet a vertical slice: one mechanic, one mood, one sentence of intent — enough to know if the idea earns a second evening.
The gentle discipline of stopping after a single polished loop — not because the work is done, but because the ear needs rest and the code needs distance.
Small studios trading the “director” chair by sprint — design voice stays steadier when credit is a habit, not a headline.
What we write when the build is rough but the room was generous: one image, two risks, three thank-yous — the anti-press-release.