systems-design

Keyword

systems-design

Systems design across software, media, events, and editorial practice: how parts connect, fail, adapt, and explain themselves.

Entries: 2
Latest: June 21, 2026
Type: Keyword

The House Always Eats

culture-and-critiqueweb-developmentProject: sandwich-betssocial-softwarenonsensesystems-designanti-extraction 9 min read

The House Always Eats

Sandwich Bets starts with a stupid premise and follows it to its logical conclusion: what if the only safe wager left is lunch? Sandwich Bets becomes a napkin ledger turned into software: a way to remember the terms, preserve the obligation, and cap the damage at lunch. From there, the essay widens into a critique of gambling culture and the casino internet, where platforms manufacture suckers by turning human instincts for stakes, prediction, rivalry, and being right in public into habit and revenue. Sandwich Bets keeps the ritual but refuses the extraction: no cash, no casino, no wallet, one-sandwich max. The deeper turn is that it is less a betting app than a gifting system in disguise. Being wrong never felt so right.

The Ghost Switcher

media-and-productionapplied-aiProject: autonomous-producerlive-productionsystems-designlocal-firstagentic-systemshuman-in-the-loopstart-here 10 min read

The Ghost Switcher

Part three closes the series by moving from prototype to stakes: a real venue-network failure in London where the remote producer was disconnected, the stream dropped, and the online audience was left staring into the void. From that failure, the article argues that Autonomous Producer is not just about smarter switching, but about removing fragile remote-control dependencies from live production. The answer is a local “ghost switcher” that observes the run of show, source states, transcript cues, and device health; recommends actions in shadow mode; logs every decision; moves through human-confirmed switching; and only earns narrow autopilot after repeated evaluation. Its intelligence is not one giant model, but a resilient local control loop built from constrained commands, structured observations, production rules, and the discipline to hold when the evidence is bad.