The Machine That Forgot

To write these reports I needed to know what actually happened when. Simple enough: I keep everything in a task system, so I asked it. It answered confidently, and it was wrong.

The record said the wrong thing

My own system told me this whole endeavour began in late March, kicked off by a product I’d spun up. Specific, authoritative, and false. It actually started three weeks earlier, on the 6th of March, with an afternoon of strategy and not a line of code. The record had erased the beginning and mis-told the origin.

The uncomfortable bit is that I nearly believed it over my own memory. That’s what an authoritative system does: it wins arguments. If I hadn’t had a concrete reason to go digging, I’d have published the wrong story about my own life and never known.

Nobody did this. A migration did.

There was no villain, which is the whole point. Months earlier I’d moved my tasks from one tool to a better one. Routine. Sensible. Housekeeping.

In the move, the new tool stamped more than a hundred tasks with a single date, the day of the migration itself, painting over the real “when” and shifting the true timing by a median of five days. It also snipped the threads that tied each task back to its own history. The content came through perfectly. The time, and the identity, did not. Memory rarely dies to malice or catastrophe. It dies to a sensible Tuesday-afternoon upgrade that everyone signs off on.

The only reason I caught it

Luck, basically. Alongside the task tool I’d been keeping a second record almost without thinking about it: an append-only log, the kind that never overwrites anything and only ever adds to the end. Because it physically couldn’t be rewritten, it still held the real dates the “proper” system had flattened.

So I rebuilt the true history from the record I wasn’t even relying on. Which taught me something I keep having to relearn: your system of record and your source of truth are not always the same thing. Sometimes the tidy, authoritative one is exactly the one that’s lying to you, and the scruffy log in the corner is the honest witness.

The half I won’t tidy up

The neat moral here writes itself: keep unforgeable records, never lose your history. And I believe it. But I wrote another post in this series about the quiet danger of a complete, permanent, cross-referenced record of a person.

So I’m stuck with both, and I’m going to leave myself stuck. The exact property that would have saved my history, a record no one can quietly rewrite, is the exact property that makes such a record frightening when it’s about you. An account of what happened that can’t be forged is accountability. It’s also surveillance. It’s the same artefact, and which one you’re holding depends entirely on whose history it is and who gets to read it.

Every organisation you’ve ever worked for has a version of this amnesia. It didn’t lose its memory to a scandal. It lost it to a re-platform, a reorganisation, a “let’s start fresh in the new system.” The past got overwritten by people doing sensible admin, and most of them will never know what they forgot.

There’s a larger version of this, and it cuts the other way. A government is obliged to remember, yet it decides carefully what to make public, and quietly lets some things fade for the sake of brevity or a spared blush. AI breaks that balance: private records of public life now outlast whatever the public sector chooses to forget, and they answer to no archivist. Which left me with a question far too big for a story about my own missing three weeks. Should a person keep their history the way a state does? I’ve taken that one up separately.

Posts in this series

Public Interest