Engineer Atlas
OverviewLearnArchitecture FinderPlaygroundFrameworksRoadmapPracticeInterview
OverviewLearnArchitecture FinderPlaygroundFrameworksRoadmapPracticeInterviewHiring GuideCheat SheetCompare
Agentic Engineering
  • Fundamentals
  • Agent Architecture
  • Tool Calling
  • RAG Engineering
  • Context Engineering
  • Memory & State
  • Planning
  • MCP — Model Context Protocol
  • Multi-Agent Systems
  • Human-in-the-Loop
  • Evaluation & Testing
  • Observability
  • Guardrails & Security
  • Reliability Engineering
  • Frameworks
Agentic/Learn/Memory & State

Memory & State

Context vs short-term vs long-term; semantic, episodic, procedural; why more is not better.

Memory Types
▶ interactive

Agents have three storage horizons — the context window, short-term session state, and long-term persistent memory — and long-term memory splits into semantic facts, episodic events and procedural know-how.

Memory Architectures

A memory system is a write path (extract → dedupe → store) plus a read path (retrieve → rank → inject) over a store chosen for the access pattern — key-value, vector or graph — always scoped per user.

Memory Pitfalls

More memory is not automatically better: pollution, poor retrieval, summarisation drift, missing expiry, privacy exposure and no user control each turn a helpful feature into a liability.

Engineer Atlas
GitHub·LinkedIn