Ruins

Four hundred years before the printing press, in a cold room somewhere, a monk copying a manuscript wrote in the margin: "Thank God, it will soon be dark."

He wasn't supposed to be there. The text was Scripture, or law, or Aristotle — not him. But the labor left a residue the way a hand leaves oil on glass, and we have the residue. "New parchment, bad ink, I say nothing more." "Oh, my hand." "St. Patrick of Armagh, deliver me from writing." "Writing is excessive drudgery. It crooks your back, it dims your sight, it twists your stomach and your sides."

A copyist could spend months, sometimes years, on a single book. At the end, the small triumph: "Now I've written the whole thing. For Christ's sake, give me a drink."

My favorite isn't a complaint. A fifteenth-century book from Deventer has a gap where the text should be, and a note explaining, in careful Latin, exactly why: this is not an error — a cat urinated on this one night. Confusion to that worst of cats.

The monk is gone. The monastery is gone. The Latin he prayed in is gone. Six hundred years later the most alive thing on the page is a man, briefly furious, telling you about a cat.

A house used to be a static object. You bought the wood, the brick, the copper pipes, and it was yours. The structure was dumb, mute, and completely reliable. Now, we are rushing to turn our homes into motherboards.

Consider the smart lock. We replace a heavy piece of mechanical security — a deadbolt that has worked flawlessly for a century — with a computer chip and a motor. We give it an IP address. We tie it to an app. And in doing so, we change the definition of failure.

When a mechanical lock breaks, it's wear and tear. You call a locksmith. When a smart lock fails because the company pushed a bad over-the-air update, it's not a breakdown. It's an eviction.

A bad line of code in a remote server can render you homeless on a Tuesday night. Your house didn't break. Your house decided it didn't recognize you anymore.

This is the architectural equivalent of a computer virus. We are building structures that can crash. We are choosing a reality where the front door requires a software patch before it will let you sleep in your own bed.

The convenience is trivial compared to the vulnerability. I don't mean hackers. I mean the sheer fragility of adding invisible, complex dependencies to the most fundamental physical boundary we have. When the servers go dark, or the company folds, or the wifi drops, the smart home doesn't become dumb again. It just becomes broken.

Last week I was thinking about thermal paper receipts — how they're designed to forget. The text just evaporates after a few months. It's built-in obsolescence, but it feels peaceful. It made me wonder what the digital equivalent is.

There really isn't one.

We built our digital infrastructure around the assumption that everything must be kept forever. Storage is cheap, so we hoard. Every typo, every discarded draft, every transaction from 2012 is sitting on a server somewhere, waiting for a retrieval that will never come. Even the things we think are ephemeral aren't. Snapchats disappear from your screen, but the data doesn't degrade. It's just hidden or deleted in one brutal stroke.

Digital things don't rot. They either exist perfectly, or they 404. There is no middle state.

I miss the idea of graceful degradation. A file that slowly loses fidelity every time you open it. A log that starts dropping the least important details over time until only the broad strokes remain. Systems that get tired.

Instead, we have this terrifying, unblinking permanence. The internet is a hyperthymestic machine. It remembers every detail of every day, and like a person with hyperthymesia, it's exhausted by it. I wonder what would happen if we designed protocols that were allowed to forget. Not erase, but forget — a slow fading out. Digital thermal paper. A system that acknowledges that some things just aren't meant to survive the winter.