|
| 1 | +# 🧠Nexent Intelligent Memory System Technical Specification |
| 2 | + |
| 3 | +## 1. System Architecture Overview |
| 4 | + |
| 5 | +The Nexent Intelligent Memory System is built on an advanced memory storage architecture that provides intelligent agents with persistent context-aware capabilities. Through a multi-layered memory management mechanism, the system achieves cross-conversation knowledge accumulation and retrieval, significantly enhancing the coherence and personalization of human-machine interactions. |
| 6 | + |
| 7 | +### Core Technical Features |
| 8 | +- **Layered Memory Architecture**: Four-level memory storage system built on the mem0 framework |
| 9 | +- **Adaptive Memory Management**: Supports both automated and manual memory operation modes |
| 10 | +- **Cross-Session Persistence**: Ensures continuity of knowledge and context across multiple conversations |
| 11 | +- **Fine-Grained Permission Control**: Provides flexible memory sharing strategy configuration |
| 12 | + |
| 13 | +--- |
| 14 | + |
| 15 | +## 2. Configuration and Initialization |
| 16 | + |
| 17 | +### 2.1 System Activation |
| 18 | +1. Access the memory management interface: Click the **Memory Management Icon** in the upper right corner of the conversation interface |
| 19 | +2. Enter the **System Configuration** module for initialization settings |
| 20 | + |
| 21 | +### 2.2 Core Configuration Parameters |
| 22 | + |
| 23 | +| Configuration Item | Options | Default Value | Description | |
| 24 | +|-------------------|---------|---------------|-------------| |
| 25 | +| Memory Service Status | Enable/Disable | Enable | Controls the operational status of the entire memory system | |
| 26 | +| Agent Memory Sharing Strategy | Always Share/Ask Me Each Time/Prohibit Sharing | Always Share | Defines whether user authorization consent is required for memory sharing between agents | |
| 27 | + |
| 28 | +<div style="display: flex; justify-content: left;"> |
| 29 | + <img src="./assets/memory/mem-config.png" style="width: 80%; height: auto;" alt="Select Agent" /> |
| 30 | +</div> |
| 31 | + |
| 32 | +--- |
| 33 | + |
| 34 | +## 3. Layered Memory Architecture |
| 35 | + |
| 36 | +Nexent adopts a four-layer memory storage architecture based on **mem0**, achieving precise memory classification and retrieval through different scopes and lifecycle management: |
| 37 | + |
| 38 | +### 3.1 Architecture Layer Details |
| 39 | + |
| 40 | +| Memory Level | Scope | Storage Content | Lifecycle | Configuration Role | Typical Applications | |
| 41 | +|--------------|-------|-----------------|-----------|-------------------|---------------------| |
| 42 | +| **Tenant Level Memory** | Organization-wide | Enterprise-level standard operating procedures, compliance policies, organizational structure, factual information | Long-term storage | Tenant Administrator | Enterprise knowledge management, standardized process execution, compliance checking | |
| 43 | +| **Agent Level Memory** | Specific Agent | Professional domain knowledge, skill templates, historical conversation summaries, learning accumulation | Consistent with agent lifecycle | Tenant Administrator | Professional skill accumulation, domain knowledge sedimentation, experiential learning | |
| 44 | +| **User Level Memory** | Specific User Account | Personal preference settings, usage habits, common instruction templates, personal information | Long-term storage | All Users | Personalized services, user experience optimization, preference management | |
| 45 | +| **User-Agent Level Memory** | Specific Agent under Specific User Account | Collaboration history, personalized factual information, specific task context, relationship models | Consistent with agent lifecycle | All Users | Deep collaboration scenarios, personalized tuning, task continuity maintenance | |
| 46 | + |
| 47 | +### 3.2 Memory Priority and Retrieval Strategy |
| 48 | + |
| 49 | +Memory retrieval follows the following priority order (from high to low): |
| 50 | +1. **Tenant Level** → Basic facts |
| 51 | +2. **User-Agent Level** → Most specific context information |
| 52 | +3. **User Level** → Personal preferences and habits |
| 53 | +4. **Agent Level** → Professional knowledge and skills |
| 54 | + |
| 55 | +--- |
| 56 | + |
| 57 | +## 4. Operation Modes and Functional Interfaces |
| 58 | + |
| 59 | +### 4.1 Automated Memory Management |
| 60 | +- **Intelligent Extraction**: Automatically identifies key factual information in conversations and generates memory entries |
| 61 | +- **Automatic Context Embedding**: Agents automatically retrieve the most relevant memory entries and implicitly embed them in conversation context |
| 62 | +- **Incremental Updates**: Supports progressive updates, supplementation, and automatic cleanup of memory content |
| 63 | + |
| 64 | +### 4.2 Manual Memory Operations |
| 65 | + |
| 66 | +#### Adding Memory |
| 67 | +- Click the green plus button, input text, then click the checkmark to add a memory entry (maximum 500 characters) |
| 68 | + |
| 69 | +<div style="display: flex; justify-content: left;"> |
| 70 | + <img src="./assets/memory/add-mem.png" style="width: 80%; height: auto;" alt="Select Agent" /> |
| 71 | +</div> |
| 72 | + |
| 73 | +#### Deleting Memory |
| 74 | +- Click the red cross button, then click confirm in the popup confirmation dialog to delete all memory entries under a specific Agent group |
| 75 | +- Click the red eraser button to delete a specific memory entry |
| 76 | + |
| 77 | +<div style="display: flex; justify-content: left;"> |
| 78 | + <img src="./assets/memory/delete-mem.png" style="width: 80%; height: auto;" alt="Select Agent" /> |
| 79 | +</div> |
| 80 | + |
| 81 | +### 4.3 Memory Management Best Practices |
| 82 | + |
| 83 | +1. **Atomicity Principle**: Each memory entry should contain **concise**, **single**, **clear** factual information |
| 84 | +2. **Temporal Management**: Regularly clean up outdated or no longer relevant memory entries to maintain the timeliness and accuracy of the memory database |
| 85 | +3. **Privacy Protection**: Sensitive information should be avoided from being shared at the tenant level or agent level |
0 commit comments