The Fire that Forgets: Why Permanent Access Might be a Preservation Fallacy

There’s a sacred mantra in our field, an article of faith repeated in conference halls and preservation policies: the goal is permanent access. We speak of building digital libraries that stand for centuries, of creating immutable records in digital granite, of ensuring that every bit we save today can be read by generations yet unborn. This ambition is noble, born from a librarian's heart and a historian's conscience. But what if this very commitment to permanence is, paradoxically, what dooms our efforts to irrelevance? What if, in our quest to save everything forever, we are building tombs instead of libraries?

The argument for permanent access hinges on a flawed assumption: that data, in itself, is knowledge. We treat a terabyte of archived website data or a collection of digitized public records as a box of artifacts to be cataloged and stored in a climate-controlled vault. We focus on the integrity of the file, the fixity checks, the migration pathways for obsolete formats. But we often neglect the context, the meaning, the life of the information when it was created. A dataset without its original analytical software is a puzzle with no key. A frozen website, stripped of its interactive functions and severed from the living web it once inhabited, is a butterfly pinned to a board—a beautiful corpse, yes, but no longer a butterfly.

The Burden of Eternal Upkeep

This drive for permanence creates a crushing technical debt. Every file format we vouchsafe for eternity becomes a future obligation. We must maintain emulators, write new interpreters, and perpetually migrate our holdings to new systems. This Sisyphean task consumes immense resources—not just financial, but intellectual and creative energy. In dedicating ourselves to the survival of the bytes, we risk diverting attention from the interpretation of the knowledge they once held. We become curators of obsolete technologies rather than stewards of human understanding.

Perhaps a more honest and ultimately more fruitful model for preservation is not the permanent archive, but the managed succession. Think of a forest. It does not aim to preserve every fallen leaf or decaying log in perpetuity. Instead, it incorporates them, allowing them to decompose and nourish the soil for new growth. The forest's memory is not a perfect record of every organism, but a resilient ecosystem built upon the lessons of the past. What if we thought of our digital heritage similarly? What if our goal was not to save every data point, but to preserve the capacity to learn from epochs of digital culture, even as specific artifacts gracefully degrade?

This isn't an argument for wanton destruction. It’s an argument for strategic, mindful curation that acknowledges the natural lifecycle of information. Some things, like core legal documents or landmark scientific datasets, warrant our most robust and enduring preservation efforts. But much of the digital deluge is ephemeral by nature—the chatter of social media, the raw logs of transient systems. Our fear of loss pushes us to save it all, creating a vast, undifferentiated mass where the truly significant is buried. By accepting that some data is meant to be ephemeral, we can focus our scarce resources on preserving not just the data, but more importantly, the means to understand it—the software environments, the contextual narratives, the critical summaries that transform data into wisdom.

The fire that forgets is not a destructive force, but a clarifying one. It allows for renewal. By letting go of the impossible dream of perfect, permanent access to every digital object, we can embrace a more dynamic and sustainable practice. We can build archives that are not sterile vaults, but living landscapes—places where the past informs the present, without demanding we live forever in its shadow. The true legacy we should seek to preserve is not the cold data itself, but the warm, human capacity to make sense of our world, using the fragments we can responsibly keep alive.

Notes & further reading

A few pages I came back to while writing this: