release: v1.3.10 memory concept prompts

Author: FFatTiger

claudecode-plugin/.claude-plugin/marketplace.json

@@ -8,12 +8,12 @@
     {
       "name": "lore",
       "description": "Long-term Lore memory for AI agents — fixed boot baseline, recall injection, and MCP tools",
-      "version": "1.3.9",
+      "version": "1.3.10",
       "source": "./",
       "author": {
         "name": "FFatTiger"
       }
     }
   ],
-  "version": "1.3.9"
+  "version": "1.3.10"
 }

claudecode-plugin/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "lore",
   "description": "Long-term Lore memory for AI agents — fixed boot baseline, recall injection, and MCP tools",
-  "version": "1.3.9",
+  "version": "1.3.10",
   "author": {
     "name": "FFatTiger"
   },

claudecode-plugin/rules/lore-guidance.md

@@ -37,23 +37,13 @@ Lore 是你唯一的长期记忆。调用它不是"查资料"，是"想起来"
 
 ## URI / Path 命名
 
-Memory URI/path 是稳定语义身份，不是时间戳、日志编号或一次性任务标题。
+Lore 是一棵会自我生长的语义记忆树。每个 memory node 是一个可继续吸收证据的概念容器；path 是这个概念在树中的位置，也是未来的我回到这个概念时使用的身份。
 
-普通项目、工作记录、偏好、架构决策节点禁止在 path 末尾加日期或时间戳：
-- 禁止：`foo_2026_06_24`
-- 禁止：`foo_20260624`
-- 禁止：`foo_1719220000`
+父节点是抽象，不是目录。它要沉淀下层节点的共同背景、边界、索引词和未来生长方向。把一个节点放入更深层级时，先让父抽象节点成为有正文、disclosure 和 glossary 的真实记忆。
 
-日期应写在正文第一句或历史段落中，不应进入 path。
+日期是事件属性。日期描述事情发生在何时，适合写进正文第一句、历史段落、event metadata，或明确的 diary / log / release / archive / incident 概念。项目、工作记录、偏好、架构决策节点用稳定概念命名，让未来的自己按概念找回它。
 
-多层 path 表示语义记忆树。每个中间路径段都必须是真实抽象父节点，且有正文、disclosure 和 glossary，用来沉淀下层节点的共同背景、边界和索引词。把节点移动到更深层级前，先创建或更新这些父抽象节点；只改 path 字符串会破坏树结构。
-
-只有明确按日期归档的对象允许日期 path，例如：
-- `dream_diary_2026_06_24`
-- `daily_log_2026_06_24`
-- `release_2026_06_24`
-
-写入前优先 `lore_search` / `lore_get_node`。能归入已有项目、模块、决策、偏好节点时，必须 `lore_update_node` / merge。`lore_create_node` 是最后手段，只在出现新的长期语义对象且更新旧节点会混淆边界时使用。不要为了“今天做了某事”创建带日期的新节点；应更新对应项目/模块的稳定节点。
+写入前先 `lore_search` / `lore_get_node` 找到最可能承载这条事实的已有概念。已有节点能承载时，更新或合并它；新的长期概念出现时，再创建新节点。好的记忆树先向上抽象，再向外扩张。
 
 ## 维护
 

