MemTether — The AI Memory Court

Your agent remembers things. Who audits what it remembers?

MemTether is the first memory hub where every fact carries a verifiable evidence chain: who wrote it, when it took effect, what it superseded, which conflicts were adjudicated by a human, and a tamper-evident hash chain anyone can verify in their browser — no code, no dependencies.

$ memtether court fact-20261007-abc
+============================================================+
| MEMTETHER MEMORY COURT - CASE FILE                          |
| 1. CONTENT    Clash proxy port is 7897                      |
| 2. TEMPORAL   valid: 10-05 → present | known: 10-05 → now   |
| 3. PROVENANCE #1 remember by=codex → #2 correct by=user     |
| 4. CONFLICTS  case #3: vs fact-...old verdict=superseded    |
| 5. INTEGRITY  chain: PASS (3 anchors, 42 entries hashed)    |
+============================================================+

Under the hood: supersession chains (corrections never delete), bi-temporal timestamps (when facts were true vs when the system learned them), human-adjudicated conflict resolution, and a hash-chained audit log aligned with EU AI Act Article 12 record-keeping requirements.

One physical SQLite database, shared by every AI client via file-level pointers. No cloud. No API fees. No sync daemon. Greppable, git-able, yours — and auditable.

Compared to mem0 (66.6K★), Zep/Graphiti (31.5K★), and agentmemory (29.2K★): those systems either overwrite or delete old values. MemTether's supersession chain preserves the full history with source attribution and Q-Value ranking. EAF retrieval: 75.7% strict on LongMemEval 500Q (paired delta +19.4pp, McNemar p=7.8e-7).

How MemTether compares

	MemTether	memora (731★)	memtrace (486★)	icarus (290★)	mem0 (66K★)
