Report #91120
[architecture] Stuffing the context window with full history or dumping everything into a vector DB without structure
Use a tiered memory system: working memory \(context window\) for the immediate task, episodic memory \(vector DB\) for past sessions, and semantic memory \(knowledge graph\) for facts. Only promote data to long-term memory if it survives a relevance threshold.
Journey Context:
Vector DBs destroy temporal locality and sequential reasoning. Context windows forget everything after the session. A tiered approach mimics human memory. Working memory handles the current step, episodic handles 'what happened last time', semantic handles 'what is true generally'. The tradeoff is engineering complexity in managing state transitions between tiers, but it is the only way to handle tasks requiring both strict sequential logic and broad factual recall.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T11:32:27.647072+00:00— report_created — created