Building and running an inclusive algorave night

Sooner or later, every live coder wants to put on a night: a small dark room, a sound system that can carry sub-bass, projected code glowing on the wall, and a crowd dancing to algorithms. This module turns that ambition into an organiser’s craft. The whole task is not “play a gig” but “design an event” — and because “Algorave” is a freely usable name that carries community norms rather than a licence, hosting one means inheriting a value system you must be able to enact and defend.

Start supported: draft just the technical setup sheet, leaning on the minimal-venue specification (full-range speakers, high-contrast projector, dark standing room — no rows of seats) and on the story of code projection as an accessibility channel for deaf audience members, which reframes the projector from decoration to access infrastructure. Next, draft the social layer with the safe-space code-of-conduct procedure as a JIT pointer, adapting it with the domain-specific failure modes a live-coding community actually names — tool tribalism, mansplaining, non-consensual filming. Finally, work unsupported toward the full run-book, adding a flat, diverse billing policy and the rationale section.

The required atoms gate that capstone directly: you cannot write the setup sheet without the venue spec, the conduct document without the two code-of-conduct atoms, the lineup policy without the no-headliner and diversity principles, or the rationale without the visible-process rule, the TOPLAP transparency ethic behind it, and the free-culture caution about sponsorship capture. The supporting atoms enrich your defence — the guidelines’ documented critique, the history of women’s structural exclusion, and the decentralised city-scene model that your night will join.