docs: finish Mimir -> Mneme prose rename in remaining docs (#321)

Code identifiers, GHCR image, repo URLs, and registry metadata were
already renamed in #318/#319. This pass covers the product-name prose
still saying "Mimir" in awesome-mimir.md, CONTRIBUTING.md, SUPPORT.md,
SBOM/federal-buyers/EXPORT-CONTROL docs, the three MCP client
integration guides, the three vs-competitor comparison docs, and the
four integrations/ READMEs.

Deliberately left "mimir"/"Mimir" where it's a real back-compat
identifier rather than prose:
- mimir_* MCP tool wire names (unchanged, back-compat guaranteed)
- ~/.mimir/data/mimir.db path examples (unchanged, back-compat path)
- The CLI binary invocation and "mcpServers": {"mimir": {"command":
  "mimir", ...}} config key — install.sh symlinks mneme -> mimir, so
  "mimir" is still the primary working command today
- PyPI package/module names and classes (mimir_autogen, mimir_crewai,
  mimir_langgraph, mimir-persist, MimirStore, MimirMemoryTool,
  MimirMemory) and their real "binary=\"mimir\"" code defaults
- docs/SBOM.md's literal crate/component identifiers
  (crates.io:mimir@2.0.0, Component name: mimir)
- External repo name (hermes-mimir-plugin) and this repo's own
  filenames (awesome-mimir.md, mimir-vs-*.md)

Co-authored-by: tcconnally <hermes@perseus.observer>
Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>

Author: 3 people

CONTRIBUTING.md

@@ -1,14 +1,14 @@
-# Contributing to Mimir
+# Contributing to Mneme
 
-Thanks for wanting to help! Mimir is a Rust MCP server for persistent AI agent
+Thanks for wanting to help! Mneme is a Rust MCP server for persistent AI agent
 memory. Contributions of all kinds are welcome — code, docs, bug reports, feature
 ideas.
 
 ## Development Setup
 
 ```bash
 git clone https://github.com/Perseus-Computing-LLC/mneme.git
-cd mimir
+cd mneme
 
 # Build (requires Rust 1.70+)
 cargo build --release

SUPPORT.md

@@ -10,11 +10,11 @@
 
 ## MCP Host Integration
 
-Mimir works with any MCP-compatible host. See the [README](README.md#mcp-configuration)
+Mneme works with any MCP-compatible host. See the [README](README.md#mcp-configuration)
 for Claude Desktop, Cursor, OpenClaw, and Hermes Agent configuration examples.
 
 ## Perseus Integration
 
-If you're using Mimir as the memory backend for Perseus, see the
+If you're using Mneme as the memory backend for Perseus, see the
 [Perseus docs](https://github.com/Perseus-Computing-LLC/perseus) for the full
 `.perseus/config.yaml` setup.

awesome-mimir.md

@@ -1,7 +1,7 @@
-# Awesome Mimir
+# Awesome Mneme
 
-> Curated list of Mimir integrations, tools, and resources.
-> Mimir is an MCP-native, local-first persistent memory engine for AI agents.
+> Curated list of Mneme integrations, tools, and resources.
+> Mneme is an MCP-native, local-first persistent memory engine for AI agents.
 
 ## Contents
 
@@ -15,14 +15,14 @@
 
 ## Official Resources
 
-- [Mimir GitHub Repo](https://github.com/Perseus-Computing-LLC/mneme) — The Mimir source
+- [Mneme GitHub Repo](https://github.com/Perseus-Computing-LLC/mneme) — The Mneme source
 - [Roadmap](https://github.com/Perseus-Computing-LLC/mneme/blob/main/ROADMAP.md)
 - [Contributing Guide](https://github.com/Perseus-Computing-LLC/mneme/blob/main/CONTRIBUTING.md)
 - [Security Policy](https://github.com/Perseus-Computing-LLC/mneme/blob/main/SECURITY.md)
 
 ## Framework Integrations
 
-Mimir adapters for popular AI agent frameworks:
+Mneme adapters for popular AI agent frameworks:
 
 ### LangGraph (LangChain)
 - [mimir-langgraph](https://github.com/Perseus-Computing-LLC/mneme/tree/main/integrations/langgraph) — `MimirStore` implementing `BaseStore`
@@ -40,15 +40,15 @@ Mimir adapters for popular AI agent frameworks:
 - `pip install -e integrations/autogen/`
 
 ### Other Frameworks
-Mimir is MCP-native — any framework with MCP support can use Mimir directly:
+Mneme is MCP-native — any framework with MCP support can use Mneme directly:
 - [OpenAI Agents SDK](https://github.com/openai/openai-agents-python) — via MCP stdio
 - [Google ADK](https://github.com/google/adk-python) — via MCP stdio
 - [Agno](https://github.com/agno-agi/agno) — via MCP stdio
 - [Magentic-One](https://github.com/anthropics/anthropic-quickstarts) — via MCP stdio
 
 ## MCP Hosts
 
-Mimir works with any MCP host. Configuration is one line:
+Mneme works with any MCP host. Configuration is one line:
 
 ```json
 {
@@ -71,7 +71,7 @@ Tested and confirmed working with:
 
 ## Tools & Plugins
 
-### Mimir Itself (36 MCP Tools)
+### Mneme Itself (36 MCP Tools)
 
 | Category | Tools |
 |---|---|
@@ -88,28 +88,28 @@ Tested and confirmed working with:
 
 ### Plugin Ecosystem
 
-- [hermes-mimir-plugin](https://github.com/Perseus-Computing-LLC/hermes-mimir-plugin) — Native Mimir integration for Hermes Agent
-- [Perseus Mimir Connector](https://github.com/Perseus-Computing-LLC/perseus) — Perseus live context injection from Mimir
+- [hermes-mimir-plugin](https://github.com/Perseus-Computing-LLC/hermes-mimir-plugin) — Native Mneme integration for Hermes Agent
+- [Perseus Mneme Connector](https://github.com/Perseus-Computing-LLC/perseus) — Perseus live context injection from Mneme
 
 ## Community Projects
 
 *Add your project here! Open a PR to [awesome-mimir.md](https://github.com/Perseus-Computing-LLC/mneme/blob/main/awesome-mimir.md).*
 
 ## Articles & Tutorials
 
-*Add articles, blog posts, and tutorials about Mimir.*
+*Add articles, blog posts, and tutorials about Mneme.*
 
 ## Comparisons
 
-- [Mimir vs Mem0](https://github.com/Perseus-Computing-LLC/mneme/blob/main/docs/comparison/mimir-vs-mem0.md) — Local-first vs cloud-only
-- [Mimir vs Letta](https://github.com/Perseus-Computing-LLC/mneme/blob/main/docs/comparison/mimir-vs-letta.md) — Memory engine vs agent runtime
-- [Mimir vs Zep](https://github.com/Perseus-Computing-LLC/mneme/blob/main/docs/comparison/mimir-vs-zep.md) — Single binary vs infrastructure
+- [Mneme vs Mem0](https://github.com/Perseus-Computing-LLC/mneme/blob/main/docs/comparison/mimir-vs-mem0.md) — Local-first vs cloud-only
+- [Mneme vs Letta](https://github.com/Perseus-Computing-LLC/mneme/blob/main/docs/comparison/mimir-vs-letta.md) — Memory engine vs agent runtime
+- [Mneme vs Zep](https://github.com/Perseus-Computing-LLC/mneme/blob/main/docs/comparison/mimir-vs-zep.md) — Single binary vs infrastructure
 
 ## Key Differentiators
 
-Why Mimir stands out:
+Why Mneme stands out:
 
-| Feature | Mimir | Mem0 | Letta | Zep |
+| Feature | Mneme | Mem0 | Letta | Zep |
 |---|---|---|---|---|
 | **MCP-Native** | ✅ 36 tools | ❌ | ❌ | ❌ |
 | **Local-First** | ✅ Single binary | ❌ Cloud-dependent | ❌ Docker + Postgres | ❌ Docker + Postgres |

docs/EXPORT-CONTROL.md

@@ -1,4 +1,4 @@
-# Export Control Self-Classification — Perseus & Mimir
+# Export Control Self-Classification — Perseus & Mneme
 
 **Prepared by:** Perseus Computing LLC
 **Date:** 2026-06-20
@@ -9,7 +9,7 @@
 
 ## Executive Summary
 
-Both Perseus (perseus-ctx) and Mimir are **MIT-licensed, publicly available open source software**.
+Both Perseus (perseus-ctx) and Mneme are **MIT-licensed, publicly available open source software**.
 Under the Export Administration Regulations (EAR) 15 CFR §§ 730-774 and the International
 Traffic in Arms Regulations (ITAR) 22 CFR §§ 120-130, both products are self-classified as
 **EAR99** — not subject to export licensing requirements.
@@ -26,7 +26,7 @@ This document provides the analysis and rationale for federal procurement and SB
 - **Distribution:** PyPI (public package registry)
 - **Source:** https://github.com/Perseus-Computing-LLC/perseus (public, MIT license)
 
-### Mimir (v2.0.0)
+### Mneme (v2.0.0)
 - **Type:** Rust binary — persistent memory MCP server for AI agents
 - **Function:** Stores, searches, and retrieves structured entities via JSON-RPC 2.0 over stdio. Includes AES-256-GCM encryption (standard commercial algorithm). Optional embedding via public ONNX models. No cryptographic key management — keys are user-provided.
 - **Distribution:** GitHub Releases (public binary downloads)
@@ -39,7 +39,7 @@ This document provides the analysis and rationale for federal procurement and SB
 ### Jurisdiction: EAR99
 
 Per 15 CFR § 734.3(b), items subject to the EAR include all items in the United States
-unless specifically excluded. The following analysis determines whether Perseus or Mimir
+unless specifically excluded. The following analysis determines whether Perseus or Mneme
 fall under a more restrictive ECCN (Export Control Classification Number).
 
 ### ECCN Review
@@ -56,7 +56,7 @@ fall under a more restrictive ECCN (Export Control Classification Number).
 
 ### Cryptography Analysis (ECCN 5D002)
 
-Mimir includes AES-256-GCM encryption via the `aes-gcm` Rust crate (v0.10). Under
+Mneme includes AES-256-GCM encryption via the `aes-gcm` Rust crate (v0.10). Under
 EAR Category 5 Part 2, cryptographic software may require classification under 5D002.
 
 **However**, per 15 CFR § 740.13(b)(1) and Supplement No. 8 to Part 742, "publicly
@@ -66,7 +66,7 @@ available" encryption source code is **not subject to the EAR** when it is:
 2. Available for free distribution (MIT license — ✅)
 3. Not restricted to specific countries or persons (public repo — ✅)
 
-Both Perseus and Mimir source code are publicly available on GitHub under MIT license.
+Both Perseus and Mneme source code are publicly available on GitHub under MIT license.
 The AES-256-GCM implementation is via a standard, publicly available open-source crate.
 No proprietary or classified encryption algorithms are used.
 
@@ -85,7 +85,7 @@ countries, 10% for embargoed destinations).
 ### USML Review
 
 Per 22 CFR § 121.1 (United States Munitions List), ITAR controls apply to defense
-articles and services. Neither Perseus nor Mimir:
+articles and services. Neither Perseus nor Mneme:
 
 - Are specifically designed, developed, configured, adapted, or modified for a
   military application (Category I-XXI)
@@ -120,7 +120,7 @@ open source software, standard EAR99 treatment applies.
 | Product | ECCN | ITAR | License Required | Encryption Registration |
 |---|---|---|---|---|
 | Perseus (perseus-ctx) | EAR99 | Not applicable | No | No |
-| Mimir | EAR99 | Not applicable | No | No (public availability exclusion) |
+| Mneme | EAR99 | Not applicable | No | No (public availability exclusion) |
 
 ---
 

docs/SBOM.md

@@ -1,4 +1,4 @@
-# Mimir SBOM (Software Bill of Materials)
+# Mneme SBOM (Software Bill of Materials)
 ## For Federal Procurement Compliance
 
 **Package:** mimir v2.0.0

docs/comparison/mimir-vs-letta.md

@@ -1,8 +1,8 @@
-# Mimir vs Letta: Memory Engine vs Agent Runtime
+# Mneme vs Letta: Memory Engine vs Agent Runtime
 
 ## Quick Summary
 
-| | Mimir | Letta |
+| | Mneme | Letta |
 |---|---|---|
 | **Stars** | ~20 | ~15K |
 | **What it is** | Pure memory engine | Full agent runtime with memory |
@@ -18,11 +18,11 @@
 
 ## Architecture: Composable vs Monolithic
 
-Mimir is a **pure memory engine** — it does one thing (persistent memory) and
+Mneme is a **pure memory engine** — it does one thing (persistent memory) and
 composes with any agent framework via MCP stdio. Letta is an **agent runtime**
 that includes memory as one component.
 
-### Mimir: Memory as a Service
+### Mneme: Memory as a Service
 
 ```
 CrewAI ──────────┐
@@ -32,8 +32,8 @@ Claude Desktop ──┤                    └── SQLite
 Cursor ──────────┘
 ```
 
-Mimir plugs into any MCP host. Your agents can use CrewAI, LangGraph, AutoGen,
-or any framework — Mimir is just the memory layer.
+Mneme plugs into any MCP host. Your agents can use CrewAI, LangGraph, AutoGen,
+or any framework — Mneme is just the memory layer.
 
 ### Letta: Everything in One Box
 
@@ -49,7 +49,7 @@ Letta agents run inside Letta's runtime. The memory is coupled to the agent
 framework. You can't use Letta's memory with a CrewAI agent or a Claude Desktop
 session.
 
-## When to Use Mimir
+## When to Use Mneme
 
 - You want memory that **works with any agent framework**
 - You're building agents with CrewAI, LangGraph, AutoGen, or raw MCP
@@ -68,9 +68,9 @@ session.
 
 ## Memory Models
 
-### Mimir: Lifecycle-Aware Entities
+### Mneme: Lifecycle-Aware Entities
 
-Mimir entities have a full lifecycle:
+Mneme entities have a full lifecycle:
 - **Ebbinghaus decay** — memories naturally fade unless retrieved
 - **Layer promotion** — buffer → working → core based on access patterns
 - **Automatic archival** — stale entities archive, recoverable
@@ -91,8 +91,8 @@ a standalone memory service.
 
 ## MCP Tools: 36 vs 8
 
-Mimir's 36 MCP tools cover the entire memory surface. Letta exposes ~8 tools
-focused on agent state management. Mimir's additional tools enable:
+Mneme's 36 MCP tools cover the entire memory surface. Letta exposes ~8 tools
+focused on agent state management. Mneme's additional tools enable:
 
 - **mimir_correct** — structured learning from errors
 - **mimir_synthesize** — LLM session synthesis
@@ -103,21 +103,21 @@ focused on agent state management. Mimir's additional tools enable:
 
 ## Honest Assessment
 
-**Mimir's strengths vs Letta:**
+**Mneme's strengths vs Letta:**
 - Composable with any framework (not locked into one agent runtime)
 - Single binary, no PostgreSQL dependency
 - 36 MCP tools vs 8
 - Encryption at rest
 - Full entity lifecycle management
 - MIT license
 
-**Mimir's weaknesses vs Letta:**
+**Mneme's weaknesses vs Letta:**
 - Letta has a more mature agent platform with advanced features
 - Letta's memory block model is well-tested in production
 - Letta provides managed cloud hosting (Letta Cloud)
 - Larger community and more documentation
 - Sandboxed code execution is Letta-native
 
-**If you're choosing today:** Mimir is the better choice if you want memory
+**If you're choosing today:** Mneme is the better choice if you want memory
 that works with any agent framework. Letta is better if you want a complete
 managed agent platform and are willing to commit to Letta's ecosystem.

docs/comparison/mimir-vs-mem0.md

@@ -1,8 +1,8 @@
-# Mimir vs Mem0: Local-First vs Cloud-Only Memory
+# Mneme vs Mem0: Local-First vs Cloud-Only Memory
 
 ## Quick Summary
 
-| | Mimir | Mem0 |
+| | Mneme | Mem0 |
 |---|---|---|
 | **Stars** | ~20 | ~55K |
 | **Language** | Rust | Python |
@@ -16,7 +16,7 @@
 | **License** | MIT | Apache 2.0 |
 | **Embeddings** | Optional (Ollama or OpenAI-compatible) | Required (OpenAI default) |
 
-## When to Use Mimir
+## When to Use Mneme
 
 - You want a **single binary** with no infrastructure
 - You need **fully offline** operation (air-gapped, classified environments)
@@ -36,7 +36,7 @@
 
 ## Architecture Differences
 
-### Mimir: Single Binary, No Dependencies
+### Mneme: Single Binary, No Dependencies
 
 ```
 Agent ──MCP stdio── mimir (Rust binary)
@@ -46,7 +46,7 @@ Agent ──MCP stdio── mimir (Rust binary)
                       └── Web dashboard (optional)
 ```
 
-Mimir is a self-contained Rust binary. The SQLite database is a single file.
+Mneme is a self-contained Rust binary. The SQLite database is a single file.
 Install is one `curl | sh`. Nothing else to configure.
 
 ### Mem0: Python + External Services
@@ -63,9 +63,9 @@ The "self-hosted" path still needs PostgreSQL, Qdrant, or Neo4j running.
 
 ## Memory Models
 
-### Mimir: Structured Entities
+### Mneme: Structured Entities
 
-Entities in Mimir have explicit structure:
+Entities in Mneme have explicit structure:
 - **Category + Key**: Namespaced, idempotent storage
 - **Type**: Declared entity type (fact, decision, preference, etc.)
 - **Decay**: Ebbinghaus decay with retrieval boosts
@@ -88,9 +88,9 @@ that works well for straightforward RAG use cases.
 
 ## MCP Tools: 36 vs 5
 
-Mimir exposes 36 MCP tools covering the full memory lifecycle:
+Mneme exposes 36 MCP tools covering the full memory lifecycle:
 
-| Category | Mimir Tools |
+| Category | Mneme Tools |
 |---|---|
 | CRUD | remember, recall, recall_when, get_entity, forget |
 | Graph | link, unlink, traverse |
@@ -108,7 +108,7 @@ Mem0 exposes ~5 tools: add, search, get, get_all, delete.
 
 ## MCP-Native Advantage
 
-Mimir is MCP-native — the binary IS an MCP server. Connect via stdio, SSE, or HTTP:
+Mneme is MCP-native — the binary IS an MCP server. Connect via stdio, SSE, or HTTP:
 
 ```json
 {
@@ -126,21 +126,21 @@ afterthought, not the native interface.
 
 ## Honest Assessment
 
-**Mimir's strengths:**
+**Mneme's strengths:**
 - Zero-dependency deployment (one binary, one file)
 - MCP-native architecture
 - Structured memory model with lifecycle management
 - Encryption at rest
 - Fully offline operation
 - MIT license
 
-**Mimir's weaknesses vs Mem0:**
+**Mneme's weaknesses vs Mem0:**
 - Much smaller community (20 stars vs 55K)
 - Requires Rust toolchain to build from source
 - No managed cloud offering
 - Fewer tutorials and integration examples
 - Binary distribution is less familiar to Python developers
 
-**If you're choosing today:** Pick Mimir if you value simplicity, privacy, and
+**If you're choosing today:** Pick Mneme if you value simplicity, privacy, and
 MCP-native design. Pick Mem0 if you need cloud-managed memory or already have
 a Python/PostgreSQL stack.