The Shipbreaker's Principle: Dismantling Digital Monoliths for Preservation

In the shipbreaking yards of Alang, India, and Chittagong, Bangladesh, a strange and brutal form of reverse engineering takes place. Decommissioned supertankers and cargo ships, once singular behemoths of the seas, are meticulously taken apart. Workers don’t wield the tools of creation, but of deconstruction: torches, winches, and sledgehammers. They are not building a single, greater structure; they are breaking a single, complex object into its constituent, reusable parts. This arduous, dangerous process is not just an industry; it is a profound lesson for anyone trying to preserve our digital world.

In digital preservation, we have often been architects, obsessed with building monolithic, perfect containers—the digital equivalent of a fortified vault or an unsinkable ship. We design ever-more complex file formats, create massive, centralized web archives, and build specialized software suites intended to render obsolete formats in pristine condition. We build our own digital supertankers, hoping they will sail the waters of technological change forever. But time and again, we find these very monoliths are the ones most at risk. The software becomes unsupported, the file format is superseded, and the entire, intricate system becomes a ghost ship, adrift and unopenable.

The shipbreaker offers a different, more pragmatic philosophy: What if preservation isn't about maintaining the whole, but about intelligently disassembling it into parts that are easier to salvage? Instead of trying to perfectly freeze a complex digital object—a 1990s multimedia CD-ROM with its custom engine, for instance—we could apply the shipbreaker’s principle. Dismantle it. Extract the raw assets: the text files, the image files, the audio clips, the source code. These are our ‘scrap steel,’ ‘copper wiring,’ and ‘furniture.’ They are simple, standard, and far more likely to be readable by future systems than the intricate, proprietary machine they were once part of.

The Anatomy of a Dismantled Record

This isn’t just for complex digital artifacts. Consider a single, contemporary government PDF. It is, in its own way, a monolith. It bundles text, formatting, embedded fonts, and images into a single, often opaque, file. A preservationist might try to keep the PDF reader software alive. A shipbreaker would ask: what are the essential, reusable parts? The answer might be to automatically extract the plain text and the raw images, preserving them as separate, simple files. The specific layout might be lost, but the core intellectual content—the very reason for preservation—is saved in its most basic, durable form. The ship is broken, but its valuable cargo is secured.

This approach forces a difficult but crucial conversation about what we are *really* trying to save. The shipbreaker knows the paint on the hull is worthless scrap; the engine block is valuable. In our digital world, we must ask: Are we preserving the exact look-and-feel of a 2005 website, or the information it contained? The former is a monumental, perhaps impossible, task. The latter, while still challenging, is made easier by breaking the website down into its core components: the HTML text, the CSS rules (as a separate, readable artifact of design intent), and the images.

Embracing the shipbreaker’s principle is to accept a certain kind of loss. The majestic silhouette of the supertanker will never sail again. But its steel will be reforged into new structures. By learning to break things down, we stop fighting a losing battle to preserve complex, interdependent systems and start building a foundation of simple, rugged, and durable parts. It is a humble, practical form of preservation, less concerned with perfection and more with ensuring that something—the most important something—survives the relentless tide of obsolescence.

Notes & further reading

A few pages I came back to while writing this: