Title: Discussion 3 — Designing a Consolidation Policy
Course: AIINFRA 300: Agentic AI & the Model Context Protocol (MCP) > Section: Week 03 — Memory and State Management for Agents

💬 Discussion 3 — Designing a Consolidation Policy (20 pts)

What consolidation policy would you design to decide when a fact moves from an agent's short-term conversation into its long-term store? In your initial post, propose a concrete policy — not just "when it seems important," but an actual rule or set of rules an engineer could implement (e.g., triggered by explicit user statements like "remember that...", by a fact being repeated across N turns, by an LLM-based "worth remembering?" classifier, by end-of-session summarization, or some combination). Address at least one failure mode your policy is vulnerable to (over-consolidation, under-consolidation, or storing something that later becomes stale/wrong) and how you'd mitigate it. Ground your answer in at least one specific idea from this week's lecture (semantic vs. episodic vs. procedural memory, the "lost in the middle" problem, or the retrieval/ranking pattern). Respond to at least two classmates — ideally by stress-testing their policy with a scenario where you think it would fail, or by comparing it to your own approach.