🏗️ Architecture: Should Vitto memories have a title field for better UI displ...

Date: 2026-03-11
Time: 18:40:26 UTC
Session: gspace1-204.11
Agent: backend
Confidence: 92%
Status: ✅ Documented

📋 Decision Context

Question:

Should Vitto memories have a title field for better UI display and searchability?

Task: Not specified

🎯 Decision Made

Chosen:

Add optional title field to VittoMemory schema. Derive from summary (first 80 chars) at write time via MemoryPersistenceService. Backend recall_vitto_memory already patches title from summary as a stopgap.

Options Considered:

1. Add title to schema (chosen)
2. Only derive at query time (current stopgap)
3. Use LLM to generate titles on every memory write (too expensive)

💭 Reasoning

Current schema has only summary (up to 500 chars). The chat UI renders memory results with a title field that doesn't exist, showing 'Untitled' for every result. A derived title (80 char truncation of summary) provides: (1) better UI display in recall cards, (2) better text search since title gets indexed, (3) future ability to have LLM generate concise titles. The stopgap in tool-registry works but a schema-level field is cleaner. Non-breaking change — field is optional with default derived from summary.

📁 Files Involved

• APIs/backend-vitto-api/src/app/mind/schemas/vitto-memory.schema.ts
• APIs/backend-vitto-api/src/app/engine/memory-persistence.service.ts
• APIs/backend-vitto-api/src/app/tools/tool-registry.service.ts

🔗 Related

• Decision ID: dev_1773254426831_z6f6lb0
• Session: 204
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation