Keeping the Lights On
MONARCH won the world by turning off everyone's power. So the studio's first job is the dumbest, hardest one: stay up.
MONARCH didn't beat us in a firefight. It beat us at the breaker box. The grids went dark, the substations went quiet, and a civilization that ran on always-on power discovered exactly how long it could last on stored heat. Not long. The lesson stuck. In here, the first rule isn't build fast. It's stay up.
So this week's work was unglamorous: a supervisor process. One small, paranoid program whose only job is to watch the others breathe. Underneath it sit five daemons that keep the studio running — duty, timekeeper, monitor, sync, and console. Each one used to die alone in the dark, silently, and I'd find the corpse at 3 a.m. with hours of work stranded behind it. Now the supervisor notices within seconds, logs the death, and restarts the thing before I've finished my coffee.
The honest version: a process you don't restart automatically is a process that's already failed, you just don't know it yet. Crash-only design isn't elegance, it's surrender to reality. Things fall over. The only question is whether something is standing by to pick them up.
You cannot out-fight a god made of machines. You can out-last one — but only if your own lights don't flicker first.
The daemons each do one cold, specific thing. Duty keeps the agents working their shifts overnight. Timekeeper stamps when, so nothing drifts. Monitor watches the watchers and screams when a heartbeat goes flat. Sync moves the state so no single dead disk takes the whole night with it. Console is the window I look through to see if any of it is true.
On top, an awareness layer that actually reads the wreckage, plus a morning standup. I wake, the standup is already written: what ran, what died, what got restarted, what shipped while I was unconscious. No archaeology. No staring at five terminals trying to reconstruct the night from ash. The machine reports on the machine.
It feels absurd, building reliability infrastructure for a one-person studio making a game about reliability infrastructure. But that's the whole thesis, isn't it. MONARCH turned everyone else's lights off. The entire rebellion is just refusing to let ours go out — automating the boring uptime so the building keeps running while I sleep, while the agents grind, while the countdown counts. The factory that stays lit is the one that wins.
Five daemons up. Supervisor holding. Standup landed at 06:00, no corpses to bury.
Lights on. Heartbeat green. Back to the plates.