memory

# Memory Use maintained experience only when it helps an actual task. Memory is optional: no mandatory recall at RPI entry, lesson at completion, worksheet, page quota or background mining. A trivial edit can proceed directly to implementation. ## Choose one operation | Need | Read on demand | |---|---| | An earlier constraint or source map may change the next action | [Find / recall](references/recall.md) | | Capture useful evidence from selected sources, episodes or corrections | [Capture / mine / learn](references/mine-learn.md) | | Update, qualify, consolidate or retire a supported claim | [Curate / qualify / retire](references/curate.md) | | Find repeated operational friction in supplied history | [Toil evidence](#toil-evidence) | Memory owns these find, capture and curate operations; other roles link here instead of maintaining their own procedures. Capture/mine/learn includes bounded source maps, verdicts, corrections and failed or harmful reuse; it is not a required completion step. The optional [OKF page profile](references/learn/okf-page-profile.md) checks structure only. Do not load every operation reference just because Memory was selected. ## One authority per fact BD or the caller's tracker owns work/status/dependencies/handoffs; Git owns content and delivery history; native sessions and CASS own episode evidence. Caller-selected reviewed Markdown topic pages hold reusable claims in a project `.context/` or an external bundle. These are evidence, not anoth...