Hi @toxfox69,

Thank you for this PR and the effort you put into the TIAMAT connector.

After review, we’ve decided not to merge it into the MemOS repo for now. Here’s why:

1. Architecture fit — MemOS’s storage layer is built around graph backends (Neo4j, Postgres, etc.) that implement BaseGraphDB with nodes, edges, embeddings, and graph traversal. TIAMAT’s flat storage + FTS5 model is different, so it doesn’t fit as a drop-in backend.

2. Primary use case — The connector mainly serves as a TIAMAT API client for users who don’t run MemOS. The MemOS-specific helpers (import_textual_memories / export_as_textual_items) are secondary, so the core value is outside MemOS’s scope.

3. Maintenance and dependencies — Adding a third-party cloud service client would introduce an external dependency and maintenance burden that we’d prefer to keep out of the core repo for now.

We’d suggest publishing this as a standalone package (e.g. tiamat-memos-connector or under the TIAMAT org) and optionally linking it from MemOS docs as a community integration. Users who want a lightweight TIAMAT-backed memory store can install it directly.

Thanks again for the contribution and for your interest in MemOS.