The dog was low and thick. That's all anyone registered before it hit her in the park — dense, heavy, moving fast enough to fracture a tibia. Her right one. What followed was the standard aftermath: phone trees, hold music, insurance portals, and claims that went nowhere. The kind of administrative debris that accumulates around an injury is the way silt accumulates around a wreck.
This is a story about that debris. And about what happened when someone decided to do something about it.
For as long as Silicon Valley has been selling a frictionless tomorrow, ordinary people have been its passive shoppers — scrolling the App Store, hoping someone went to the trouble of building whatever they need. Vibe coding changes the equation. In theory. The premise: gesture toward whatever irks you, and a constellation of large language models, code generators, and development environments will click their heels. Zero programming skills required.
The target wasn't a résumé reviewer or an inventory tracker. It was something more specific, more petty — and for that reason, more interesting. The policy world has a word for it: sludge. The rising tide of tiny administrative obligations that increasingly defines modern existence. The steps required to dispute a charge. The phone tree that front-loads fax options for a patient calling to book an appointment. The streaming service you forgot you had. Each one feels like a discrete assault on your time. But they're not discrete. They're separate mushrooms sprouting from the same mycorrhizal network.
Bigger problems attract legislation, journalism, Senate hearings. Smaller ones, too petty to litigate, simply become a fact of life. The arc of history bends toward justice. When it comes to fighting a one-dollar bank fee, it bends toward hold music.
The app began as a description typed into Claude on a Sunday afternoon.
I'd like to create a communally shared app that gathers and shares information related to how much time and energy we devote to fighting burdensome administrative tasks, bureaucratic sludge, Kafka-esque unsubscribe mazes, byzantine insurance portals, wrongful charges, denied claims, confusing membership plans, and the like.
What came back wasn't an error page. It was a real interface — stubbed out, non-functional at first, but there. A "Log Incident" tab. A "Dashboard" tab. The skeleton of something.
The next hours were assembly, not engineering. Ferrying credentials between services. Clicking Deploy. Watching something fail. Pasting the error back to Claude. Repeating. Like following Ikea instructions without knowing what a Flared Mudguard does — but if you follow the directions, the thing gets built.
There were real problems along the way. An API key left exposed in a public repository. User-submitted text being inserted into the page's HTML unsanitized — meaning anyone could submit malicious code as their company name and have it execute in every visitor's browser. Both caught. Both fixed. The experience was akin to building an elaborate Lego creation with a patient, infinitely available collaborator who also happened to know where you'd made every mistake.
The first real submission came from a man who'd spent three hours navigating phone trees to manage his wife's medical care after the injury. His grievance:
Whenever I call to make a doctor's appointment, I have to sit through options that aren't likely choices for patients calling to make an appointment — the very first being information for sending a fax.
Time spent: three hours. Annoyance level: three out of ten. What he'd rather have been doing: gardening.
His submission was rewarded with an Ursula K. Le Guin quote — We live in capitalism. Its power seems inescapable. So did the divine right of kings — and a photo of a dachshund napping beside a stream.
Then the auto-context generator went to work:
Automated phone systems typically front-load options based on call volume data or administrative convenience rather than user intent, which is why fax transmission — likely a legacy option serving a small percentage of callers — sits ahead of the appointment-booking function that probably generates most inbound traffic.
He was, by all accounts, particularly impressed by this conjuring of perspective.
The app went live. Friends submitted complaints about Audible's credit policy, double-billing from Hulu, the login gymnastics required to buy a daughter's prom ticket. One user called it a "grievance dragnet." Another described it as a friend who listens to you cry about your latest breakup, and while you're in the shower she's suggested, quietly builds you a new dating profile designed to avoid everything you just complained about.
Seeing the other entries, she added, was a reminder: it's not you. It's the system.
The internet has been promising to redistribute power for decades, and that promise has mostly served as cover. No janky database built on a Sunday afternoon will claw back our time and agency from the purveyors of sludge.
But the database exists. It is live. It is undeniably there.
Sludge thrives in the dark. It relies on the assumption that our individual wasted hours don't add up to anything. A shared civic ledger — even a janky one — pushes against that assumption. The mushrooms, trembling.
Maybe the menu options really might change.