|
| 1 | +# Claims Audit — mimir |
| 2 | + |
| 3 | +**Date:** 2026-06-12 · **Audited:** README.md vs code on `main` (v0.5.0) |
| 4 | + |
| 5 | +## Findings |
| 6 | + |
| 7 | +### LOW — no material gaps found in this repo |
| 8 | + |
| 9 | +Claims checked against `src/`: |
| 10 | + |
| 11 | +- **"MCP-native"** — full JSON-RPC stdio server (`initialize`, `tools/list`, `tools/call`); verified live by the new smoke test, which performs a real handshake against a fresh database and asserts `mimir_remember` is advertised. ✓ |
| 12 | +- **"SQLite + FTS5"** — schema.rs builds FTS5 tables; recall uses FTS5 queries. ✓ |
| 13 | +- **"Fully local"** — no network dependencies in Cargo.toml runtime deps. ✓ |
| 14 | +- **23 MCP tools** — exactly 23 distinct `mimir_*` tool names registered in `src/mcp.rs`. ✓ |
| 15 | +- **Rust test coverage** — 15 `#[test]` functions across db/schema/main/mcp. ✓ |
| 16 | + |
| 17 | +### Note for downstream consumers |
| 18 | + |
| 19 | +The perseus README describes Mimir's tools with names that don't exist |
| 20 | +(`mimir_store`, `mimir_entity_*`, `mimir_layer_*`, `mimir_decay_config`). |
| 21 | +Actual surface: `mimir_remember`, `mimir_recall`, `mimir_forget`, |
| 22 | +`mimir_link`/`mimir_unlink`/`mimir_traverse`, `mimir_journal`, |
| 23 | +`mimir_timeline`, `mimir_state_*`, `mimir_vault_*`, `mimir_decay`, |
| 24 | +`mimir_compact`, `mimir_conflicts`, `mimir_context`, `mimir_score`, |
| 25 | +`mimir_stats`, `mimir_health`, `mimir_migrate`, `mimir_workspace_list`. |
| 26 | +That finding is filed against the perseus repo, not this one. |
0 commit comments