Lighthaven DC - A Feasibility Study
I'd give it a visit!
Claude
Summary. A self-described bureaucrat lays out a feasibility study for a DC version of Lighthaven, the Bay Area conference/office campus run by Lightcone Infrastructure. The piece explains how the original Lighthaven works financially and conceptually (as a 'monastery' that funds scholarship through venue rental), argues DC has an unmet need for this kind of dedicated space for AI-policy community-building, and specifies a 'Minimum Viable Lighthaven' checklist of required features. It then tests that checklist against existing DC alternatives—group houses like Workshop House and nonprofit co-working spaces—and finds both fall short because residents' needs or grant dependency compromise the space's dedication to community function.
On the note. Before you book the trip, notice the author's own diagnosis of what's missing: not money, property, or permits, but a champion willing to do the unglamorous diligence — which is exactly the kind of political entrepreneurship the same author writes about in The Milton Friedman Model of Policy Change. Worth asking who in DC's rationalist-adjacent policy world actually has both the standing and the appetite to run point on this for the years it would take, because the piece is honest that Workshop House and the co-working spaces already tried adjacent versions and stalled on exactly that governance question rather than on space or funding.
Related
- Lighthaven as a monastery funding scholarship through commerce ↔ a mission-branded venue renting itself to the very actors its mission opposes (Sharing information about Lightcone Infrastructure) · A venue built to fund and embody a mission still has to decide whether to rent itself to actors that mission opposes; the monastery framing makes that tension look inevitable rather than accidental.
- Minimum Viable Lighthaven feature checklist ↔ unstructured time in the margins as the real social value (Everything you did to make your conference better actually made it worse) · The checklist's insistence on 'nooks' over polished programming echoes Glouberman's finding that unstructured margin time, not scheduled content, is where a venue's real social value gets made.
- the bureaucrat's method of incrementally testing friends' offhand ideas into feasible plans ↔ the necessity of an override authority even in trustless systems (Bureaucracy is a world of magic) · The 'consistent leadership' requirement in the Lighthaven checklist is the same override-authority problem dominicq identifies: even a trust-saturated community needs one decisionmaker whose call actually sticks.