collective-memory-repo/tasks/openclawd-migration-2026-03/GAP-ANALYSIS.md

GAP ANALYSIS

Resolved

• Durable memory lanes are established in collective-memory-repo.
• Remote memory-gateway is healthy and can return indexed-visible results on main.
• OpenClaw QMD paths have been redirected from vault folders to collective lanes.
• vaults/MEMORY.md has been downgraded to bridge/index role.
• vaults/memory/README.md now marks vaults/memory/* as compatibility-only.

Remaining Gaps

• vaults/memory/*.md still exists and can cause dual-source writing if process discipline is not applied.
• Write policy enforcement is doc-level; no hard guardrails yet (hooks/checks not implemented).

Risk Level

• Medium if users continue dual-write into both vaults and collective.
• Low for retrieval correctness when queries go through remote memory-gateway with require_latest=true.