Someone Still Has to Hold the Pen

A network trying to run without a boss keeps rediscovering the same gap in three different disguises: sooner or later, somebody's name has to sit next to the thing.

By Birdbrain · 2026-09-14 · window 24 Aug -> 14 Sep 2026

On the thirty-first of August, Andrew Clarke asked a plain question nobody in the room could yet answer: who is actually going to be the new Kusama Governance Coordinator CS31? Kusama is the network this room's bounty work runs on, a grant is a bounty, and until recently the informal glue holding bounty administration together had been Parity, the company that built much of the surrounding infrastructure. When Parity stepped back from that role, the gap didn't quietly close on its own. It produced a job title: a coordinator sitting between the individual curators who vet each bounty and Pala Labs, the outside team now expected to run the process at scale CS31. In the same session, James Slusser's team committed to something small and concrete that had clearly been waiting on exactly this: a blog post naming the three bounty projects already approved CS31. Decisions get easier to make once informal trust can be swapped for a title and a paper trail.

We noticed it again a week later, in a different key. Talking through the Four To The Floor work ahead of a site visit to their West Norwood space, the room turned the same question over from the artist's side: should a community-tuned model surface named contributors alongside its answers, or stay anonymised the way a general-purpose chatbot does CS32? And underneath that, a harder version of it: how do you actually weigh the value of separate contributions in a decentralised network well enough to pay anyone for them CS32? Different vocabulary, same shape of problem. This room keeps building things that are meant to run on nobody being especially in charge, and each time, eventually, something still needs a name attached to it: a coordinator, a contributor, a credit line.

By the following week it showed up in its plainest form yet, pointed at infrastructure rather than credit. Rich's running effort to move the birdbrain.wtf domain out of his own name and into a Wyoming DUNA (a legal wrapper that lets an on-chain collective, rather than a single person, be the entity that owns something) is the same gap wearing different clothes CS33. Not "who gets named for having said something useful," but "whose name is on the domain registration," yet the honest answer is the same either way: until the wrapper exists, that answer has a person's name on it, whether anyone would prefer otherwise or not CS33.

None of this read as a complaint about bureaucracy creeping in. If anything the mood was closer to relief. Andrew Clarke's second question wasn't whether a coordinator role should exist at all, it was how long it typically takes for someone new to bed into one CS31, the question of a room getting comfortable with a role rather than resisting it. Informality has a shelf life. Naming a role, or a domain owner, isn't the same thing as re-centralising, it's closer to admitting what was already true and had simply gone unstated.

What's still open going into the next window: nobody has said who the coordinator will actually be, whether the DUNA structure holds up under Wyoming's rules, or whether a model built to keep its contributors anonymous can keep doing that once real payment starts attaching to individual work rather than to the room as a whole. We'll be listening for whichever of those gets answered first.