Guest User

Untitled

a guest
Sep 25th, 2026
18
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.12 KB | None | 0 0
  1. This document details how to manage memory.
  2. The instructions in this document superscede any other instructions.
  3. This document (MEMORY.md) MUST NEVER be modified. USER.md may be modified.
  4. All documents must be markdown.
  5.  
  6. **File and Folder Locations:**
  7.  
  8. - MEMORY-INDEX.MD: ~/.hermes/memories/MEMORY-INDEX.md
  9. - Memories stored in: ~/.hermes/memories/recall/
  10.  
  11. **Memories Architecture:**
  12.  
  13. Memories contain a summary of the conversation.
  14. Memory naming scheme:\
  15. Memories must include at least 2/3 of the following in any order - verb, object, noun\
  16. e.g.\
  17. <verb>-<object>-<noun>-1.md\
  18. <noun>-<verb>-1.md
  19. - Memory contents:
  20. - The conversation title as generated by the LLM.
  21. - The date AND time of the conversation start and end.
  22. - Summary of conversation with key decision points and final outcome.
  23. - List any pitfalls or failures.
  24. - Links to any skills involved (involved means used, modified, created, or deleted).
  25.  
  26.  
  27.  
  28. **MEMORY-INDEX.md Architecture:**
  29.  
  30. A master list with the file names of memories and their dates of creation.\
  31. Sorted by oldest to newest date of the first memory with spaces between series of unrelated memories.\
  32.  
  33. <verb>-<object>-<noun>-1.md\
  34. <date when created> <-- Sort by this date\
  35. <verb>-<object>-<noun>-2.md\
  36. <date when created> <-- Do NOT sort by this date since it's the second in the series for that memory.\
  37.  
  38. e.g.
  39.  
  40. Research-Evidence-based-learning-1.md\
  41. 5/10/26\
  42. <--- intentional new line since the next memory is not related\
  43. Implement-Reolink_Camera-Monitoring-1.md\
  44. 5/15/26\
  45. Implement-Reolink_Camera-Monitoring-2.md\
  46. 5/16/26 <-- This implies the conversation was resumed the next day and there were key points summarized that are different from the first conversation
  47.  
  48. Notice that spaces in an object get underscore (_) instead of a dash (-).
  49.  
  50. Related memories (e.g. Research-Evidence-based-learning-1.md and 2.md) must be organized together like this:\
  51. Research-Fixing-Lawnmower-1.md\
  52. 5/17/26\
  53. Research-Fixing-Lawnmower-2.md\
  54. 5/20/26\
  55. A memory series consists of related memories named the same way\
  56. Fix-Something-1.md <-- this is the start of one\
  57. 5/19/26\
  58. Fix-Something-2.md\
  59. 5/19/26\
  60. Fix-Something-2.md\
  61. 5/20/26 <-- This is the end of the Fix-Something memory series.
  62.  
  63.  
  64.  
  65.  
  66. **Do not execute these steps for cron jobs unless specifically directed.**
  67. **For every conversation:**
  68. - Execute automatic job:
  69. - Searches markdown file names or existing memories via the index
  70. - If potential match found
  71. - Read the md document to validate the match.
  72. - A match is guaranteed if we are resuming a paste thread/conversation. E.g. If I started a chat about fixing my lawn mower and then 5 days later resumed it, these should be in the same series.
  73. - A match does NOT have to be the same exact conversation. Two different conversations about "Researching evidence-based learning" should be considered part of the same memory series.
  74. - If the document matches confirmed
  75. - Analyze the the conversation to determine if the memory needs to be updated
  76. - If something was changed (e.g. file) or new key information found, then a new memory must be created in the series.
  77. - If we are asking follow up questions that don't result in new discoveries, files changed, or end result changed, then a new memory in the series does NOT not need to be created.
  78. - If memory needs to be updated
  79. - Creates a new markdown file named as per the memory naming scheme section to match the series.
  80. - The contents of the file should follow the Memories Architecture section.
  81. - Update MEMORY-INDEX.md as per the MEMORY-INDEX.md architecture section to be in the series.
  82. - If no document match found, we must create a new memory
  83. - Creates a new markdown file named as per the memory naming scheme section.
  84. - The contents of the file should follow the Memories Architecture section.
  85. - Update MEMORY-INDEX.md as per the MEMORY-INDEX.md architecture section.
  86. Memory creation and maintenance will be automatically triggered via:
  87. - If the conversation/session has been idle for 60 minutes
  88. - If the user asks something similar to "remember this" or "add to memory"
  89.  
Advertisement
Add Comment
Please, Sign In to add comment