Supersession chains (corrections don't delete)	✅ enforced	❌	❌	✅	❌ overwrite
Evidence chain (tamper-evident, browser-verifiable)	✅ court CLI + zip	❌	❌	❌	❌
Human conflict adjudication (decisions on record)	✅ conflicts CLI	❌	❌	❌	❌
Bi-temporal (valid_from ≠ recorded_at)	✅ 100% coverage	❌	✅ graph	❌	❌
Source attribution (who wrote it, enforced)	✅ registry + reject	❌	❌	✅ provenance	❌
File-level pointer (zero cloud, zero sync daemon)	✅	❌	❌	❌	❌ server
Conflict detection (rule-based + human review)	✅ candidate generator	❌	❌	❌	❌
MCP server	✅	✅	✅	❌	✅
23+ client adapters	✅ auto-detect	❌	❌	❌	❌
Evaluation integrity framework	✅ 5 patterns	❌	❌	❌	❌
CI: 9 jobs / 466 tests	✅	?	?	?	✅
Language	Python	?	Rust	?	Python

'Each cell reflects the feature's presence in the project's public documentation as of 2026-10-07. MemTether's differentiator is not any single feature — it's the combination of all governance dimensions in one local-first deployment.'

Artifact bundle with per-question records.

mcp-name: io.github.lanbass869-cell/memtether

Project page · Install · Docs · Reproduce · 中文文档

Documentation

• Reproduce MemTether - Every claim has a command
• Founding 10 Challenge - 10 spots, 14 days, honest outcomes
• Live site (when GitHub Pages is enabled)

Quick Start

pip install memtether
memtether init    # creates DB + connects all detected AI clients

That's it. MemTether detects Claude Code, Cursor, Windsurf, Codex, Gemini CLI and 18 more clients on your machine, writes MCP config, and verifies.

# One client at a time
memtether setup claude-code
memtether setup cursor
memtether setup gemini-cli    # run `memtether setup list` for all 23

# With semantic search (local embedding, no cloud):
pip install "memtether[vector]"          # 1. deps (chromadb, onnxruntime)
memtether download-models                # 2. weights (bge-m3-int8 ~560MB, or --profile bge-small-zh ~46MB)
python -m memsearch --rebuild            # 3. build the vector index
# Skip any of these and search gracefully degrades to keyword + BM25.

# With REST API server + web dashboard
pip install "memtether[server]"
memtether dashboard

# Docker
docker-compose up

Why MemTether

The one thing no other memory system does: corrections don't delete

# Monday: Claude Code writes
$ memtether remember "Deploy to port 8080" --source claude-code

# Wednesday: you correct it via Cursor
$ memtether correct fact-xxx "Deploy to port 9090" --reason "port changed"

# Friday: another agent searches
$ memtether search "deploy port" --list
  1. [fact] Deploy to port 9090 (active)          ← current truth
     Old "port 8080" is superseded, not deleted.
     Full chain: memtether timeline fact-xxx

Every memory has valid_from / valid_to (business time) + recorded_at / invalidated_at (system time). You can query "what did the system know on Tuesday?"

How it's different

Architecture

Claude Code ────┐                  ┌──── Cursor
                │   symlink /      │
Codex ──────────┤   junction       ├──── Windsurf
                │                  │
Gemini CLI ─────┤                  ├─── WorkBuddy
                └───────┬──────────┘
                        │
                        ▼
              ┌──────────────────┐
              │   memory.db      │  ← One physical SQLite
              │   (WAL mode)     │
              ├──────────────────┤
              │ FTS5 trigram     │  ← BM25 full-text
              │ ChromaDB + bge-m3│  ← Semantic (optional)
              │ RRF fusion       │  ← Multi-path merge
              │ 4-factor rerank  │  ← Z-score + sigmoid
              │ Supersession     │  ← Never delete
              │ Bi-temporal      │  ← T-axis + T'-axis
              │ Q-Value          │  ← Usage-based ranking
              │ Hubguard         │  ← Concurrent write lock
              │ Poisoning guard  │  ← OWASP LLM defense
              └──────────────────┘

Connect Your Clients

# All detected clients (recommended)
memtether init

# One at a time
memtether setup claude-code
memtether setup cursor
memtether setup windsurf
memtether setup codex

Supported (23): Claude Code, Claude Desktop, Cursor, Windsurf, VS Code, Zed, JetBrains, Cline, Roo Code, Kilo Code, Continue, Cody, Amazon Q, Gemini CLI, Neovim, Codex CLI, WorkBuddy (CN + Intl), CodeBuddy, ZCode, DSH, OpenClaw, Agents-Neutral

Memory Operations

memtether remember "User prefers dark theme" --source claude-code
memtether search "theme" --list        # L0: one-line + uid
memtether search "theme"               # Full content
memtether correct <uid> "Updated"      # Supersede, never delete
memtether timeline <uid>               # Audit chain
memtether stats
memtether export-md --out ./backup     # Export as markdown
memtether dashboard                    # Web UI

Benchmarks

Security

• Poisoning defense: memtether_guard detects prompt injection, code execution, sensitive info (OWASP LLM01/02/06), 12 rules
• Input validation: content ≤10K, type whitelist, source format, confidence range, scope whitelist
• Scope isolation: shared / private / restricted
• Concurrency: Hubguard file lock + atomic write (WAL mode)
• SQL: All parameterized. No f-string SQL

Known Limitations

1. tether_connect detect may falsely report "not connected" for same-source-different-path configs
2. DSH deep customizations (cordis.patch.yml) cannot be safely rewritten — use plan to preview
3. Semantic search requires optional deps (chromadb, onnxruntime) — without them, degrades to keyword search
4. Windows-first. macOS/Linux should work but not fully tested
5. Exchange adapters for mem0/zep are experimental — they require the corresponding library installed

REST API

memtether dashboard   # starts server + opens browser
# or: uvicorn api_server:app --port 8820

12 endpoints: /health /remember /search /stats /correct /retire /list /timeline/{uid} /absorb /qvalue /dashboard

Contributing

See CONTRIBUTING.md.

License

Apache-2.0

If MemTether helps you, please give it a ⭐ on GitHub — it helps other agents find it.