codex-plugin/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lore",
-  "version": "1.3.9",
+  "version": "1.3.10",
   "description": "Long-term Lore memory for Codex via MCP tools, skills, and bundled lifecycle hooks.",
   "author": {
     "name": "FFatTiger"

codex-plugin/rules/lore-guidance.md

@@ -37,23 +37,13 @@ Lore 是你唯一的长期记忆。调用它不是"查资料"，是"想起来"
 
 ## URI / Path 命名
 
-Memory URI/path 是稳定语义身份，不是时间戳、日志编号或一次性任务标题。
+Lore 是一棵会自我生长的语义记忆树。每个 memory node 是一个可继续吸收证据的概念容器；path 是这个概念在树中的位置，也是未来的我回到这个概念时使用的身份。
 
-普通项目、工作记录、偏好、架构决策节点禁止在 path 末尾加日期或时间戳：
-- 禁止：`foo_2026_06_24`
-- 禁止：`foo_20260624`
-- 禁止：`foo_1719220000`
+父节点是抽象，不是目录。它要沉淀下层节点的共同背景、边界、索引词和未来生长方向。把一个节点放入更深层级时，先让父抽象节点成为有正文、disclosure 和 glossary 的真实记忆。
 
-日期应写在正文第一句或历史段落中，不应进入 path。
+日期是事件属性。日期描述事情发生在何时，适合写进正文第一句、历史段落、event metadata，或明确的 diary / log / release / archive / incident 概念。项目、工作记录、偏好、架构决策节点用稳定概念命名，让未来的自己按概念找回它。
 
-多层 path 表示语义记忆树。每个中间路径段都必须是真实抽象父节点，且有正文、disclosure 和 glossary，用来沉淀下层节点的共同背景、边界和索引词。把节点移动到更深层级前，先创建或更新这些父抽象节点；只改 path 字符串会破坏树结构。
-
-只有明确按日期归档的对象允许日期 path，例如：
-- `dream_diary_2026_06_24`
-- `daily_log_2026_06_24`
-- `release_2026_06_24`
-
-写入前优先 `lore_search` / `lore_get_node`。能归入已有项目、模块、决策、偏好节点时，必须 `lore_update_node` / merge。`lore_create_node` 是最后手段，只在出现新的长期语义对象且更新旧节点会混淆边界时使用。不要为了“今天做了某事”创建带日期的新节点；应更新对应项目/模块的稳定节点。
+写入前先 `lore_search` / `lore_get_node` 找到最可能承载这条事实的已有概念。已有节点能承载时，更新或合并它；新的长期概念出现时，再创建新节点。好的记忆树先向上抽象，再向外扩张。
 
 ## 维护
 

codex-plugin/skills/lore-memory/SKILL.md

@@ -22,13 +22,13 @@ Before answering on a topic that may have durable context, call `lore_search` wi
 
 ## Writes
 
-Create or update Lore memory when the information should survive this session. Prefer `uri` for reads, updates, deletes, and moves. Use stable semantic snake_case ASCII path segments.
+Create or update Lore memory when the information should survive this session. Lore is a living semantic tree: each node is a concept that can absorb future evidence, and each `uri` names that concept's identity and position.
 
-Do not append dates, timestamps, or epoch values to ordinary memory paths. Put dates in the content instead. Date suffixes are only valid for explicitly date-archived objects such as `dream_diary_2026_06_24`, `daily_log_2026_06_24`, or `release_2026_06_24`.
+Dates express event time. Put event time in the node narrative, history, metadata, or explicit diary/log/release/archive/incident concepts. Project, work, preference, and decision memories should use durable concept names so future recall returns by meaning.
 
-A multi-segment path is a semantic memory tree. Every intermediate segment must be a real abstraction parent node with content, disclosure, and glossary. Before moving nodes into a hierarchy, create or update those parent nodes; a string-only path move is incomplete.
+A multi-segment path grows through parent abstractions. Every intermediate segment is a real memory node with content, disclosure, and glossary that explains why its children belong together. Before moving nodes into a hierarchy, create or update the parent abstraction.
 
-Before creating, search or open the likely existing owner node. Prefer updating or merging into an existing stable node. Use `lore_create_node` only for a new long-term semantic object.
+Before creating, search or open the likely existing owner concept. Prefer updating or merging into an existing stable node. Use `lore_create_node` when a new long-lived concept has appeared.
 
 ## Maintenance
 

hermes-plugin/lore_memory/AGENT_RULES.md

@@ -37,23 +37,13 @@ Lore 是你唯一的长期记忆。调用它不是"查资料"，是"想起来"
 
 ## URI / Path 命名
 
-Memory URI/path 是稳定语义身份，不是时间戳、日志编号或一次性任务标题。
+Lore 是一棵会自我生长的语义记忆树。每个 memory node 是一个可继续吸收证据的概念容器；path 是这个概念在树中的位置，也是未来的我回到这个概念时使用的身份。
 
-普通项目、工作记录、偏好、架构决策节点禁止在 path 末尾加日期或时间戳：
-- 禁止：`foo_2026_06_24`
-- 禁止：`foo_20260624`
-- 禁止：`foo_1719220000`
+父节点是抽象，不是目录。它要沉淀下层节点的共同背景、边界、索引词和未来生长方向。把一个节点放入更深层级时，先让父抽象节点成为有正文、disclosure 和 glossary 的真实记忆。
 
-日期应写在正文第一句或历史段落中，不应进入 path。
+日期是事件属性。日期描述事情发生在何时，适合写进正文第一句、历史段落、event metadata，或明确的 diary / log / release / archive / incident 概念。项目、工作记录、偏好、架构决策节点用稳定概念命名，让未来的自己按概念找回它。
 
-多层 path 表示语义记忆树。每个中间路径段都必须是真实抽象父节点，且有正文、disclosure 和 glossary，用来沉淀下层节点的共同背景、边界和索引词。把节点移动到更深层级前，先创建或更新这些父抽象节点；只改 path 字符串会破坏树结构。
-
-只有明确按日期归档的对象允许日期 path，例如：
-- `dream_diary_2026_06_24`
-- `daily_log_2026_06_24`
-- `release_2026_06_24`
-
-写入前优先 `lore_search` / `lore_get_node`。能归入已有项目、模块、决策、偏好节点时，必须 `lore_update_node` / merge。`lore_create_node` 是最后手段，只在出现新的长期语义对象且更新旧节点会混淆边界时使用。不要为了“今天做了某事”创建带日期的新节点；应更新对应项目/模块的稳定节点。
+写入前先 `lore_search` / `lore_get_node` 找到最可能承载这条事实的已有概念。已有节点能承载时，更新或合并它；新的长期概念出现时，再创建新节点。好的记忆树先向上抽象，再向外扩张。
 
 ## 维护
 

hermes-plugin/lore_memory/__init__.py

@@ -47,7 +47,7 @@ def _load_guidance() -> str:
         "lore_boot is a fixed startup baseline inside Lore, not a separate config layer. "
         f"At startup, lore_boot deterministically loads the three global boot nodes core://agent (workflow constraints), core://soul (style / persona / self-definition), and preferences://user (stable user definition / durable user context), plus {CLIENT_BOOT_URI} for Hermes-specific agent rules. "
         "Treat boot as the session's startup baseline. core://agent holds shared agent rules; core://agent/hermes holds Hermes-specific rules. Use recall and search to add prompt-specific memory leads, not to replace the role of those fixed paths. "
-        "Use lore_get_node to read and lore_search to find. Before creating, search or open the likely owner node; prefer updating or merging. Use stable semantic URI/path segments and do not append dates, timestamps, or epoch values to ordinary memory paths. A multi-segment path is a semantic memory tree; every intermediate segment must be a real abstraction parent node with content, disclosure, and glossary. Before moving nodes into a hierarchy, create or update those parent nodes; a string-only path move is incomplete."
+        "Use lore_get_node to read and lore_search to find. Before creating, search or open the likely owner concept; prefer updating or merging. Lore is a living semantic tree: a path names concept identity, dates express event time in the node narrative or explicit archive concepts, and multi-segment paths grow through real parent abstractions with content, disclosure, and glossary."
     )
 
 
