Open architecture specification for provenance-aware AI systems and institutional memory.
Durable Memory is the layer that decides what an agentic system intentionally preserves beyond a single task.
It is not storage. Storage keeps whatever it is given. Durable Memory keeps only what is authoritative, verified, and worth carrying into future reasoning. A vector database is one possible implementation of Durable Memory. It is not the definition.
Within Sovereign Systems, Durable Memory is defined by the decision it makes at the write boundary, not by the technology that holds the bytes.
The term Durable Memory was first formalized as part of the Sovereign Systems Specification by Ken W. Alger in 2026.
If the context window is the CPU cache of an AI system and Active Working Memory is its RAM, Durable Memory occupies the position of the filesystem. The analogy is useful, and it has one important limit.
A filesystem stores everything written to it. Durable Memory does not. Treating the two as the same thing is the mistake that produces bloated, low-trust memory stores: everything is kept, nothing is curated, and retrieval slowly degrades as the store fills with material that never deserved to survive.
A system that remembers everything eventually remembers nothing particularly well.
The cleanest way to separate the two concepts is to notice that they answer different questions.
Storage answers: can we keep this?
Durable Memory answers: should we keep this?
A filesystem, a database, and an object store all answer the first question. Durable Memory is the layer that answers the second, and that judgment is what makes it memory rather than a warehouse.
Durable Memory is defined at the point where information attempts to cross into long-term retention. That crossing is a decision, not a default.
Information that belongs in Durable Memory can answer questions such as:
Information that cannot answer them remains temporary context and is allowed to expire.
This is why the discipline of the write boundary, Write-Side Custody, matters more to Durable Memory than any retrieval technique applied later.
A memory that cannot explain why it exists is difficult to trust.
For any record it retains, Durable Memory should be able to say who created it, when, under what authority, on what evidence, whether it has changed, and whether it can be verified. Those answers are what separate institutional knowledge from institutional folklore, and they are captured by mechanisms such as the Forensic Receipt.
Information without provenance is just gossip.
Durable Memory tends to hold specifications, user preferences, signed evidence, Architecture Decision Records, policies, verified observations, structured domain knowledge, and significant historical interactions.
It should not accumulate scratch calculations, intermediate reasoning, duplicate information, or ephemeral tool output. Those may have been useful during a task. Usefulness in the moment is not a reason to survive it.
Active Working Memory assembles the state needed for the current task. Durable Memory preserves what should outlive it.
Working memory is the source of candidates for retention. Durable Memory is the layer that decides which of those candidates are worth keeping and refuses the rest.
Sovereign Systems treat Durable Memory as a decision layer by:
The objective is not to preserve everything that might be useful. The objective is to preserve what deserves to be trusted later.
A useful heuristic is:
Storage decides whether information can be kept. Durable Memory decides whether it should be.
Curation is not a limitation on memory. It is what makes memory worth having.