Overview
MeMex Zero-RAG (JPeetz) is a specialized LLM Wiki implementation with a zero-hallucination enforcement architecture. It uses an L1/L2 design and quarantines pages with >20% unsourced content — a hard provenance guarantee. It contributes the “Quarantine” lifecycle state used in the comprehensive report’s page-lifecycle model.
Key Facts
- Innovation: zero-hallucination enforcement via quarantine
- Architecture: L1/L2 tiers
- Provenance rule: pages with >20% unsourced material are quarantined, not published
- Part of the Tier 3 specialized implementations in the comprehensive report
- License: MIT
Features
Core Architecture
- Zero-RAG design — no embeddings, no vector databases, no infrastructure; just markdown + git + LLM
- L1/L2 cache architecture — L1 (private, git-ignored: identity, rules, credentials) + L2 (versioned wiki, shareable)
- LLM-agnostic — works with Claude, GPT, Gemini, Llama, Codex, any agent that reads/writes files
- Git-native — full version history, branching, rollback; multi-agent via worktrees
Ingest & Processing
- CLI ingestion —
memex ingest paper.pdf,memex ingest https://example.com - Multi-format support — PDF, markdown, web pages via CLI
- Agent-driven compile — LLM reads sources and builds structured wiki pages
Quality & Governance
- Zero hallucination protocol — every claim must cite a source; unsourced = lint error
- Quarantine mode — pages with >20% unsourced claims get
status: quarantine - Conflict resolution — LLM flags contradictions in contradictions.md, pauses for human decision
- Confidence tracking — per-claim certainty scores, lifecycle states (draft/active/stale/quarantine)
- GitHub Actions — broken links, missing citations, orphan pages checked on every PR
MCP / Tools
- MCP server — 12 tools: wiki_search, wiki_read, wiki_read_by_slug, wiki_list, wiki_query, wiki_write, wiki_flag, wiki_revalidate, wiki_ingest, wiki_lint, wiki_graph, wiki_stats
- SSE transport — remote/multi-agent access via uvicorn + starlette
- Lifecycle management — wiki_flag (quarantine), wiki_revalidate (confirm/update/retire)
Knowledge Graph
- Optional force-directed graph — vis-network visualization of all wikilinks
- Type-coded nodes — entities, concepts, sources, synthesis with legend
- Live search with highlight in graph view
Integration
- Claude Code, Cursor, Codex, OpenClaw — works with any MCP-compatible agent
- Obsidian compatible — wiki works as Obsidian vault from day one
- CLI tooling — memex ingest/search/lint/graph/serve commands
Data & Storage
- Markdown files + git — no databases, no APIs, no infrastructure
- Session distillation — agent transcripts converted to structured markdown for ingest
- Page lifecycle — status field (draft/active/stale/quarantine) for knowledge lifecycle management
Relationships
- llm-wiki — implemented-by: specialized, opinionated implementation
- open-knowledge-format — extends: its quarantine rule is a stricter local governance than OKF’s consumer tolerance
- lint — extends: quarantine is an automated extension of the lint/health pass
- memory-lifecycle — influenced: its L1/L2 tiers inform the page-lifecycle (Draft→Reviewed→Verified→Stale→Archived→Quarantine)
Implications
MeMex addresses the exact risk the user cares about: knowledge that looks real but isn’t sourced. Its >20% quarantine threshold is a concrete provenance control this vault could adopt in its own lint rules.
External Links
- Repository: https://github.com/JPeetz/MeMex-Zero-RAG
Não confunda com
Este projeto compartilha o nome “memex” com outros dois do ecossistema, mas são coisas diferentes:
- ai-memex-cli — é uma CLI dual-vault com destilação de sessão, não tem regra de zero-hallucination.
- wastedcode-memex — é um runtime daemonizado em Go, não uma implementação de wiki com quarantena.