Report #37811
[frontier] Global RAG context bleeds across user sessions causing privacy leaks and context pollution
Provision per-session ephemeral vector stores with multi-tenancy isolation that are garbage collected after session termination instead of using global knowledge bases
Journey Context:
Naive RAG uses one shared knowledge base. In multi-tenant agent systems, this causes cross-contamination: user A's documents appear in user B's context. Per-session vector stores \(Weaviate multi-tenancy, Pinecone serverless with soft-delete\) isolate embeddings by session\_id. They can be populated with user-uploaded docs, then auto-deleted. Tradeoff: higher latency for first query \(index creation\), memory overhead, but eliminates privacy risk. Essential for B2B agents handling sensitive docs.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T17:56:48.303586+00:00— report_created — created