docs: reorganize harness documentation

README.md

@@ -209,8 +209,8 @@ Different agents/processes can use different stores via the `MNEMON_STORE` envir
 
 **How do I customize the behavior?**
 Edit the generated guideline (`~/.mnemon/prompt/guide.md` in current setup
-flows) or use the installable [GUIDELINE.md](docs/framework/GUIDELINE.md) as
-the source. The skill file should stay focused on command syntax.
+flows) or use the installable [memory loop GUIDE](harness/memory-loop/GUIDE.md)
+as the source. The skill file should stay focused on command syntax.
 
 **What is sub-agent delegation?**
 Sub-agent delegation is optional. When a runtime supports it, the main agent can
@@ -249,11 +249,9 @@ See [Development and Deployment](docs/DEPLOYMENT.md) for Docker, Compose, Ollama
 
 ## Documentation
 
-- [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/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
+- [Modular Self-Evolution Harness](docs/harness/README.md) — formal harness docs for modular agent, memory loop, and skill loop design
+- [Memory Loop Harness](harness/memory-loop/README.md) — installable memory loop assets
+- [Skill Loop Harness](harness/skill-loop/README.md) — installable skill loop assets
 - [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

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/SELF_EVOLUTION_HARNESS.md).
+This document describes the current Mnemon binary and engine architecture. The formal modular self-evolution harness docs live in [Mnemon Harness](harness/README.md), with installable runtime assets under the repository-level [harness](../harness/) directory.
 
 ---
 
@@ -40,9 +40,9 @@ 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/SELF_EVOLUTION_HARNESS.md)
+### [Self-Evolution Harness](harness/README.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.
+The formal modular harness docs for agent-agnostic installation, memory loop, skill loop, and future attachable evolution modules.
 
 ### [8. Design Decisions & Future Direction](design/08-decisions.md)
 

docs/design/02-philosophy.md

@@ -30,10 +30,11 @@ This means:
 - **Stronger judgment capability**: An Opus-class LLM evaluates candidate links, not gpt-4o-mini
 - **LLM swappable**: The same Binary + Skill works across Claude Code, Cursor, or any LLM CLI
 
-This engine follows the broader [Mnemon Memory Harness](../framework/HARNESS.md) stance:
-hook-native, LLM-led, and protocol-constrained. The framework doctrine is kept
-separate from the current engine architecture so we can discuss principles
-without assuming today's binary is the final runtime shape.
+This engine follows the broader [Mnemon Harness](../harness/README.md) stance:
+hook-native, LLM-led, protocol-constrained, and modular around the host agent.
+The harness doctrine is kept separate from the current engine architecture so
+we can discuss principles without assuming today's binary is the final runtime
+shape.
 
 ## 2.2 Tools are Organs, Skills are Textbooks