@unblocklabs/unblock-memory 0.2.4 → 0.2.5

package/README.md

@@ -47,16 +47,21 @@ directories, or globs into named corpora:
               kind: "files",
               paths: ["MEMORY.md", "USER.md", "memory/**/*.md"],
             },
-            {
-              name: "projects",
-              kind: "files",
-              paths: ["/absolute/shared/**/*.md"],
-            },
             {
               name: "sessions",
               kind: "sessions",
               chatTypes: ["channel", "group"],
             },
+            {
+              name: "canon",
+              kind: "files",
+              paths: ["knowledge/canon/**/*.md"],
+            },
+            {
+              name: "reflections",
+              kind: "files",
+              paths: ["knowledge/reflections/**/*.md"],
+            },
           ],
           // Optional: omit unless the local analysis worker is installed.
           analysis: {
@@ -80,7 +85,7 @@ context resident after first use. Set it to `false` to restore QMD's five-minute
 idle unload behavior.
 
 `memory_search` searches every configured corpus by default. Pass
-`corpora: ["projects"]` to search selected corpora or `corpora: ["all"]` to
+`corpora: ["canon"]` to search selected corpora or `corpora: ["all"]` to
 request all of them explicitly. Search results include their corpus name and
 remain readable by passing the returned `qmd://` path to `memory_get`.
 
@@ -181,5 +186,50 @@ A failed rebuild leaves the stale result intact, while a successful rebuild
 atomically replaces it. Analysis is never scheduled automatically. If the worker
 is absent or fails, `memory_search` and `memory_get` continue to work.
 
+## Curating canon and reflections
+
+The plugin bundles the `memory-curator` skill for turning useful clusters into
+durable knowledge. It becomes available when the plugin is enabled. If the
+agent has an explicit skill allowlist, include `memory-curator`.
+
+Keep curated files outside `memory/**` so each file belongs to only one corpus:
+
+```text
+knowledge/
+├── canon/
+│   └── gateway-restarts.md
+└── reflections/
+    └── 2026-08-26.md
+```
+
+Canon files are stable topic files updated in place. Each one contains only the
+current affirmative rule or understanding, its update time, current rationale,
+and `qmd://` evidence links. Do not include old procedures, changelogs, or a
+`Supersedes` section: semantic chunking may retrieve those passages without the
+surrounding warning that they are obsolete.
+
+Reflection files are daily or timestamped and append-oriented. They hold useful
+patterns, hypotheses, contradictions, and uncertainty, but are not
+authoritative. Both corpora participate in later search and clustering, so a
+later run can reconsider prior reasoning. Repeated derived text is not
+independent corroboration; durable canon still needs underlying source evidence.
+
+For a manual run, ask the agent:
+
+```text
+Use $memory-curator to review my memory clusters and curate any durable updates.
+```
+
+For recurring curation, use an OpenClaw automation with the same thin message:
+
+```text
+Use $memory-curator to run the scheduled memory curation cycle.
+```
+
+The skill lists current clusters, reclusters only when analysis is missing or
+stale, follows representative sources with `memory_get`, and may correctly
+write nothing. Its own writes are indexed for the next cycle; it does not
+recluster recursively in the same run.
+
 Existing `unblock-qmd` indexes are derived caches and may be left in place;
 Unblock Memory rebuilds its own index from configured corpora.

package/openclaw.plugin.json

@@ -1,10 +1,11 @@
 {
   "id": "unblock-memory",
   "name": "Unblock Memory",
-  "version": "0.2.4",
+  "version": "0.2.5",
   "description": "Indexes, retrieves, and analyzes configured workspace memory with existing QMD vectors.",
   "kind": "memory",
   "activation": { "onStartup": false },
+  "skills": ["./skills"],
   "contracts": { "tools": ["memory_search", "memory_get", "memory_sync_sessions", "memory_sync_status", "memory_recluster", "memory_list_clusters", "memory_fetch_cluster"] },
   "toolMetadata": {
     "memory_sync_sessions": { "sideEffecting": true },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@unblocklabs/unblock-memory",
-  "version": "0.2.4",
+  "version": "0.2.5",
   "description": "Workspace-native memory for OpenClaw, powered by QMD",
   "type": "module",
   "license": "MIT",
@@ -18,7 +18,7 @@
     "access": "public",
     "provenance": true
   },
-  "files": ["dist", "README.md", "openclaw.plugin.json"],
+  "files": ["dist", "skills", "README.md", "openclaw.plugin.json"],
   "scripts": {
     "build": "tsc -p tsconfig.build.json",
     "typecheck": "tsc -p tsconfig.json --noEmit",

package/skills/memory-curator/SKILL.md

@@ -0,0 +1,78 @@
+---
+name: memory-curator
+description: Review Unblock Memory clusters and turn supported current knowledge into canon or exploratory reasoning into reflections.
+---
+
+# Memory Curator
+
+Use Unblock Memory's semantic clusters to maintain durable workspace knowledge.
+Clusters show similarity, not truth or consensus. Prefer no write over a weak or
+duplicative artifact.
+
+## Review clusters
+
+1. Call `memory_list_clusters`.
+2. If analysis is missing or stale, call `memory_recluster`, then list again.
+3. Fetch useful clusters with `memory_fetch_cluster`. Treat noise as optional
+   review material, not automatically important content.
+4. Follow representative `qmd://` source paths with `memory_get` whenever the
+   excerpt lacks context or a conclusion could change durable knowledge.
+5. Distinguish underlying memory or session evidence from earlier canon and
+   reflections. Derived artifacts may help locate, challenge, or revise an
+   understanding, but repetition does not make them independent evidence.
+6. For each reviewed cluster, choose canon, reflection, or no write.
+
+## Write canon
+
+Use `knowledge/canon/<stable-topic>.md` for a supported, durable rule or current
+understanding. Update the topic file in place instead of creating dated copies.
+
+Every semantic chunk in canon must remain correct if retrieved alone:
+
+- State only the current affirmative truth.
+- Remove obsolete instructions rather than preserving them for comparison.
+- Never add `Supersedes`, history, changelog, old-process, or migration sections.
+- Include a human-readable `Updated` timestamp, the current rationale, and
+  `qmd://` evidence citations.
+- Preserve uncertainty in the claim itself. If the evidence does not support a
+  stable current claim, write a reflection or nothing.
+
+A concise shape is sufficient:
+
+```markdown
+# Topic
+
+Updated: 2026-08-26 14:30 EDT
+
+## Current understanding
+
+Present-tense rule or facts.
+
+## Rationale
+
+Why this is the current understanding.
+
+## Evidence
+
+- qmd://memory/...
+- qmd://sessions/...
+```
+
+## Write reflections
+
+Use `knowledge/reflections/YYYY-MM-DD.md` for patterns, hypotheses,
+contradictions, open questions, or reasoning worth revisiting. Append a
+timestamped section when the day's file already exists. Label uncertainty
+plainly and include the `qmd://` evidence examined. Reflections are not
+authoritative instructions.
+
+## Finish the cycle
+
+- Do not rewrite raw memory or session projections.
+- Avoid restating knowledge already captured accurately.
+- Verify new or updated knowledge with `memory_search`, selecting `canon` or
+  `reflections` when useful.
+- Report clusters reviewed, files changed, evidence used, uncertainties, and
+  intentional skips.
+- Do not recluster again after this cycle's writes. Let them enter the next
+  scheduled cycle so the run cannot recursively react to its own output.