-
Notifications
You must be signed in to change notification settings - Fork 1
Description
Discussed in #3
Originally posted by dynamder November 17, 2025
架构变更说明 Major Architecture Refactoring (EN/简体中文)
English Version Below / 中文版本见下文
CN 中文公告
为了构建一个更健壮、可扩展的基础架构,以更好地实现项目的核心目标——高效管理和查询复杂的记忆数据,我们决定对项目进行一次全面的底层重构。此次重构将解决原有架构(Alpha版本)在设计和灵活性上的限制,为未来的功能迭代打下坚实基础。
🎯 主要变更内容
- 记忆模型重构: 核心变更是将原先单一的
MemoryNote模型拆分为三个职责明确的记忆类别(语义记忆、情景记忆、程序记忆),从而提供更精确的数据管理和查询能力。 - API 规范化: 设计一套清晰、统一的 API 接口,提升开发者体验和系统可维护性。
- 技术栈评估: 我们正在评估由 Qdrant + SurrealDB 转向 Helix DB 的可能性,以寻求更优的性能和一体化体验。当前新架构设计仍以现有技术栈为基础。
📄 当前状态与文档
新架构的初步设计已经完成,并已形成文档。
- 详细设计说明: 请查阅
docs/architecture/beta_ver.md了解完整的架构设计、决策理由和未来规划。 - 代码状态: 新的架构代码将陆续在
main分支上开发。请注意,main分支在重构期间可能处于不稳定状态。
致开发团队成员
- 开发流程:
main分支已启用保护规则。请通过 Pull Request 进行代码审阅和合并。 - 旧代码存档: 旧的 Alpha 版本代码已被存档至
alpha_deprecated分支,仅供历史参考。所有新开发请基于main分支进行。
致感兴趣的用户和贡献者
- 预览与反馈: 我们诚挚邀请您预览架构设计文档。如果您有任何想法、问题或发现,欢迎通过 [创建 Discussion] 或 [提交 Issue] 与我们交流,您的反馈至关重要。
- 注意事项:
main分支目前无法用于实际开发。
感谢您的关注与持续支持!我们相信这次重构是项目演进的关键一步,将带来显著的长期价值。我们期待与社区一同打造一个更强大的系统。
EN English Announcement
To build a more robust and scalable infrastructure that better achieves the project’s core goal—efficiently managing and querying complex memory data—we have decided to conduct a comprehensive low-level refactoring of the project. This refactoring will address the design and flexibility limitations of the original architecture (Alpha version) and lay a solid foundation for future feature iterations.
🎯 Key Changes
- Memory Model Refactoring: The core change involves splitting the previously monolithic
MemoryNotemodel into three distinct memory categories (semantic memory, episodic memory, and procedural memory), enabling more precise data management and querying capabilities. - API Standardization: A clear and unified set of API interfaces will be designed to improve developer experience and system maintainability.
- Tech Stack Evaluation: We are evaluating the possibility of transitioning from Qdrant + SurrealDB to Helix DB to pursue better performance and an integrated experience. For now, the new architecture design remains based on the existing tech stack.
📄 Current Status & Documentation
The initial design of the new architecture has been completed and documented.
- Detailed Design Documentation: Please refer to
docs/architecture/beta_ver.mdfor the complete architecture design, rationale behind decisions, and future plans. - Code Status: The new architecture code will be developed incrementally on the
mainbranch. Please note that themainbranch may be unstable during the refactoring period.
For Development Team Members
- Development Workflow: The
mainbranch is now protected. Please use Pull Requests for code review and merging. - Legacy Code Archive: The old Alpha version code has been archived in the
alpha_deprecatedbranch for historical reference only. All new development should be based on themainbranch.
For Interested Users and Contributors
- Preview and Feedback: We sincerely invite you to preview the architecture design documentation. If you have any ideas, questions, or findings, please feel free to share them by [creating a Discussion] or [submitting an Issue]. Your feedback is highly valuable.
- Important Note: The
mainbranch is currently not suitable for practical development use.
Thank you for your attention and continued support! We believe this refactoring is a critical step in the project’s evolution and will bring significant long-term value. We look forward to building a more powerful system together with the community.