EvMem

Documentation · not source

Persistent memory as a computational substrate, not a context buffer

Website · EvSphere

---

What this repository is. Documentation for EvMem — what it does, how it is organised, and what state it is in.

What it is not. This is not the source repository. No implementation code, configuration, prompts or infrastructure lives here, and none will.

---

❓ Why it exists

A session ends. The store does not. Unrelated memories stay inactive while relevant ones participate — the point is not to load more, it is to load less, deliberately.

---

🧩 What it does

• Captures session events as they happen rather than summarising at the end
• Selects which memories are relevant to the current task
• Retains raw information instead of immediately compressing it into semantics
• Retrieves memory nodes in a context-dependent way
• Updates memory as runs complete, so later sessions benefit
• Serves locally with its own configuration boundary

---

🔄 How it fits together

Persistent Memory
        ↓
   Memory Selection          ← what is relevant right now?
        ↓
  Relevant Memory Nodes
        ↓
   Selective Activation      ← only these participate
        ↓
       Reasoning
        ↓
    Memory Update            ← what happened is written back

---

📊 Status

Maturity	In development — see STATUS.md
Version	bundled with 0.7.3
Public page	https://evsphere.vercel.app/evmem

---

⚠️ Known limits

• Not distributed independently — currently reachable only through the EvAgent package
• Closed source; no standalone package or public repository
• Its configuration file holds an API key and a model base URL and must never be committed or captured
• Setup downloads an embedding model of roughly 634 MB
• No public schema documentation; any diagram published is sanitised
• No security or privacy certification is claimed

Full detail, including what is not claimed, is in docs/STATUS.md.

---

📚 Documentation

Document	Covers
ARCHITECTURE.md	Conceptual structure and subsystem responsibilities
docs/HOW-IT-WORKS.md	Stage by stage, and where the boundaries are
docs/STATUS.md	Maturity, requirements and what is not claimed
docs/FAQ.md	Common questions and honest answers
NOTICE.md	What is deliberately absent, and licensing

---

🔗 EvSphere

🌐 Website · GitHub · npm · LinkedIn · X

Machine-readable: llms.txt · llms-full.txt

---

⚖️ Disclosure

Internal implementation detail is not published here. No credential, endpoint, key, dataset or client material is included — see NOTICE.md.

If you find any of those here, it is an error. Report it privately through the enquiry page rather than opening a public issue.