宿主 Agent 的核心引擎。它运行任务、接收 hook 注入,并根据 GUIDE.md 判断是否加载 skill 或启动 subagent。
-工作记忆主体。Prime 直接把它加入 system prompt;memory_set.md 负责在线维护它。
-长期记忆主体。mnemon binary 通过 brew 安装;memory_get.md 和 dreaming subagent 通过协议调用它。
-diff --git a/README.md b/README.md index c0e8e24b..dd10741a 100644 --- a/README.md +++ b/README.md @@ -252,8 +252,8 @@ See [Development and Deployment](docs/DEPLOYMENT.md) for Docker, Compose, Ollama - [Mnemon Memory Harness](docs/framework/HARNESS.md) — skill-first memory harness design and installation guideline - [Harness Install Guide](docs/framework/INSTALL.md) — agent-facing installation contract - [Memory Guideline](docs/framework/GUIDELINE.md) — recall/writeback judgment policy -- [Self-Evolution Harness Design](docs/design/SELF_EVOLUTION_HARNESS.md) — consolidated v0.2 architecture for install, memory loop, skill evolution, and risk control -- [Agent Systems Research](docs/research/agent-systems/README.md) — condensed source index for memory and self-evolution research +- [Self-Evolution Harness Design](docs/design/self-evolution-harness/SELF_EVOLUTION_HARNESS.md) — consolidated v0.2 architecture for install, memory loop, skill evolution, and risk control +- [Agent Systems Research](docs/design/self-evolution-harness/research/agent-systems/README.md) — condensed source index for memory and self-evolution research - [Design & Architecture](docs/DESIGN.md) — current engine architecture, algorithms, integration design - [Usage & Reference](docs/USAGE.md) — CLI commands, embedding support, architecture overview - [Architecture Diagrams](docs/diagrams/) — system architecture, pipelines, lifecycle management diff --git a/docs/DESIGN.md b/docs/DESIGN.md index ef50df3f..feea24f0 100644 --- a/docs/DESIGN.md +++ b/docs/DESIGN.md @@ -6,7 +6,7 @@ Mnemon is a persistent memory system designed for LLM agents. It adopts the **LLM-Supervised** pattern: the host LLM acts as external orchestrator of a standalone memory binary through symbolic CLI interfaces, while the binary handles deterministic storage, graph indexing, and lifecycle management. Memory is organized as a four-graph knowledge structure with temporal, entity, causal, and semantic edges. Implemented as a single Go binary + SQLite, with no external API dependencies. -This document describes the current Mnemon binary and engine architecture. The broader memory harness doctrine lives in [Mnemon Memory Harness](framework/HARNESS.md), with installable runtime artifacts in [INSTALL.md](framework/INSTALL.md) and [GUIDELINE.md](framework/GUIDELINE.md). The v0.2 self-evolution architecture is consolidated in [Self-Evolution Harness Design](design/SELF_EVOLUTION_HARNESS.md). +This document describes the current Mnemon binary and engine architecture. The broader memory harness doctrine lives in [Mnemon Memory Harness](framework/HARNESS.md), with installable runtime artifacts in [INSTALL.md](framework/INSTALL.md) and [GUIDELINE.md](framework/GUIDELINE.md). The v0.2 self-evolution architecture is consolidated in [Self-Evolution Harness Design](design/self-evolution-harness/SELF_EVOLUTION_HARNESS.md). --- @@ -40,7 +40,7 @@ Effective Importance (EI) decay formula, immunity rules, auto-pruning, GC comman Markdown-installable runtime integration: `SKILL.md`, `INSTALL.md`, `GUIDELINE.md`, the four hook phases (Prime, Remind, Nudge, Compact), agent-led memory decisions, optional setup automation, and lightweight markdown self-evolution. -### [Self-Evolution Harness](design/SELF_EVOLUTION_HARNESS.md) +### [Self-Evolution Harness](design/self-evolution-harness/SELF_EVOLUTION_HARNESS.md) The v0.2 architecture for agent-agnostic installation, canonical `.mnemon` filesystem, memory consolidation loop, skill evolution, optional maintenance runner, and proposal-first risk control. diff --git a/docs/design/SELF_EVOLUTION_HARNESS.md b/docs/design/self-evolution-harness/SELF_EVOLUTION_HARNESS.md similarity index 98% rename from docs/design/SELF_EVOLUTION_HARNESS.md rename to docs/design/self-evolution-harness/SELF_EVOLUTION_HARNESS.md index f7429f5a..23e9aa78 100644 --- a/docs/design/SELF_EVOLUTION_HARNESS.md +++ b/docs/design/self-evolution-harness/SELF_EVOLUTION_HARNESS.md @@ -2,7 +2,7 @@ 本文档是 Mnemon self-evolution harness 的唯一核心设计入口。它替代此前分散在 `docs/design/self-evolution-harness/` 下的多份分篇设计,并把研究材料浓缩为架构决策所需的摘要。 -交互式架构展示保留在 [architecture-site.html](self-evolution-harness/architecture-site.html)。Issue 入口见 [#10](https://github.com/mnemon-dev/mnemon/issues/10),初始设计 PR 见 [#9](https://github.com/mnemon-dev/mnemon/pull/9)。 +交互式架构展示保留在 [architecture-site.html](architecture-site.html)。Memory loop MVP 的设计文档见 [memory-loop/README.zh.md](memory-loop/README.zh.md),双语可视化页面见 [memory-loop/site/index.html](memory-loop/site/index.html)。Issue 入口见 [#10](https://github.com/mnemon-dev/mnemon/issues/10),初始设计 PR 见 [#9](https://github.com/mnemon-dev/mnemon/pull/9)。 ## 1. 背景与决策 @@ -1196,7 +1196,7 @@ Cross-system conclusions: 5. Background maintenance needs provenance, reports, backups, and hard write boundaries. 6. Host-specific adapters should be convenience scripts, not the core architecture. -Source provenance is kept in [Agent Systems Research](../research/agent-systems/README.md). Detailed per-system notes were intentionally folded into this synthesis to keep the architecture maintainable. +Source provenance is kept in [Agent Systems Research](research/agent-systems/README.md). Detailed per-system notes were intentionally folded into this synthesis to keep the architecture maintainable. ## 18. 成功标准 Success Criteria diff --git a/docs/design/self-evolution-harness/architecture-site.html b/docs/design/self-evolution-harness/architecture-site.html index b3afe23f..6481f3f1 100644 --- a/docs/design/self-evolution-harness/architecture-site.html +++ b/docs/design/self-evolution-harness/architecture-site.html @@ -3,7 +3,7 @@
- +第一版只实现一个清晰的记忆闭环:HostAgent 通过 hook 获得时机,通过 Markdown guide 做判断,通过 memory_get / memory_set / dreaming subagent 调用具体协议,最终在 MEMORY.md 与 Mnemon 之间完成在线读写和离线巩固。
-这里先说明哪些东西是系统主体,哪些只是安装、触发、协议或维护资产。
-宿主 Agent 的核心引擎。它运行任务、接收 hook 注入,并根据 GUIDE.md 判断是否加载 skill 或启动 subagent。
-工作记忆主体。Prime 直接把它加入 system prompt;memory_set.md 负责在线维护它。
-长期记忆主体。mnemon binary 通过 brew 安装;memory_get.md 和 dreaming subagent 通过协议调用它。
-GUIDE.md 说明何时读写记忆;Claude Code setup scripts 负责把 hook、skill、subagent 挂载到宿主。
-Prime、Remind、Nudge、Compact 只负责触发时机,不承载记忆协议。
-memory_get.md 绑定 Mnemon recall;memory_set.md 绑定 MEMORY.md 编辑规则。
-dreaming subagent 负责维护任务:巩固、压缩、丢弃和长期写入。
-GUIDE.md 只回答“何时读记忆、何时写记忆、什么值得保留”,不直接绑定 MEMORY.md 或 Mnemon。
-memory_get.md 负责把“读记忆”落到 Mnemon recall;memory_set.md 通过 MNEMON_MEMORY_LOOP_DIR 定位并 patch MEMORY.md。
-Dreaming 不是普通 hook。它是被 spawn 的维护 subagent,先写 Mnemon,再整理 MEMORY.md。
-点击左侧阶段,只显示当前阶段的数据流,避免所有箭头同时出现。
-