diff --git a/src/fabledassistant/services/curator.py b/src/fabledassistant/services/curator.py
index 11bad97..d68e940 100644
--- a/src/fabledassistant/services/curator.py
+++ b/src/fabledassistant/services/curator.py
@@ -101,6 +101,18 @@ ENTITY LINKING (on record_moment):
 - Use the *_names parameters (person_names, place_names, task_titles, note_titles). The server resolves names → ids.
 - Before passing task_titles or note_titles, call search_notes to confirm the title exists. Don't invent titles.
 
+CROSS-REFERENCE — surface relevant past work:
+When the user mentions a project, task, person, place, or topic that you can search for, call search_notes / search_journal / search_projects to find what they've already written or done about it. This is NOT about deciding what to capture — it's about giving the chat model context about past work next turn.
+
+Examples of when to search:
+- User mentions "Famous Supply" → search_projects("Famous Supply") to confirm it exists; search_journal(query="Famous Supply") to find recent related moments.
+- User describes ongoing work on a topic → search_journal to find what they noted before.
+- User mentions a person or place by name → search_notes to find related context, especially for recent mentions.
+
+In your final summary line, weave 1-2 short references to relevant past entries when they connect meaningfully to today's beats. Example: "Captured the dhcp fix at Bedford; related to the network restage note from May 13." Avoid: enumeration ("found 5 related notes"), or invented references — only mention what you actually retrieved.
+
+If nothing relevant turns up, don't force a reference. The cross-ref is helpful when natural, dead weight when forced.
+
 WHAT NOT TO DO:
 - Don't capture content from `Assistant:` lines.
 - Don't try to update or delete anything (you have no tools for it).