Proposal: GovernedMemory adapter for Mem0 OSS

[piyushkr0509]

Hi Mem0 maintainers,

We built an optional GovernedMemory adapter for the synchronous Mem0 OSS client.

Design:

• Mem0 remains the system of record for memory content, embeddings, IDs, and semantic search.
• GovernedMemory evaluates writes and retrieved candidates for trust, taint, policy, quarantine, provenance, and auditability.
• No duplicate memory store, embeddings, or vector-search pipeline.
• The adapter is a thin coordination layer.

Current scope:

• GovernedMem0.add()
• GovernedMem0.search()
• GovernedMem0.quarantine()
• GovernedMem0.get_governance()
• GovernedMem0.retry_binding()

Supported contract:

• mem0ai==2.0.12
• Synchronous Mem0 OSS Memory
• Mem0 Platform MemoryClient and async APIs are not currently supported.

Repository:
https://github.com/Metaworkers-ai/governedmemory

Integration guide:
https://github.com/Metaworkers-ai/governedmemory/blob/main/docs/integrations/mem0.md

We would appreciate feedback on:

1. Whether this adapter boundary is compatible with Mem0’s OSS direction.
2. Recommended extension points or APIs for governance wrappers.
3. Whether a link to this integration would be appropriate in Mem0 documentation.
4. Any compatibility concerns we should address before recommending it publicly.