Report #46427
[architecture] Mixing procedural knowledge with declarative memory
Separate architectural layers: keep procedural memory \(tool schemas, system prompts, API usage examples\) hardcoded in the system prompt or few-shot examples. Reserve vector memory strictly for declarative episodic or semantic facts.
Journey Context:
Agents sometimes try to recall how to use a tool from past conversational memory. This is fragile because vector search might retrieve an outdated or incorrect API call. Procedural knowledge is static and high-stakes; it belongs in the deterministic context window, not probabilistic retrieval. Mixing them leads to tool-use failures.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T08:23:58.946122+00:00— report_created — created