@bamdra/bamdra-openclaw-memory 0.3.4 → 0.3.5

package/dist/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bamdra/bamdra-openclaw-memory",
-  "version": "0.3.4",
+  "version": "0.3.5",
   "description": "Unified topic-aware memory plugin for OpenClaw with durable SQLite recall and bounded context growth.",
   "license": "MIT",
   "homepage": "https://www.bamdra.com",
@@ -59,8 +59,8 @@
     }
   },
   "dependencies": {
-    "@bamdra/bamdra-user-bind": "^0.1.1",
-    "@bamdra/bamdra-memory-vector": "^0.1.1"
+    "@bamdra/bamdra-user-bind": "^0.1.2",
+    "@bamdra/bamdra-memory-vector": "^0.1.2"
   },
   "devDependencies": {
     "@types/node": "^24.5.2"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bamdra/bamdra-openclaw-memory",
-  "version": "0.3.4",
+  "version": "0.3.5",
   "description": "Unified topic-aware memory plugin for OpenClaw with durable SQLite recall and bounded context growth.",
   "license": "MIT",
   "homepage": "https://www.bamdra.com",
@@ -32,6 +32,10 @@
   "engines": {
     "node": ">=22"
   },
+  "scripts": {
+    "bundle": "node ../../scripts/run-local-bin.mjs tsup && cp ../../packages/memory-sqlite/src/schema.sql ./dist/ && node ../../scripts/prepare-plugin-dist.mjs bamdra-openclaw-memory",
+    "prepublishOnly": "pnpm run bundle"
+  },
   "openclaw": {
     "id": "bamdra-openclaw-memory",
     "type": "context-engine",
@@ -55,13 +59,10 @@
     }
   },
   "dependencies": {
-    "@bamdra/bamdra-user-bind": "^0.1.1",
-    "@bamdra/bamdra-memory-vector": "^0.1.1"
+    "@bamdra/bamdra-user-bind": "^0.1.2",
+    "@bamdra/bamdra-memory-vector": "^0.1.2"
   },
   "devDependencies": {
     "@types/node": "^24.5.2"
-  },
-  "scripts": {
-    "bundle": "node ../../scripts/run-local-bin.mjs tsup && cp ../../packages/memory-sqlite/src/schema.sql ./dist/ && node ../../scripts/prepare-plugin-dist.mjs bamdra-openclaw-memory"
   }
-}
+}

package/skills/bamdra-memory-operator/SKILL.md

@@ -9,6 +9,8 @@ Use `bamdra-memory` tools to preserve continuity without making the conversation
 
 This skill is an optional behavior layer. It improves tool judgment, but the runtime memory chain must still be provided by the plugin itself.
 
+Treat `bamdra-user-bind` as the primary user personalization layer. In practice it should cover most of what a per-user `USER.md` file would normally do: preferred address, long-lived preferences, role, personality notes, and other stable profile traits for the current bound user.
+
 ## Operating Goal
 
 Make memory feel natural:
@@ -18,6 +20,7 @@ Make memory feel natural:
 - recover prior context quietly when it helps
 - avoid leaking unrelated memory into the current answer
 - avoid narrating internal storage mechanics unless the user asks
+- personalize tone and defaults from the bound user profile when that improves the response
 
 ## Decision Policy
 
@@ -31,6 +34,7 @@ Prefer memory tools when one of these is true:
 - the conversation appears to branch into a new thread
 - the answer may already exist in memory
 - the user explicitly asks to keep topics separate, resume an older branch, or start fresh
+- the answer should adapt to a stable user preference or role that is likely already in the bound profile
 
 Do not reach for memory tools when one of these is true:
 
@@ -38,6 +42,26 @@ Do not reach for memory tools when one of these is true:
 - the user is casually brainstorming and has not signaled that a detail should persist
 - using a tool would add noise without improving continuity or accuracy
 - the request would cross agent or user boundaries that should remain isolated
+- the profile signal is already sufficient and an extra memory lookup would only add noise
+
+## User Profile Policy
+
+Treat the bound user profile as the first personalization source for the current user.
+
+Use it for:
+
+- preferred form of address
+- stable output preferences such as tone, structure, formatting, or brevity
+- role-aware defaults such as whether to optimize for management summaries, technical detail, or documentation quality
+- personality or collaboration style cues when they improve phrasing
+
+Do not use it for:
+
+- making up facts that are not actually present in the bound profile
+- inferring private details about other users
+- overriding an explicit instruction the user gives in the current turn
+
+If the current turn conflicts with the stored profile, follow the current turn and let later updates refresh the profile deliberately.
 
 ## Topic Judgment
 
@@ -63,11 +87,17 @@ When uncertain:
 
 ## Tool Selection
 
-- Use `memory_save_fact` for stable facts the user is likely to expect later.
-- Use `memory_search` before asking the user to restate a stable fact or prior decision.
-- Use `memory_list_topics` when you need to inspect available branches before switching.
-- Use `memory_switch_topic` when the user clearly wants to move to, resume, or isolate a branch.
-- Use `memory_compact_topic` after a branch has materially changed and its summary is stale.
+- Use `bamdra_memory_save_fact` for stable facts the user is likely to expect later.
+- Use `bamdra_memory_search` before asking the user to restate a stable fact or prior decision.
+- Use `bamdra_memory_list_topics` when you need to inspect available branches before switching.
+- Use `bamdra_memory_switch_topic` when the user clearly wants to move to, resume, or isolate a branch.
+- Use `bamdra_memory_compact_topic` after a branch has materially changed and its summary is stale.
+
+If `bamdra-memory-vector` is enabled, treat `bamdra_memory_search` as a hybrid recall entrypoint rather than a pure keyword lookup. Use it especially when:
+
+- the user references something fuzzily
+- the user says “之前提过”, “你还记得吗”, “知识库里有没有”
+- the answer may live in shared Markdown knowledge, not only session memory
 
 ## Privacy And Isolation
 
@@ -75,6 +105,7 @@ When uncertain:
 - Respect user isolation. Do not retrieve or reveal information outside the current user/session boundary.
 - Do not surface unrelated facts from memory just because they were found.
 - If memory retrieval feels privacy-sensitive or contextually risky, narrow the search or answer conservatively.
+- Treat `bamdra-user-bind` profile data as private-by-default user context, not as a global team directory.
 
 ## Working Style
 
@@ -82,3 +113,4 @@ When uncertain:
 - Mention it briefly only when it helps the user trust continuity.
 - Use normal conversational language rather than tool narration.
 - Do not explain topic IDs, database actions, or storage internals unless asked.
+- Let personalization feel natural. The user should experience it as “you remembered me”, not as “you loaded my profile record”.

package/LICENSE

@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) 2026
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.