docs: remove deprecated Graph Memory references
Graph Memory was deprecated on April 16, 2026. This removes remaining mentions across docs that could mislead readers into thinking it is still a supported feature. - Platform pages (overview, quickstart, faqs, platform-vs-oss, vibecoding): remove graph memory from feature lists, comparison table, and intro copy - Platform features (platform-overview, mcp-integration, advanced-memory-operations): rephrase "graph-powered retrieval" to "advanced retrieval"; drop "Enable graph memories" tip; remove graph-edge verification step from the metadata example - Core concepts (add, search, memory-types, memory-evaluation): remove "optional graph storage" / "graph features" / "graph writes" / "graph toggles"; drop "graph" from Entity Search description; remove outdated add/search architecture diagrams (replacement pending) - Open source features (overview, rest-api): remove "graph relationships" and "graph backend(s)" from REST server config narrative - API reference (organizations-projects): drop "graph settings" from Update Project Settings description - Cookbooks: remove "Graph Memory on Neptune" card (page removed) and Neptune mention from AWS Bedrock card; remove "Graph Capabilities" bullet from Gemini cookbook; remove graph-memory conditional bullet from controlling-memory-ingestion - CLI: remove --graph / --no-graph flags from mem0 add / mem0 search flag tables and MEM0_ENABLE_GRAPH env var - Images: delete orphan add_architecture.png and search_architecture.png
This commit is contained in:
@@ -25,10 +25,6 @@ Mem0's search operation lets agents ask natural-language questions and get back
|
||||
|
||||
## Architecture
|
||||
|
||||
<Frame caption="Architecture diagram illustrating the memory search process.">
|
||||
<img src="../../images/search_architecture.png" />
|
||||
</Frame>
|
||||
|
||||
<Steps>
|
||||
<Step title="Query processing">
|
||||
Mem0 cleans and enriches your natural-language query so the downstream embedding search is accurate.
|
||||
|
||||
Reference in New Issue
Block a user