🏗️ Architecture: Should user_agent_memories be moved out of gograb-api to an ...

Date: 2026-02-11
Time: 22:50:50 UTC
Session: gspace1-106.10
Agent: architecture
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

Should user_agent_memories be moved out of gograb-api to an AI-specific database (ai-agents, ai-memory, or vitto-mind)?

Task: Database architecture audit - where to store user_agent_memories and data ownership rules

🎯 Decision Made

Chosen:

Keep in gograb-api alongside other user data

Options Considered:

1. Keep in gograb-api alongside other user data
2. Move to ai-agents (with other agent data)
3. Move to ai-memory (with embeddings/semantic search)
4. Move to vitto-mind (with Vitto's brain)
5. Create new ai-user-data database

💭 Reasoning

user_agent_memories is fundamentally USER data — what agents know about a specific person (name, job title, preferences). It belongs with other user-owned data (users, user_preferences, user_hierarchy, billing_accounts) in gograb-api for these reasons: (1) GDPR compliance — user data deletion only needs to target one database, (2) Data locality — loadUserContext() queries users + memories in one connection, no cross-database joins, (3) The ai-* databases are AI SYSTEM data (tasks, decisions, patterns, embeddings) that don't belong to any individual user, (4) vitto-mind is Vitto's operational brain (strategies, skills, execution traces) — different concern from per-user facts, (5) backend-ai-api already has a platform connection to gograb-api via UserAgentMemoryModule — the pattern is established and working.

📁 Files Involved

• libs/libs-api/backend-core/src/lib/config/database-names.config.ts
• docs/english/GoGrab-Space/architecture/database-architecture.md

🔗 Related

• Decision ID: dev_1770850250875_x1nlffd
• Session: 106
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation