retrieve-memorylisted

# Retrieve Memory Default rule: if you cannot cite a source-of-truth file/doc/ADR from the repo, consult memories first, then proceed. The memory model is documented in [[mem.concept.doctrine.memory-model]]. ## Tool preference If your harness supports MCP tools and doctrine's MCP server is connected (you see `memory_find`, `memory_retrieve`, `memory_show`, `memory_list` in your tool list), **prefer these MCP tools over the CLI**. They return machine-parseable JSON text in the MCP content block without spawning a shell, and `memory_show` enriches results with resolved backlinks. ### Progressive disclosure (MCP pattern) 1. **`memory_find`** — scope-constrained discovery first. Always supply at least one selector (path, glob, tag, type, or free-text query). Metadata only, no bodies. Rows include a `held_back_on_retrieve` flag — do not treat high-risk memories as consumable knowledge. 2. **`memory_retrieve`** — safe context recall for candidates identified in step 1. Trust holdback enforced; low-trust high-severity memories are suppressed automatically. 3. **`memory_show`** — full inspection only when you need the complete picture. Use `view: summary` for token efficiency. Held-back memories carry a warning; do not consume them as knowledge. 4. **`memory_list`** — browse/index only. Prefer scoped `memory_find`. When MCP tools are not available (e.g. in a plain shell environment), fall back to the `doctrine memory` CLI commands described below. ## Two s