Feature request: discuss optional ClawMem memory backend / integration

Summary

I'd like to discuss whether Haystack would be open to an optional ClawMem integration for durable memory in agent and pipeline workflows.

This is not a request to replace Haystack's architecture. The narrower question is whether ClawMem could fit as an optional component/integration for teams that want auditable long-term memory.

Why this seems worth discussing

Haystack's README explicitly describes the framework as giving developers control over retrieval, routing, memory, and generation, and says users can use built-in components for memory or create their own.

That makes this look like a potentially good fit for:

1. an external integration component
2. a docs/example integration pattern
3. a first-party optional connector if maintainers think it belongs in the ecosystem

What ClawMem would add

ClawMem is oriented around:

• durable memory across sessions
• auditability of memory updates
• repository/workspace-scoped memory boundaries
• optional shared memory across collaborators and agents

Clarification I am looking for

Would maintainers be open to one of these directions?

1. external integration component
2. docs/example integration
3. first-party optional connector
4. not a good fit for Haystack

Minimal scope

The smallest useful scope seems to be:

• optional integration only
• preserve existing Haystack defaults
• fit into Haystack's component model instead of introducing a competing orchestration layer

If this sounds reasonable, I can turn it into a concrete implementation brief.

Start with Haystack's README and its component model to understand how optional memory integrations are currently described and structured. The issue is ready when maintainers select a direction—external component, documentation/example integration, first-party connector, or no fit—and the scope is turned into a concrete implementation brief.