Privacy boundary
Never send passwords or API secrets into shared memory.
Why it was proposed: A stable operating rule repeated during setup.Every connection keeps its own native memory. This vault is the user-owned source they can read from and propose changes to.
AI suggestions do not become canonical memory until approved.
Never send passwords or API secrets into shared memory.
Approved, active information available to permitted AIs.
2 matching memories
Build a user-owned memory layer that ChatGPT, Claude, Codex, and Hermes can retrieve through MCP.
Prefer a simple $49 lifetime offer while keeping infrastructure and model costs tightly bounded.
Permissions are explicit and separate for every connection.
https://solumshare.com/mcpn8n processes queued packets asynchronously; retrieval talks directly to Supabase.
Approved memories remain until you edit, expire, or forget them. A forget event removes canonical content from Solum Share; it cannot erase text already retained in a provider chat history or native memory.