Thanks! We use PostgreSQL (Supabase) with pgvector. Tried file-based early on but needed proper concurrent access and vector search.

  Indexing is hybrid — pgvector for semantic search, full-text search for exact matches.            
                                                                                                    
  For lifecycle, we keep it simple: users organize knowledge into "spaces" per project. Git spaces  
  auto-sync commits/PRs. No automatic eviction — snapshots let you save/restore state.              
                                                                                                    
  Cross-conversation context: we don't carry over conversation state. Each session, Claude just
  queries stored knowledge for what's relevant. No identity leaking between sessions, just
  searchable context on demand.

  Curious — have you run into specific challenges with memory lifecycle in your own work?