Culture pages usually describe an aspiration. This one describes a practice — the one currently followed by a team small enough that every rule here is tested daily, and written down so it survives the team getting bigger.
[ 01 ]Writing culture
Writing is how a small team thinks clearly and how a future bigger team inherits the thinking. The specs, the gates, the letters, the releases — the whole company is a set of documents with a product attached.
Decisions are documents
Anything that changes the product, the spend, or a promise gets written down before it happens — context, options, decision, and the gate it answers to. If it was not written, it was not decided.
Specs are argued in the document, not the meeting
Comments beat conference rooms. A spec collects written objections for days before anyone talks about it live, so the loudest voice in the room is the best argument, not the best performer.
Bad news gets the same prose as good news
A miss is documented in the format the win would have used. The retention plateau dipping gets a memo with numbers, not a hallway euphemism.
[ 02 ]Async defaults
Async is the default, sync is the exception
Work moves through written threads that anyone can read tomorrow. Live conversation is reserved for what genuinely needs it: hard trade-offs, bad news, and the occasional unblocking call.
Response windows, not response reflexes
Threads expect answers in hours, not minutes. Nobody is rewarded for being permanently reachable, and deep work hours are not interruptible by default.
One source of truth per question
Every recurring question — what gate is next, what reads are budgeted, what shipped — has exactly one written home. If you had to ask in chat, the document failed and gets fixed.
[ 03 ]Shipping rituals
Ship to the plateau, not the launch tweet
Every feature is argued by lifecycle week: which week of a user's life does this touch, and which failure does it remove? Day-one wow that taxes week-five usage is rejected by default.
The monthly gate review, in writing
Once a month, the actual numbers — retention cohorts, payback, runs per user, ledger balance — go on the page next to the gates they answer to. The review is a document with the numbers in it, not a slide deck about momentum.
Changelog or it did not happen
Everything that ships gets a dated, honest changelog entry, including the regressions. The record is the ritual.
Every feature carries a distribution clause
Each spec answers: what artifact does this produce, and who else sees it? Features that produce nothing a second person ever encounters must justify themselves twice.
[ the shortest version ]
Write it down.
Ship it measured.
Let the gates argue.
[ 04 ]The bar
Would the trust kernel approve of how you work?
Attributable, scoped, inspectable — the standards we hold the runtime to are the standards for the work itself. You should be able to show why you know what you know.
Best in the world at something narrow
The company strategy is the hiring strategy. We want people who have gone embarrassingly deep on something specific, because that is the only kind of advantage we can afford.
Kill your feature test
Everyone here has shipped something they later deleted because the numbers said so. If you have never killed your own work, you have never measured it honestly.
[ 05 ]What we don't do
Meetings theatre
No standing meetings without a written agenda and a decision to make. No status meetings at all — status lives in documents that take two minutes to read.
Growth hacks
No dark patterns, no fake urgency, no notification spam dressed as engagement. If the product cannot pull people back on its own, paid pushes only disguise the disease.
Vanity metrics in any internal document
Cumulative signups, annualized best months, community size — banned indoors. If a number cannot survive the definitions on the investors page, it does not appear in a memo.
Hustle cosplay
No performative hours, no 2 a.m. badge of honor. The work is a long game; we measure output against the gates, and burnout is a trust incident against yourself.
[ 06 ]If this reads like relief
Everything above is checkable in your first week — ask to see the gate reviews, the killed features, and the changelog with the regressions still in it.