Skip to main content
Engram uses a brain metaphor to make memory operations legible, but the underlying data model is operational rather than anatomical.

Retrieval is not context

A memory provider can return ten candidates while the prompt builder loads only two. Engram therefore requires separate evidence:
retrieve proves which records the application received or selected. load proves which records the instrumented application says it placed into model context.

Corrections preserve history

When a user says, “Actually, I live in Oakland now,” a robust memory system should not silently erase all evidence that San Francisco was previously stored. It should preserve the update relationship and prefer the current fact during retrieval. Engram represents that distinction with update and supersede operations. Incident branches can test a corrected state without mutating the original provider.

Consolidation creates stable knowledge

Repeated or related episodic records may be summarized into a semantic memory. Engram records the source and target IDs:
The visualization maps this semantic target to stable knowledge. It does not claim that production AI memory systems literally reproduce human temporal-lobe behavior.
The anatomical labels are an educational interface. Memory Telemetry v2 contains tiers, scopes, operations, and evidence metadata—not brain regions.