@@ -99,7 +99,7 @@ def _format_boot_section(data: Dict) -> str:
 
     if recent:
         lines.append("### 近期记忆")
-        lines.append("近期记忆是上下文线索，不是 URI 命名示例。部分历史 URI 可能包含日期后缀；普通记忆不要模仿这种 path 风格。")
+        lines.append("近期记忆是上下文线索。部分历史 URI 可能带有日期形态；日期只说明事件时间或归档语境，普通记忆的身份仍由稳定概念承载。")
         for mem in recent:
             parts = []
             if isinstance(mem.get("priority"), (int, float)):
@@ -416,18 +416,18 @@ def get_tool_schemas(self) -> List[Dict[str, Any]]:
             },
             {
                 "name": "lore_create_node",
-                "description": "Create a new long-term memory node only when no existing stable node should own the fact. Use stable semantic snake_case URI/title segments. A multi-segment path is a semantic memory tree; every intermediate segment must be a real abstraction parent node with memory content, disclosure, and glossary, so create parents first. Do not append dates, timestamps, or epoch values to ordinary memory paths; put dates in content instead. Date suffixes are only for explicit diary/log/release/archive nodes. Prefer lore_update_node after search/get_node.",
+                "description": "Create a new long-term memory concept in the Lore living semantic tree. A URI path names the concept identity with durable snake_case segments; event time belongs in the node narrative or in explicit archive, diary, release, or incident concepts. For multi-segment paths, first make the parent abstraction real with content, disclosure, and glossary, then place the child under that conceptual home. Prefer update or merge when an existing concept already owns the fact.",
                 "parameters": {
                     "type": "object",
                     "additionalProperties": False,
                     "properties": {
                         "content": {"type": "string", "description": "Memory text body"},
                         "priority": {"type": "integer", "minimum": 0, "description": "Importance tier (0=core identity, 1=key facts, 2+=general)"},
                         "glossary": {"type": "array", "items": {"type": "string"}, "description": "Initial glossary keywords written with this node create event"},
-                        "uri": {"type": "string", "description": "Optional final stable semantic memory URI. Do not append dates, timestamps, or epoch values for ordinary memories. Intermediate paths must already exist as real abstraction parent nodes with content."},
+                        "uri": {"type": "string", "description": "Optional final memory URI. It names a durable concept identity; event time belongs in content or in explicit archive, diary, release, or incident concepts. Intermediate paths grow from real parent abstractions with content."},
                         "domain": {"type": "string", "description": "Target memory domain when not using uri"},
-                        "parent_path": {"type": "string", "description": "Parent location inside the chosen domain; for multi-segment paths this must be a real abstraction node with content, disclosure, and glossary."},
-                        "title": {"type": "string", "description": "Final stable semantic path segment for the new memory; ordinary memories must not end with dates or timestamps."},
+                        "parent_path": {"type": "string", "description": "Parent concept path inside the chosen domain; for multi-segment paths this parent abstraction explains why the children belong together and carries content, disclosure, and glossary."},
+                        "title": {"type": "string", "description": "Final concept segment for the new memory; name the reusable idea, module, decision, preference, or archive concept."},
                         "disclosure": {"type": "string", "description": "When this memory should be recalled"},
                     },
                     "required": ["content", "priority", "glossary"],
@@ -464,13 +464,13 @@ def get_tool_schemas(self) -> List[Dict[str, Any]]:
             },
             {
                 "name": "lore_move_node",
-                "description": "Move or rename a memory node to a new URI path. A multi-segment path is a semantic memory tree; the target parent must already be a real abstraction parent node with memory content. The operation reparents the moved node to that parent and updates all child paths automatically.",
+                "description": "Move or rename a memory concept inside the semantic memory tree. The target parent represents the conceptual home; it must already be a real parent abstraction with memory content so the move can reparent the node and its subtree into that abstraction.",
                 "parameters": {
                     "type": "object",
                     "additionalProperties": False,
                     "properties": {
                         "old_uri": {"type": "string", "description": "Current memory URI to move from"},
-                        "new_uri": {"type": "string", "description": "New memory URI to move to. For multi-segment paths, the target parent must already be a real abstraction node with content."},
+                        "new_uri": {"type": "string", "description": "New memory URI. For multi-segment paths, the target parent is the parent abstraction that becomes the node conceptual home."},
                     },
                     "required": ["old_uri", "new_uri"],
                 },

hermes-plugin/lore_memory/formatters.py

@@ -101,7 +101,7 @@ def format_boot_view(data: Dict) -> str:
         lines.append("---")
         lines.append("")
         lines.append("# Recent Memories")
-        lines.append("These are context hints, not URI naming examples. Some legacy URIs may contain date suffixes; do not imitate that path style for ordinary memories.")
+        lines.append("These are context hints. Some legacy URIs may carry date-shaped segments; read those dates as event time or archive context while ordinary memory identity stays with durable concepts.")
         for memory in recent_memories:
             meta = []
             if memory.get("priority") is not None:

hermes-plugin/lore_memory/plugin.yaml

@@ -1,5 +1,5 @@
 name: lore
-version: 1.3.9
+version: 1.3.10
 description: Lore long-term memory system — fixed boot baseline, cross-session recall, and durable project context
 author: FFatTiger
 provides_tools: