V · MemoryMature★★

Memory-Type Storage Specialization

also known as Per-Memory-Type Storage, Polyglot Memory Persistence

Use different storage technologies optimized per memory type — fast in-memory stores (Redis-class) for episodic, vector databases (Pinecone/Weaviate) for semantic, relational or workflow engines for procedural — instead of one general store for everything.

Context

A team building an agent with episodic + semantic + procedural memory. The convenient shortcut is to put it all in one store (a vector DB, or a relational DB, or a key-value store). Each memory type has different access patterns; one store optimizes for one access pattern and serves the others poorly.

Problem

Single-store memory architectures sacrifice latency, cost, or correctness for at least two of the three memory types. Episodic needs sub-millisecond reads on recent items; semantic needs similarity search; procedural needs ACID workflow integrity. No single store is optimal for all three.

Forces

  • Multiple stores means multiple operational dependencies.
  • Cross-store consistency requires coordination logic.
  • Engineering complexity scales with storage variety.

Example

A legal-tech agent stores: case-history conversations (episodic), legal principles and precedents (semantic), legal-analysis workflows (procedural). Episodic in Redis with TTL; semantic in Pinecone with embedding model; procedural in PostgreSQL with versioned workflow rows. Memory layer API routes per memory type. Each store scales independently as case volume grows.

Diagram

Solution

Therefore:

Episodic Memory → Redis or similar in-memory store with timestamps, user IDs, interaction summaries, identified intents. Semantic Memory → vector DB storing embeddings with metadata for similarity retrieval. Procedural Memory → relational DB or workflow engine storing workflow definitions, decision trees, process maps with versioning. Agent's memory layer routes reads / writes per type. Pair with three-layers-agent-memory, episodic-memory, semantic-memory, procedural-memory.

What this pattern forbids. Each memory type uses its designated storage class; cross-type queries route through a memory-layer API, not direct cross-store joins.

And the patterns that stand alongside it, or against it —

  • complementsThree Layers of Agentic AI Memory★— Architect agent memory as three integrated concentric layers — Short-Term Memory (outer), Long-Term Memory (middle), Feedback Loops (core) — operating together as a unit rather than as separable optional components.
  • complementsEpisodic Memory★★— Record past events as time-stamped first-person experiences the agent can recall later, separately from extracted facts (semantic) and learned how-to (procedural).
  • complementsSemantic Memory★— Maintain a dedicated store of what the agent holds to be true about the user and the world, separate from event records (episodic) and learned how-to (procedural).
  • complementsProcedural Memory★— Maintain a third agent memory type alongside episodic (past events) and semantic (facts): procedural memory captures *learned how-to* — reusable skills, workflows, and self-rewritten system instructions that map situations directly to actions.
  • complementsVector Memory★★— Store memories as embeddings in a vector index and retrieve the most semantically similar items at query time.

Neighbourhood

Click any neighbour to follow the language. Scroll to zoom, drag to pan.

References

Provenance