The Cathedral Builders: On Digital Preservation and the Lessons of Stone
We often speak of digital preservation in terms of cold, hard logic: file formats, checksums, and migration paths. We imagine our work as a kind of flawless, automated machinery, a perfect system for the ages. But to find a more profound, more human metaphor for the work we do, we might look not to the server rack, but to the soaring nave of a medieval cathedral. The builders of those stone giants understood something we are only beginning to grasp: that preservation is not a single act of creation, but a covenant passed between generations.
Consider the cathedral itself. Its construction often spanned centuries, far beyond the lifespan of the original architect or the first teams of masons. The initial plans were not rigid blueprints but visions, adaptable frameworks. The builders knew that the techniques, tools, and even the aesthetic tastes of those who came after them would be different. They built not for completion, but for continuation. They left behind not just stone, but a tradition, a set of principles, and a clear, legible structure upon which future artisans could build. This is the first lesson: our digital architectures must be built for adaptation, not for obsolescence. We are not creating perfect, frozen monuments; we are laying a foundation that others must be able to understand, repair, and extend long after our proprietary software has turned to dust.
The second lesson is in the material. Stone weathers. It is worn by rain, scoured by wind, and cracked by frost. The cathedral builders did not see this decay as a failure of their craft, but as an inevitable force to be managed through perpetual, loving maintenance. Gargoyles were replaced, mortar was repointed, and flying buttresses were shored up. This continuous, often thankless labor was the true engine of preservation.
We, too, are battling a kind of weather: bit rot, format obsolescence, and link decay. The notion of a "perfect copy" is as much a fantasy as an uncracked stone in a five-hundred-year-old wall. Our work is not done when the data is saved; it has only just begun. Preservation is active stewardship, a constant vigilance against entropy. It requires the digital equivalent of stonemasons and glaziers—skilled practitioners who can diagnose decay and perform the meticulous work of repair.
Finally, the cathedral was a public record carved in limestone and glass. Its stories were readable to all, from the illiterate peasant to the learned scholar. It stood as an open, accessible ledger of faith, history, and community. Our digital public records must aspire to the same radical readability. They must be built on open standards and formats that ensure not just survival, but comprehension. A dataset locked in a proprietary format is a stained-glass window bricked over; it may still be there, but its story is lost.
The cathedral builders worked with a humility we would do well to emulate. They knew they would never see the final spire, just as we will never see the final use of the data we preserve today. Our task is not to finish the work, but to make it worthy of continuation, to build something so fundamentally sound and clearly crafted that future generations will know how to care for it, and why they should.
Notes & further reading
A few pages I came back to while writing this: