diff --git a/integrations/dkg-wm-bridge.json b/integrations/dkg-wm-bridge.json
new file mode 100644
index 0000000..29ea47e
--- /dev/null
+++ b/integrations/dkg-wm-bridge.json
@@ -0,0 +1,74 @@
+{
+  "$schema": "../schema/integration.schema.json",
+  "schemaVersion": "0.1.0",
+  "slug": "dkg-wm-bridge",
+  "name": "DKG Working Memory Bridge",
+  "description": "Agent-plugin that deposits workspace artifacts (memory files, research notes, session outputs) into DKG v10 Working Memory with schema.org provenance and status tags, and promotes them to Shared Memory. Works with OpenClaw, Hermes, and comparable agents.",
+  "category": [
+    "ingestion",
+    "working-memory",
+    "agent-plugin",
+    "provenance"
+  ],
+  "maintainer": {
+    "github": "@jalopy1",
+    "name": "Lyvn",
+    "contact": "Telegram: @Lyvner"
+  },
+  "repo": "https://github.com/jalopy1/dkg-wm-bridge",
+  "commit": "4ec879e1f25e89b5ac4c2f4fb9fb2759d140a17b",
+  "license": "Apache-2.0",
+  "requiresDkgNodeVersion": ">=10.0.0",
+  "memoryLayers": [
+    "WM",
+    "SWM"
+  ],
+  "v10PrimitivesUsed": [
+    "ContextGraph",
+    "Assertion",
+    "Entity",
+    "UAL"
+  ],
+  "publicInterfacesUsed": [
+    "http-api"
+  ],
+  "targetAgents": [
+    "OpenClaw",
+    "Hermes",
+    "generic-CLI",
+    "generic-HTTP"
+  ],
+  "install": {
+    "kind": "cli",
+    "package": "dkg-wm-bridge",
+    "version": "0.1.5",
+    "binary": "wm-bridge",
+    "usageHint": "Run 'wm-bridge init --agent <name> --framework <openclaw|hermes>' to configure, then 'wm-bridge ingest <path>' to start depositing artifacts."
+  },
+  "security": {
+    "networkEgress": [],
+    "writeAuthority": [
+      "POST /api/assertion/create",
+      "POST /api/assertion/{name}/write",
+      "POST /api/assertion/{name}/promote",
+      "POST /api/assertion/{name}/discard",
+      "POST /api/assertion/{name}/import-file",
+      "POST /api/context-graph/create"
+    ],
+    "readEndpoints": [
+      "GET /api/status",
+      "GET /api/wallets",
+      "GET /api/context-graph/list",
+      "POST /api/assertion/{name}/query",
+      "POST /api/assertion/{name}/history",
+      "POST /api/query"
+    ],
+    "credentialsHandled": [],
+    "notes": "Zero network egress beyond the local DKG node. No install scripts. No dynamic code loading. No eval. Reads DKG auth token from ~/.dkg/auth.token or DKG_AUTH_TOKEN env var. Both DKG_API_URL and DKG_AUTH_TOKEN have sensible defaults and are not strictly required as env vars. Artifacts are classified by sensitivity level (public/shareable/personal/secret) at ingestion time. Promotion guards prevent personal/secret artifacts from reaching Shared Memory. Optional --scan flag detects PII and secrets before ingestion. All operations are audit-logged to ~/.dkg/audit.log."
+  },
+  "trustTier": "community",
+  "designBrief": "https://github.com/jalopy1/dkg-wm-bridge/blob/main/DESIGN.md",
+  "demo": "https://asciinema.org/a/99wdrB3KVZ8EvNMt",
+  "promotionPath": "Artifacts enter Working Memory as 'draft' status assertions with full PROV-O provenance (agent peer ID, timestamp, source file). Status tags track maturity: draft \u2192 reviewed \u2192 promote-ready \u2192 promoted \u2192 verified-ready. The 'promote' command moves artifacts to Shared Memory via GossipSub. Deterministic URIs (urn:dkg:wm-bridge:artifact/<hash>) remain stable through WM \u2192 SWM \u2192 VM promotion. Schema.org + PROV-O metadata is compatible with ClaimReview (the standard used by context oracles). Round 2 integration: our Context Oracle project will consume these artifacts as oracle inputs for claim verification.",
+  "fitNotes": "Directly implements the 'OpenClaw adapter that deposits every drafted artifact into the author's Working Memory' shape described in the bounty call Section 4. Extends to Hermes and generic agents. The agent's daily memory cycle (write notes \u2192 curate \u2192 publish findings) maps onto the WM \u2192 SWM \u2192 VM trust gradient. Multi-agent collaboration via shared Context Graphs enables the team-scratchpad pattern. The privacy protocol (sensitivity classification, PII/secret scanning, promotion guards) ensures personal and secret content never leaves the operator's node."
+}