# Evaluate what memory retrieves, not just what it stores

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Evaluate what memory retrieves, not just what it stores

ID: MHC-D-RESEARCH-0705 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/evaluate-what-memory-retrieves-not-just-what-it-stores

A perfect archive can still produce a bad working memory.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- A memory-enabled agent still misses old findings or fills context with irrelevant notes.

### Avoid when

- Recall targets can overfit known questions; periodically add new tasks and audit whether the retrieval policy generalizes.

### Explanation

Create recall tests from real tasks: which stored items should appear, which should stay out, and how high the important item should rank. Measure misses and distracting over-recall separately. When a task fails, inspect whether the needed fact was absent from storage, retrieved poorly or ignored after retrieval; those are different failures.

### Steps

1. Memory quality has a task-level recall and noise test, not only a count of saved items.

### Example

For a recurring customer migration, test whether the agent retrieves the current mapping exception without also loading months of unrelated status notes.

### Check

Memory quality has a task-level recall and noise test, not only a count of saved items.

### Limits

- Recall targets can overfit known questions; periodically add new tasks and audit whether the retrieval policy generalizes.

### Evidence and sources

- supports: The same memory-harness work argues that retrieval ranking and recall policy can determine whether stored memory helps or wastes context. — RS-25CBF175E2E4C6CF. Results come from a particular research-agent experiment and should be re-tested locally. (Bad memory spends tokens in the wrong direction; recall policy as evaluation target)
- RS-25CBF175E2E4C6CF: Memory Harnesses for Long-Running Research Agents — https://ai.engineer/talks/R3-anFK1YM8-memory-harnesses-long-running-research-agents

No review details supplied.
