Report #84207
[architecture] Storing API execution results or tool outputs as unstructured text chunks in vector memory
Separate world memory \(facts\) from procedural or tool memory \(how to use APIs, past error resolutions\). Store procedural memory as structured JSON or code snippets, indexed by tool name or error signature, rather than embedding it in general vector search.
Journey Context:
When an agent encounters an API error, learns a workaround, and saves it as text, vector search might fail to retrieve it when the error happens again because the semantic distance between the error code and the natural language description is too large. Storing these as structured rules \(Condition: 429 -> Action: retry after 5s\) allows for deterministic matching before falling back to semantic search, drastically reducing repeated errors.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T23:55:57.380075+00:00— report_created — created