record-memorylisted

# Record Memory Conversation context does not persist. When knowledge would save a future agent meaningful time, write a memory record immediately. Phase and slice wrap-up are mandatory prompts: scan `notes.md`, the active runtime phase sheet, audit findings, and fresh gotchas for durable guidance worth keeping. Promote only durable guidance — repeatable workflows, sharp edges, invariants, subsystem facts. Not conversational state. ## 1. Choose the narrowest type that fits `fact` (atomic checkable truth) · `pattern` (repeatable recipe / command sequence) · `system` (subsystem map + pointers, not a spec) · `concept` (stable mental model / terminology) · `signpost` ("start here" navigation) · `thread` (short-lived working set, expires fast). ⚠ **A `thread` is hidden from `find`/`retrieve` until verified** (SL-008 D6, §5). If you want a working loop to resurface by scope, prefer a durable type (`pattern`/`system`/`concept`) — or record the `thread` and `verify` it on a clean tree. An unverified thread shows only in `list`/`show`, never in scope ranking. ## 2. Record it Record with `doctrine memory record` (ask `--help` for the flags; see `using-doctrine.md` for the verb model). It scaffolds a TOML + body under `.doctrine/memory/items/`; the **born git anchor is captured automatically** — do not hand-author it. ### After recording **Suggested relations.** `record` emits suggested relations on stderr when it detects high-confidence matches against existing memories. Revie