Perspectives
Memory Through a Systems Architect's Eyes
Storage language usefully separates encoding, persistence and retrieval, but memory looks more like changing distributed state than a static record at one…
I approach memory with an occupational habit: I want to draw boxes and arrows. That habit is useful because architecture forces questions about state, boundaries, interfaces, resources and failure. It is dangerous because natural systems were not designed to respect our diagrams.
Biological memory involves changes across synapses, circuits, gene expression and systems-level interactions. Retrieval can alter memory, and habits, skills, facts and autobiographical memories rely on partly different mechanisms.
Where does state live?
Biological memory involves changes across synapses, circuits, gene expression and systems-level interactions. Retrieval can alter memory, and habits, skills, facts and autobiographical memories rely on partly different mechanisms.
Software gives us the expectation that important state should have an owner. Natural systems often distribute state across structure, concentrations, relationships and history. A snapshot can therefore tell us less than the process that produced it.
Where are the interfaces?
Storage language usefully separates encoding, persistence and retrieval, but memory looks more like changing distributed state than a static record at one address.
Engineered interfaces are declarations. Natural boundaries are often material: membranes, tissues, ecological borders, channels, gradients or social conventions. They can leak, adapt and participate in the behavior they constrain.
What is the failure model?
Databases aim to return the same record. Human memory often generalizes, compresses and reconstructs; perfect bit-for-bit recall is not its operating criterion.
Failure analysis is useful because normal operation hides assumptions. A healthy component can coexist with an unhealthy whole. A local optimization can damage the larger system. Robustness at one level can create fragility at another.
History is part of the architecture
Experimental psychology made memory measurable, while neuroscience linked learning to changes in cells and circuits.
In a designed system, legacy structure may be accidental baggage. In an evolved or historically accumulated system, legacy structure can be the reason the current architecture exists at all. The path is not documentation around the system; sometimes it is part of the system.
The zoom test
A good architectural description should survive zooming. Going down a level should reveal mechanisms capable of implementing the higher-level pattern. Going up should reveal regularities that justify discussing the larger entity in its own vocabulary.
Memory is central to personal identity even though memory is incomplete and reconstructive.
If memory can change when we retrieve it, what exactly persists when we say we are the same person?
Reading trail
These links are starting points for the scientific and historical ideas. The systems interpretation, analogies and conclusions here are my own.