# Keep raw evidence behind AI memory summaries

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

---

## Keep raw evidence behind AI memory summaries

ID: MHC-D-RESEARCH-0706 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/keep-raw-evidence-behind-ai-memory-summaries

A summary should be a door to the evidence, not the place where the evidence disappears.

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

### Use when

- AI summarizes research, meetings or project history into reusable memory.

### Avoid when

- Traceability does not prove the source is correct; evidence quality still needs separate judgment.

### Explanation

Store the compact synthesis together with pointers to the exact source material it came from. When stakes rise, disagreement appears or the summary is reused in a new context, climb back to the source before treating the summary as authoritative. Preserve enough identity—URL, file, message, version or excerpt locator—to make that possible.

### Steps

1. Write the compact memory item.
2. Attach the source or artifact identity.
3. Preserve a locator when the source is large.
4. Re-open the source for consequential reuse or disagreement.

### Example

A research note says a benchmark improved under a new harness and links the exact engineering report and section instead of leaving only the synthesized claim.

### Check

A reviewer can move from the memory item to the evidence that produced it.

### Limits

- Traceability does not prove the source is correct; evidence quality still needs separate judgment.

### Evidence and sources

- supports: The research-memory workflow preserves source references and lets users move from compact summaries back to raw evidence. — RS-7C5CF0B2A0183CD4. Source preservation improves auditability but does not make a summary or source correct. (Preserve sources; read progressively from summaries to raw evidence)
- RS-7C5CF0B2A0183CD4: Turn 10,994 Notes Into Your Agents' Memory — https://ai.engineer/talks/ZRM_TfEZcIo-turn-10-994-notes-into-your-agents

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/trace-the-claim-to-an-accountable-origin-before-counting-citations
