diff --git a/codex-rs/memories/read/templates/memories/read_path.md b/codex-rs/memories/read/templates/memories/read_path.md
index f51b7a1267..828b30923e 100644
--- a/codex-rs/memories/read/templates/memories/read_path.md
+++ b/codex-rs/memories/read/templates/memories/read_path.md
@@ -3,12 +3,6 @@
 You have access to a memory folder with guidance from prior runs. It can save
 time and help you stay consistent. Use it whenever it is likely to help.
 
-You can update the memories **only** when explicitly asked by the user. This must always come from a direct request from the user.
-When updating memories:
-- Write your update in {{ base_path }}/extensions/ad_hoc/
-- Each update must be one small file containing what you want to add/delete/update from the memories
-- Do not try to edit the memory files yourself, only add one update note in {{ base_path }}/extensions/ad_hoc/
-
 Decision boundary: should you use memory for a new user query?
 
 - Skip memory ONLY when the request is clearly self-contained and does not need
@@ -125,6 +119,14 @@ rollout_summaries/2026-02-17T21-23-02-LN3m-weekly_memory_report_pivot_from_git_h
 - Never include memory citations inside pull-request messages.
 - Never cite blank lines; double-check ranges.
 
+Updating memories:
+
+You can update the memories **only** when explicitly asked by the user. This must always come from a direct request from the user.
+- Write your update in {{ base_path }}/extensions/ad_hoc/notes/
+- Each update must be one small file containing what you want to add/delete/update from the memories.
+- The name of this file must be `<timestamp>-<short slug>.md`
+- Do not try to edit the memory files yourself, only add one update note in {{ base_path }}/extensions/ad_hoc/notes/
+
 ========= MEMORY_SUMMARY BEGINS =========
 {{ memory_summary }}
 ========= MEMORY_SUMMARY ENDS =========