From 922796d89362e077ca38907a9066696d83ec9774 Mon Sep 17 00:00:00 2001
From: "openclaw-docs-sync[bot]"
 <openclaw-docs-sync[bot]@users.noreply.github.com>
Date: Sun, 12 Apr 2026 16:11:33 +0000
Subject: [PATCH] chore(sync): mirror docs from
 openclaw/openclaw@51f0037e61be6fdcc49debfe5c279972565f720b

---
 .openclaw-sync/source.json  |  4 +--
 docs/plugins/memory-wiki.md | 63 +++++++++++++++++++++++++++++++++++++
 2 files changed, 65 insertions(+), 2 deletions(-)

diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json
index 45b1ec9af..05b531ed7 100644
--- a/.openclaw-sync/source.json
+++ b/.openclaw-sync/source.json
@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "90fac509875ef0852110d0b8364eaaa333868f3a",
-  "syncedAt": "2026-04-12T11:07:36.754Z"
+  "sha": "51f0037e61be6fdcc49debfe5c279972565f720b",
+  "syncedAt": "2026-04-12T16:11:32.563Z"
 }
diff --git a/docs/plugins/memory-wiki.md b/docs/plugins/memory-wiki.md
index 01b31a402..363ebedab 100644
--- a/docs/plugins/memory-wiki.md
+++ b/docs/plugins/memory-wiki.md
@@ -45,6 +45,28 @@ both layers in one pass with `memory_search corpus=all`.
 When you need wiki-specific ranking, provenance, or direct page access, use the
 wiki-native tools instead.
 
+## Recommended hybrid pattern
+
+A strong default for local-first setups is:
+
+- QMD as the active memory backend for recall and broad semantic search
+- `memory-wiki` in `bridge` mode for durable synthesized knowledge pages
+
+That split works well because each layer stays focused:
+
+- QMD keeps raw notes, session exports, and extra collections searchable
+- `memory-wiki` compiles stable entities, claims, dashboards, and source pages
+
+Practical rule:
+
+- use `memory_search` when you want one broad recall pass across memory
+- use `wiki_search` and `wiki_get` when you want provenance-aware wiki results
+- use `memory_search corpus=all` when you want shared search to span both layers
+
+If bridge mode reports zero exported artifacts, the active memory plugin is not
+currently exposing public bridge inputs yet. Run `openclaw wiki doctor` first,
+then confirm the active memory plugin supports public artifacts.
+
 ## Vault modes
 
 `memory-wiki` supports three vault modes:
@@ -304,6 +326,47 @@ Key toggles:
 - `render.createBacklinks`: generate deterministic related blocks
 - `render.createDashboards`: generate dashboard pages
 
+### Example: QMD + bridge mode
+
+Use this when you want QMD for recall and `memory-wiki` for a maintained
+knowledge layer:
+
+```json5
+{
+  memory: {
+    backend: "qmd",
+      "memory-wiki": {
+        enabled: true,
+        config: {
+          vaultMode: "bridge",
+          bridge: {
+            enabled: true,
+            readMemoryArtifacts: true,
+            indexDreamReports: true,
+            indexDailyNotes: true,
+            indexMemoryRoot: true,
+            followMemoryEvents: true,
+          },
+          search: {
+            backend: "shared",
+            corpus: "all",
+          },
+          context: {
+            includeCompiledDigestPrompt: false,
+          },
+        },
+      },
+    },
+  },
+}
+```
+
+This keeps:
+
+- QMD in charge of active memory recall
+- `memory-wiki` focused on compiled pages and dashboards
+- prompt shape unchanged until you intentionally enable compiled digest prompts
+
 ## CLI
 
 `memory-wiki` also exposes a top-level CLI surface: