memory-guidelisted

# Nanomneme memory Nanomneme is a shared, deterministic SQLite memory store. Memories persist beyond a session and are reused across harness adapters. Use the four native MCP tools below; never write the SQLite database or the `nmnm` CLI output directly. ## The 4Rs - **retain** (`retain_memory`) — save a durable fact, or patch an existing one by `id`. - **recall** (`recall_memory`) — read one memory by `id`. - **retrieve** (`retrieve_memory`) — search or list memories (FTS text `query`, filters). - **remove** (`remove_memory`) — soft-remove by `id` (reversible; purge is CLI-only). ## Project vs global scope For `retain_memory`, omit `scope` for this repository or use `scope: global` for cross-project user information. **Prefer project** unless the fact clearly applies to every project the user works on (e.g. a personal preference or a cross-repo convention). Other tools use optional `store` (`project` or `global`) to choose a physical database. ## When to retain Retain durable, reusable facts: decisions and their rationale, project conventions, user preferences, standing instructions. Do not retain secrets, credentials, routine logs, or transient state. Prefer patching an existing memory (retain with its `id`) over creating a near-duplicate — retrieve first to check. If the project configures `autoretention` in `nmnm.jsonc`, its rules are injected as guidance at session start; `never_persist` rules always win. You remain the only decision maker — nothing is retained w