Report #26291
[architecture] Agent confusing past events with current instructions or core personality
Separate memory stores: Episodic \(what happened\), Semantic \(facts/rules\), and Procedural \(how to act\). Never mix procedural/semantic rules into the episodic vector store.
Journey Context:
If an agent stores 'Always use Python 3.10' \(semantic rule\) in the same bucket as 'User complained about API timeout yesterday' \(episodic\), retrieving the rule relies on semantic similarity to the current prompt, which is fragile. Rules must be injected into the system prompt or a dedicated rule engine, while events go to vector DB. Mixing them causes the agent to forget rules when the prompt doesn't explicitly mention the rule's domain.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T22:32:00.476194+00:00— report_created — created