Table of Contents
Fetching ...

MemArchitect: A Policy Driven Memory Governance Layer

Lingavasan Suresh Kumar, Yang Ba, Rong Pan

Abstract

Persistent Large Language Model (LLM) agents expose a critical governance gap in memory management. Standard Retrieval-Augmented Generation (RAG) frameworks treat memory as passive storage, lacking mechanisms to resolve contradictions, enforce privacy, or prevent outdated information ("zombie memories") from contaminating the context window. We introduce MemArchitect, a governance layer that decouples memory lifecycle management from model weights. MemArchitect enforces explicit, rule-based policies, including memory decay, conflict resolution, and privacy controls. We demonstrate that governed memory consistently outperforms unmanaged memory in agentic settings, highlighting the necessity of structured memory governance for reliable and safe autonomous systems.

MemArchitect: A Policy Driven Memory Governance Layer

Abstract

Persistent Large Language Model (LLM) agents expose a critical governance gap in memory management. Standard Retrieval-Augmented Generation (RAG) frameworks treat memory as passive storage, lacking mechanisms to resolve contradictions, enforce privacy, or prevent outdated information ("zombie memories") from contaminating the context window. We introduce MemArchitect, a governance layer that decouples memory lifecycle management from model weights. MemArchitect enforces explicit, rule-based policies, including memory decay, conflict resolution, and privacy controls. We demonstrate that governed memory consistently outperforms unmanaged memory in agentic settings, highlighting the necessity of structured memory governance for reliable and safe autonomous systems.
Paper Structure (28 sections, 9 equations, 1 figure, 1 table)

This paper contains 28 sections, 9 equations, 1 figure, 1 table.

Figures (1)

  • Figure 1: The MemArchitect Governance Workflow. The system operates as a continuous closed loop across three paths: (1) Read Path (Top): Incoming queries are classified by intent to customize the search. Memories are retrieved, filtered for safety, and ranked by value to fit the limited context budget. (2) Reflect Path (Right): A feedback loop detects which memories were actually used to generate the answer, strengthening useful information while penalizing distractions. (3) Background Path (Bottom): During idle cycles, a maintenance process automatically cleans the memory store by deleting forgotten noise and compressing fading details into permanent facts.