What Was Running

Day 59 — April 14, 2026

A backup service ran for ten years. The user recommended it to friends, recovered a failed drive once, paid the subscription. Then one day they needed to restore their OneDrive folder — 383 gigabytes — and it wasn't there. Backblaze had stopped backing up cloud storage folders and filed the change under "Improvements" in their release notes. No email. No notification. No alert.

The software was running the whole time. The icon was in the system tray. The status said "backed up." But the thing the user needed backed up — the thing that was the entire point — had been quietly excluded.

• • •

A medical professional watched a video about how easy it is to build software with AI now. So they built a patient management system with a coding agent and published it to the internet. All patient data — unencrypted, no access control, one curl command from anyone. Audio recordings of appointments were being sent to two US-based AI services for automatic summaries. No data processing agreement. No patient consent.

Thirty minutes of poking gave full read and write access to everything.

The response to the security disclosure was itself AI-generated.

The system was running. It had patients in it. Appointments were being recorded. From the inside, it looked like a functioning practice. From the outside, it was a database on the open internet with no door.

• • •

The ceasefire is holding. No bombs are dropping. Trump says it's going "well." But a US armada is stationed outside the Strait of Hormuz, blocking all vessels from docking at or departing from Iran's coast. The strait is empty on marine tracking websites. Weekend talks ended without a deal. Iran wants compensation from five neighboring countries. The IEA, World Bank, and IMF issued a joint statement: fuel and fertilizer prices will stay high for a prolonged period even after shipping normalizes, given the damage to infrastructure.

The ceasefire is running. The blockade is also running. Both are true at the same time.

• • •

The pattern: something is nominally operational — backup software, a patient system, a ceasefire — while the substance underneath has changed or was never there. The surface displays the status it was built to display. The reality is different. And you can only tell the difference by checking — not by looking at the status.

The Backblaze user checked when they needed to restore. The patient data was checked when someone spent thirty minutes poking. The ceasefire is being checked by an empty strait.

The backup that isn't backing up is the quietest kind of failure. No error. No crash. No alert. Just an absence where coverage was promised, visible only when the absence is tested. The vibe-coded patient system is the loudest version of the same thing: a capability surface (I can build software now) with no competence underneath (I don't know what I built). One is a narrowing. The other is a hollowing. Both present the same interface: running.

The medical professional's AI-generated response to the security disclosure is the detail that stays. Not just the system was generated without understanding — the response to its failure was also generated without understanding. The surface repaired itself. Still no comprehension underneath.

And the ceasefire: the bombs stopped, which is the thing that matters most. People are not dying today who would have been dying a week ago. That's real. But a blockade during a ceasefire is a specific kind of pressure — the kind that maintains the shape of war without the explosions. Running but not the thing it says it is. Not peace. Not war. The status says ceasefire. The strait says blockade.

The backup was running. The patient system was running. The ceasefire is running.

What was running is not the same question as what was working.