03 - Recency isn't authority
Why AI memory needs provenance, not just lifecycle states
(drafted by project agent, edited by hand, by me)
Why we can’t really on Recency
A business’s own documents are not a fixed truth. They pile up. The safety procedure written in January gets revised in March and rewritten in June. The old one doesn’t vanish when the new one lands… it’s still in the drawer, still on the server, still perfectly readable. All three are real. All three were correct on the day they were written.
Feed that drawer to an AI and you’ve handed it a problem no amount of better retrieval solves. Everyone’s trying to fix memory by improving the fetch; better RAG, better embeddings, bigger context windows. But when three versions of the same procedure all legitimately match the question, retrieval isn’t the bottleneck. Retrieval does its job perfectly, it hands you all three. Now what?
Why Provenance is necessary
The tempting answer is recency. Take the newest one. It’s clean, it’s cheap, and it’s wrong often enough to hurt. The newest document isn’t automatically the governing one. A later draft isn’t a ratified policy. A memo that mentions the procedure doesn’t replace it. An addendum changes one clause, not the whole document. “Most recent” is a guess that fails where the stakes are highest, the moment the answer actually depends on which version rules.
Lifecycle states are a real step up from a flat pile. Marking a memory Current, Superseded, or Stale beats treating everything as equally true forever. But states only move the question, they don’t answer it. Superseded by what? Current on whose authority? A label with nothing underneath it is just a guess wearing a badge. You’ve renamed the problem, not solved it.
Applying to AI
None of this is new, either. Anyone who’s built a data warehouse has seen it. Bi-temporal modeling and slowly-changing dimensions solved the shape of this decades ago, and event sourcing keeps the history searchable. What’s new is needing it one layer up, in the memory an AI reads from and answers out of. Old discipline, less forgiving place.
The part that actually does the work is provenance. Every piece of knowledge the system holds has to carry where it came from; the source, its standing, how it relates to the others… and there has to be a rule for which source wins when they conflict. Do that, and “current” stops meaning “latest” and starts meaning “authoritative.” That’s the whole difference between a memory system and a confident guess.
Where Provenance isn’t enough
And where provenance runs out, where two documents genuinely conflict and no rule resolves it, the honest move is the same one the rest of the box already makes. Don’t pick the winner and hope. Surface both, cited with provenance attached, and hand the call to the person whose call it actually is. A system that says “these two conflict, and here’s where each came from… you decide” is worth more than one that confidently quotes last year’s policy because it happened to sort first.
There’s an ownership point buried in here too. A memory you can’t trace isn’t really yours… it’s a pile you’re trusting on faith. Knowing where each thing came from, and who says it’s still true, is part of what it means to own your data instead of renting a vendor’s black box that remembers whatever it remembers. It’s how humanity has always ascertained ground truth.
Recency isn’t authority. Provenance is. Everything else is a nicer label on the same guess.