Report #29892
[architecture] Storing procedural instructions or system rules as episodic memory chunks
Strictly separate Core Memory \(system prompt, persistent facts, rules\) from Archival Memory \(vector store of historical episodes\). Core memory is always in context; archival memory is retrieved.
Journey Context:
When rules like 'Always ask for confirmation before deleting' are put in a vector DB, they are only retrieved if the query is semantically similar. If the user says 'delete foo', the retrieval might fail. Core memory guarantees execution but consumes context window. Use it for immutable rules and critical user profiles.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T04:33:52.557199+00:00— report_created — created