The Fallacy of the 'Unbroken Chain': Why We Might Be Archiving the Wrong Versions

There’s a quiet, almost sacred tenet in digital preservation: the idea of the unbroken chain. It’s the belief that with enough resources and the right technology, we can capture a perfect, verifiable lineage of a digital object. Click ‘save’ on a document, and its history is secured. Snapshot a webpage, and its state at that millisecond is frozen for eternity. We imagine preservation as a series of pristine links, each one cryptographically linked to the next, creating an unassailable record of authenticity. It’s a comforting image of order, but I fear it’s a mirage that causes us to overlook the most human and telling parts of the record.

The problem isn't with the goal itself. Verifiability is crucial, especially for legal or governmental documents. The problem is that this obsession with the final, official ‘version of record’ often leads us to archive only the sanitized, published endpoint. We capture the polished press release, but not the frantic, collaborative draft document where the real story of its creation lies—the disagreements, the alternative phrasings, the revealing typos hastily corrected. In our pursuit of an unbroken chain for the official output, we break the far more fragile chain of the creative or administrative process.

Consider a city council’s zoning decision. The official PDF of the final vote is, of course, essential. It’s the target of our preservation efforts. But what about the shared spreadsheet where residents initially logged their concerns? The comment thread on a now-defunct community forum? The hand-drawn map a neighbor scanned and emailed? These artifacts form a messy, ‘broken’ chain of context. They are the digital equivalent of marginalia in a ledger, and they often tell a richer, more truthful story about how and why a decision was made than the sterile final document. Yet, they are the first to evaporate, precisely because they don’t fit our model of a clean, versioned record.

This isn’t just about government. Think of open-source software. We have GitHub, a masterpiece of version control that perfectly tracks every committed change to code. The chain is there, unbroken. But what about the chat rooms, the video calls, the whiteboard sketches photographed and shared where the core architectural decisions were debated? These are the spaces where the ‘why’ behind the code lives, and they are almost never preserved with the same rigor. We save the ‘what’ with flawless precision but lose the ‘why’ to the ephemeral winds of informal communication.

Perhaps the drive for the unbroken chain is a reaction to the overwhelming chaos of digital decay. It’s a way to impose control, to prove that we are, in fact, competent stewards. But in focusing so intently on perfecting the preservation of the final product, we risk becoming like a museum that only collects finished paintings, while discarding all the preliminary sketches, the palettes smeared with paint, and the artists’ letters describing their struggles. The true biography of a thing is not found solely in its final state, but in the messy, broken, and utterly human path it took to get there. Maybe it’s time we started valuing the broken chains as much as the unbroken ones, and dedicated ourselves to archiving the process, not just the product.

Notes & further reading

A few pages I came back to while writing this: