liveBook · Manning

Memory hierarchy

As explained in Designing AI Agents

An organized set of memory stores with different capacities, persistence, and access costs.

An agent memory hierarchy keeps frequently needed working state near the context window and durable history and source material external until retrieval justifies their token cost. Tiers differ by scope, function, lifetime, access, and authority; proximity changes availability, not authority. section 4.1.1

Table 4.1 Dimensions of agent memory
Memory category
Example content
 
Scope
 
Function
 
Lifetime and access
 
Owner or authority
 
Active context
 
Current instructions, evidence, tool results
 
Turn or session
 
Working state
 
Immediate and volatile
 
Runtime plus source owners
 
Task or session state
 
Goal, artifacts, receipts, pending decisions
 
Task or session
 
Resumption
 
Durable until task closure
 
Orchestrator or task owner
 
Project or user context
 
Conventions, preferences, profiles
 
Project, user, or team
 
Continuity
 
Durable, versioned, retrieved on demand
 
Human or system owner
 
Admitted lessons
Scoped guidance with admission evidence
Workload, team, or organization
Governed reuse
Versioned, expiring, supersedable
Admission owner
Archival evidence
Raw traces, prior versions, audit records
Task through organization
Audit and later review
Archived under retention policy
Evidence or records owner

Compare memory categories by scope, function, lifetime, access, and owner or authority. section 4.1.1

Keep placement separate from correctness and control:

  • Frequency and recency do not establish correctness; review model-written notes and set precedence for conflicting versions. section 4.2.6
  • Before a high-risk decision, retrieve the authoritative control-plane source and record which version governed the action. section 4.2.6

How Designing AI Agents covers it

How deep it goes
Distinguishes memory tiers and governance dimensions, then identifies promotion, eviction, invalidation, and conflict failures.
Examples
Uses active instructions, task receipts, project conventions, archival traces, MemGPT paging, and Mem0 update operations.
What you can do after
Evaluate agent memory placement and authority, and retrieve the governing source before high-risk decisions.
How it connects
Connects working, episodic, and semantic memory with context windows, external storage, and retrieval.

Also explained in

Compare how 5 books explain memory hierarchy →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Designing AI Agents. The section links point to the parts of the book it draws on.