🏗️ Architecture: How should Vitto's Mind data be exposed for the Mind Explore...

Date: 2026-02-11
Time: 19:30:13 UTC
Session: gspace1-105.24
Agent: backend
Confidence: 92%
Status: ✅ Documented

📋 Decision Context

Question:

How should Vitto's Mind data be exposed for the Mind Explorer UI?

Task: Session 105.5: Vitto Mind Explorer endpoints and UI

🎯 Decision Made

Chosen:

Add dedicated /engine/mind/* endpoints: /mind/traces (paginated execution history), /mind/strategies (strategy memories with success rates), /mind/agents (agent performance breakdown), /mind/lessons (deduplicated lessons). Frontend Intelligence tab renders these in explorable cards.

Options Considered:

• No alternatives documented

💭 Reasoning

The MindService already has all the query methods (queryTraces, getStrategyContext, getAgentReliabilityForTask, getRecentLessons). They just need HTTP endpoints. The /mind/summary endpoint we created gives the overview; these new endpoints give drill-down capability. This is additive — no existing endpoints change.

📁 Files Involved

• apis/backend-vitto-api/src/app/engine/vitto.controller.ts
• apis/backend-vitto-api/src/app/mind/mind.service.ts

🔗 Related

• Decision ID: dev_1770838213922_5sp18ex
• Session: 105
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation