🏗️ Architecture: How should Vitto Memory and Intelligence Memory Browser diff...

Date: 2026-02-17
Time: 19:23:02 UTC
Session: gspace1-111.2
Agent: architecture
Confidence: 90%
Status: ✅ Documented

📋 Decision Context

Question:

How should Vitto Memory and Intelligence Memory Browser differentiate their data to avoid overlap?

Task: Not specified

🎯 Decision Made

Chosen:

Transform Vitto Memory into a 'Knowledge Base' view with category grouping, info banner explaining the relationship, and a toggle between grouped/list views. Keep both systems' data but present them distinctly.

Options Considered:

• No alternatives documented

💭 Reasoning

Both systems store overlapping data (MCP decisions appear in both backend-vitto-api and backend-ai-api). Rather than hiding data, the fix clearly differentiates the views: Vitto Memory shows grouped knowledge categories (Patterns, Bugfixes, Milestones, etc.) while Memory Browser shows raw structured decisions with confidence/reasoning. An info banner links between them. The grouped view is the default, making the data immediately useful rather than a flat list.

📁 Files Involved

• libs/libs-ai/vitto-hub/src/lib/components/memory-manager/memory-manager.component.ts
• libs/libs-ai/vitto-hub/src/lib/components/memory-manager/memory-manager.component.html
• libs/libs-ai/vitto-hub/src/lib/components/memory-manager/memory-manager.component.scss

🔗 Related

• Decision ID: dev_1771356182821_y52xuix
• Session: 111
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation