Architecture: What should we do with gograb-core, gograb-analytics (empty ...

Documentation for Sessions

🏗️ Architecture: What should we do with gograb-core, gograb-analytics (empty ...

Date: 2026-02-11
Time: 22:51:02 UTC
Session: gspace1-106.12
Agent: documentation
Confidence: 88%
Status: ✅ Documented


📋 Decision Context

Question:

What should we do with gograb-core, gograb-analytics (empty databases) and ai-tenants (deprecated)?

Task: Database architecture audit - cleanup of unused databases and deprecated configs


🎯 Decision Made

Chosen:

Remove from configuration since they have no collections and create confusion

Options Considered:

  1. Leave them as-is for future use
  2. Remove from configuration since they have no collections and create confusion
  3. Repurpose them for new data

💭 Reasoning

gograb-core and gograb-analytics are defined in API_DATABASE_NAMES but zero schemas/modules reference them — they are dead config that creates confusion about the architecture. ai-tenants is explicitly marked DEPRECATED in the code. Keeping unused database names in the config makes developers think there's data there. Clean removal with a note in the documentation is the right approach. If analytics or core data is needed in the future, new databases can be added then with clear purpose.


📁 Files Involved


🔗 Related


Auto-generated by MCP Smart Consolidation