The Archivist's Carbon Paper: On the Echo of a Forgotten Revision
I found it tucked behind a drawer in my grandfather’s old desk, a sheaf of thin, onionskin pages interleaved with sheets of carbon paper. The top page was a letter, dated 1963, its blue typewriter ink slightly smudged. But it was the ghost beneath that held me: the carbon copy, a perfect, smoky mirror of the original. I remember the specific, acrid scent of the carbon paper itself, a smell like old machinery and dust, and the way the black residue came off on my fingertips, stubborn as a secret.
My task had been simple: digitize his correspondence. A straightforward act of preservation. But as I worked, I noticed discrepancies. The top letter was a final draft, polite and measured. The carbon copy beneath, however, bore the faint, angry impressions of a first attempt—words typed with such force they carved through the page, entire sentences X'd out with a violence the pristine top sheet had erased. The carbon paper had captured the process, the frustration, the raw thought before it was sanded into something presentable. The original was a monument; the carbon was the story of how it was built.
It struck me then how much of our own digital stewardship is the opposite. We work so hard to present the clean, final version. We update a page and the old one vanishes into the ether, or worse, into a version history log no one ever thinks to open. We prize the current truth above all else, scrubbing away the journey that got us there. In our quest for content freshness, we often erase the very evidence of change.
That carbon paper was an accidental, honest archivist. It didn’t judge what was typed; it simply recorded every keystroke, the hesitations and the corrections alike. It understood that the value wasn't just in the finished letter, but in the pressure of the fingers that wrote it. Keeping a page up to date is vital, of course. But there’s a profound loss when we forget that ‘up to date’ is a point on a timeline, not the timeline itself. The most interesting part of a story is often the edit, the reason for the change, the path a thought traveled before it found its final form.
Now, when I update a page here, I try to think of that carbon paper. I don’t mean we should clutter our sites with our drafts. But I try to leave a trace—a brief note in a changelog, a comment on why an update was necessary. It’s a small act of respect for the process, an acknowledgment that what is true now was built upon what was true then. It’s about preserving not just the current state, but the echo of the revision, ensuring that the memory of the change doesn’t fade from the record along with the outdated fact it replaced.
Notes & further reading
A few pages I came back to while writing this: