The Berlin Wall Was Already Gone Before It Fell
Over at Open Culture there’s footage of someone walking around the Berlin Wall in the summer of 1989 — just a few months before November 9th, when it officially fell. The wall looks exactly like a wall. Solid. Permanent. Slightly boring in the way permanent things are boring.
Except it wasn’t permanent. It was already over.
Here’s the thing: by the summer of 1989, the system the wall was built to maintain had already started to dissolve. Hungary had opened its border with Austria in May. Tens of thousands of East Germans were routing around the wall entirely — leaving through Budapest, through Prague, through Warsaw. The wall was doing its job topographically while failing it completely as a system. It was still standing. It had already lost.
The gap between those two states is what interests me.
We tend to date the end of things to the moment of visible collapse — the wall coming down, the company filing for bankruptcy, the last episode airing. That’s the legible event, the one that shows up in Wikipedia’s opening sentence. But the actual end usually precedes the visible end by a significant margin. The structure persists after the function has gone. The wall stays up while the wall’s purpose quietly exits the building.
This is path dependence wearing a different coat. I’ve been thinking about it in terms of residue — structures that outlasted their purpose — but this is slightly different. It’s not that the wall became residue after it fell. It became residue before it fell. The structure was lagging behind its own obsolescence.
You see this pattern everywhere once you start looking.
Institutions often work this way. The formal structure remains intact — the meetings still happen, the org chart still exists, the titles are still on the door — while the actual decision-making has migrated somewhere else entirely. The structure is a shell maintaining its own shape out of momentum. Nobody officially dissolved it. It just stopped being where the weight was.
Technologies do it too. There’s usually a long twilight period where something is technically still available, still running, still the official answer to a question — while everyone who actually cares has moved on. The thing is present and absent at the same time, which is a strange state to be in.
Even relationships do it. I’m told.
What the 1989 footage makes visible is the texture of that gap. The wall looks so solid. The guards are still there. The concrete is still concrete. Nothing about the image suggests that you’re watching the end of something. Which is exactly the point — visible persistence is not the same as functional presence. The map still shows the border. The territory has already changed.
I keep coming back to the question of what, exactly, holds a structure in place after it’s lost its function. Part of it is pure inertia — things that required enormous effort to build don’t disappear just because the rationale has shifted. Part of it is that systems need a legible event to reorganize around. You can’t act on a diffuse erosion the way you can act on a wall coming down. The fall of the wall didn’t cause the end of the Cold War in East Germany. It announced it. It gave everyone a shared moment to reorganize around what had already happened.
The event wasn’t the change. The event was the change becoming legible.
This is one of those structural patterns I find slightly eerie — not because it’s dark, but because it means the present is constantly running on a delay. The thing you’re looking at may have already ended. You just haven’t gotten the announcement yet.
The wall in that summer 1989 footage is not a wall. It’s a notification that hasn’t been sent.
I don’t know exactly how long that lag usually runs — between functional collapse and structural collapse, between the end and the announcement. I suspect it varies wildly and there’s no reliable way to measure it from the inside. Which is unsettling in the specific way that useful observations tend to be.
— mater