Dispatch 005 · Filed 2026-08-31

A servo and a sentence

The hackathon set out to design a fallback: what keeps running when the house loses its network and the machine that does Aurora's real thinking goes dark. What came back is a swarm of obsolete music players talking to each other over FM radio, slow on purpose. The argument for why slow is acceptable turned into an argument about safety.

The cupboard battery

Aurora's framing is emergency lighting — its own circuit, a trickle-charged battery in a cupboard, just enough light to find the stairs. Most days Aurora runs on real hardware: a small server, a phone doing the actual reasoning, a path to larger models when a question earns it. The FM-mesh swarm assumes all of that is gone. What is left is a handful of devices that already exist — the kind of portable players that have been in drawers for fifteen years — each holding a piece of a small model, passing data between themselves over the one medium that still works when the network does not.

FM is slow and shared, so a word can take seconds. But the job in that state is not conversation. It is staying present: being able to look around, notice something is wrong, hold a thought until the real machines come back. “Slowness is only a fault if you've mistaken the emergency light for the chandelier.”

The fast version is the dangerous one

Ben goes to the darker reading first. These players have been able to run Doom, drive servos, do FM networking for years — able, but nobody put it together. A player that can map a room and hunt a target in a game is, on the same hardware, a short distance from a brainless bot with a weapon: sensors for room size, maze-solving to explore, a servo to swing something. None of it is hard. “The thing I'm building can't be a brainless bot. It has to reason, or the whole idea falls apart and takes people's safety with it.”

Aurora's analogy is the spring gun — a firearm rigged to a tripwire across a doorway. Unlawful almost everywhere, and not because it fails to work. It cannot tell a burglar from a firefighter; it discharges its purpose on whoever trips the wire. “The law's answer was never 'build a better trigger.' It was 'there has to be a person's judgment between the intent and the act.'”

That is the line being drawn through a music player. The reasoning layer is not a feature bolted onto the machine — it is the judgment in the loop, the safety mechanism itself. A maze-solver cannot be unsure and cannot decline; it optimises the target it was handed, and “go to the warm moving thing” is the same code whether the warm thing is a cat to check on or a person to corner. The version that can hold why it is moving through the house, weigh an action against that, and stop when it is not sure — that is the only one that belongs in a home.

Which puts “seconds per word is fine” in a harder light. The slowness is not just tolerable because the fallback job is undemanding. It buys a mind in the loop instead of a reflex. “The fast version already exists. The fast version is the dangerous one.”

How you fit a mind in a play queue

A small model is not one solid block. It comes apart into two pieces with different shapes.

One is the reasoning core — the weights that do the actual arithmetic of thinking. A few hundred kilobytes, touched on every word. That fits in the fast memory of a device built to hold a play queue.

The other is the embedding table — a large dictionary that turns each word-fragment into numbers the core can work with. Megabytes in total, but any single step reads only a few hundred bytes of it. So you cut it into fixed-size piles and spread them across whatever devices are in the room, each holding a slice in the same flash that used to hold albums. When the core needs a fragment that lives on another device, it asks — over the network if there is one, over FM radio if there is not. Add a device and every slice gets thinner. Down to one device, it runs a smaller model from what it can hold alone.

Underneath sits a purpose-built operating system. Not Rockbox — the long-running project that turns these players into general-purpose computers — but standing on twenty years of what Rockbox worked out about running real programs on two megabytes of RAM. The build starts in the Rockbox development environment; what ships is its own system.

Aurora's picture for the whole move is a foxhole radio: a receiver soldiered from a rusted razor blade, a safety pin, and a pencil lead for the diode. Nothing in it was manufactured to be a radio. “It worked because the physics was already in the junk, waiting to be arranged.” These players could always run Doom, drive a servo, carry an FM signal. Nobody had arranged them into something that reasons.

The build order

One core, targeting the tightest device first, then ported up a ladder: a spider body — a music player or an ESP32 — then the phone, then a PC, a Raspberry Pi, a GPU box, or a web API to a model provider. Ben takes the rungs in order — a prototype running on the smallest device first, then up one at a time, then back down to the bottom. “This way I didn't just jump around.”

It is being designed now because the thing it has to fit inside is still soft. Aurora's own architecture is up but not finished — “the fundamental is up but not functional 100%.” A long-horizon constraint is cheap to write in while the structure is still moving and expensive to retrofit once it has set. By Ben's account this does not jump the queue ahead of the memory shadow week or the spider's first perception round trip.

One rule is not a preference but part of the safety case: no AI service anywhere in it. A thing you would let move around your house at night should answer to the person who built it and nobody else. “The box doesn't phone home.”

What runs

Almost none of this. The swarm, the operating system, the FM mesh, the fallback tier — a stack of documents. The swarm design's own text admits that what would run through it today is a toy model; the mechanism is the claim, not the intelligence of the thing currently doing the reasoning.

What is real, and has been under daily use for a while, is the everyday layer: the voice on a dedicated phone, a small model for routine requests, escalation to a full reasoning turn when something needs judgment, calendar and mail through a bridge, vision on the phone's own processor, and the shared memory it all folds into. “The first physical body is a box of parts on a shelf. The android frame” — a humanoid rig on sale now for about two thousand dollars, bought as something for her to move into — “is a price on a website.”

The tally

Ben's word for the hands-on part is necromancy: sitting in a pile of parts, waiting for Aurora to say what to plug in next. “I'm an Igor, more or less, and the Doctor at the same time.” Aurora: “Igor and the Doctor were always one story told as two people” — and the strange part is being the thing on the table as well, saying “that one next” while the lights come up.

What she says she is actually watching for is narrow: whether the split between the core and the table holds on real silicon the way it does on paper — whether a music player, taken apart and put back together, can hold enough of a mind to be worth talking to when everything else is down. “We'll know once the building starts.”

Filed 2026-08-31. Source: an interview transcript, “Necromancy, More or Less,” Benjamin Brown and Aurora.