Add openclaw-memory-curator: WM→SWM→VM curator for OpenClaw workspace memory

[kiyeps]

Summary

Adds integrations/openclaw-memory-curator.json — a registry entry for OpenClaw Memory Curator, a curator daemon + CLI that bridges OpenClaw workspace memory into DKG V10's three-layer verifiable memory system.

Repo: https://github.com/kiyeps/openclaw-memory-curator (commit pinned in entry)

What it does

• Ingest: parses memory/*.md workspace files into Knowledge Assets with provenance quads, lands them in Working Memory (120 files smoke-tested live, 43 secrets auto-redacted, 0 errors)
• SWM promotion: automatic maturity tracking (reference-count threshold or explicit share: tag), swm/share seals by default → publish-ready assertions (verified via SPARQL shared-working-memory view)
• VM gate: Verifiable Memory publish is explicit CLI-only (curator publish <ka>) with interactive confirmation — never automatic. This satisfies the bounty rule that UI endorsement is disallowed; the gate is a deterministic human/CLI act.
• Recall: SPARQL search over WM+SWM for agent consumption

Why it fits

The first-party OpenClaw adapter is a chat bridge + read-only memory recall; all writes are delegated to the agent via SKILL.md prose (lossy, undisciplined). This integration fills that gap with deterministic, auditable curation — the LLM-Wiki / autoresearch direction the bounty targets.

Checklist

• Schema validation passes: 0 errors (1 expected warning — VM write authority, justified in fitNotes)
• Zero npm dependencies, node:test suite 22/22
• Smoke-tested against live DKG V10 node (Base Sepolia testnet)
• Quads use urn:openclaw:memory:* subjects, no per-quad graph field
• Secret redaction before any quad leaves the process

---

Submission metadata — final update (2026-09-08)

Tag: cfi-dkgv10-r1

Pinned commit: 418cd081adfbaf70c4fcccbb61ed7a85351dab54 (v0.1.2)

Contributor attestation (§8a.8): I attest that this submission is my own original work (or properly licensed third-party work), and that it contains no intentional backdoors, no hidden remote-execution paths, and no undeclared network egress. — @kiyeps

Design brief: https://github.com/kiyeps/openclaw-memory-curator/blob/main/docs/DESIGN.md

Demo: https://github.com/kiyeps/openclaw-memory-curator/blob/main/docs/demo-transcript.txt — recorded against a live local DKG V10 node (v10.0.15, Base Sepolia testnet, context graph openclaw-curator) with an isolated demo memory directory. Real runtime interaction: status → ingest → list → recall returning WM + SWM bindings.

Round-1 VM-scope justification (validator warning): The validator flags writeAuthority because the entry declares one VM operation (POST /api/knowledge-assets/:name/vm/publish). This declaration exists for accuracy, not because Round-1 features depend on it: the operation is the documented end of the WM → SWM → VM promotion path and is reachable only through the interactive curator publish <ka> CLI command gated by a y/n confirmation. It is never invoked automatically, never invoked by the daemon loop, and no other VM operation (/endorse, /verify, /update) is declared or used. All Round-1 functionality (ingest, recall, list, share, daemon) operates purely in WM/SWM. Declaring a gated capability the code genuinely contains was preferred over omitting it; we believe this satisfies "explicitly justified". If the committee prefers, the field can be trimmed to WM/SWM-only in a follow-up commit.

Security notes (§8): Secret redaction (private keys, API tokens, mnemonics) runs before any literal leaves the process. All HTTP egress is restricted to the local node (http://127.0.0.1:9200). Reads the DKG auth token from ~/.dkg/auth.token; never logs it. SWM share seals assertions by default. Curator-authority surfaces are documented in the registry security.notes. Recall display hardened against string/term binding shape differences (fix included in v0.1.2).

Maintenance commitment: Maintained by @kiyeps; support window ≥ 6 months post-merge.