🏗️ Architecture: How to replace the raw textarea memory editor with a structu...

Date: 2026-03-02
Time: 21:10:20 UTC
Session: gspace1-165.13
Agent: angular
Confidence: 93%
Status: ✅ Documented

📋 Decision Context

Question:

How to replace the raw textarea memory editor with a structured, user-friendly editor?

Task: Build structured memory editor as @libs-ux/ux-memory-editor

🎯 Decision Made

Chosen:

New @libs-ux/ux-memory-editor library with two reusable components: UxMemoryEditorComponent (structured form with type selector pills, chip inputs for tags/entities, importance slider, decay protection toggle, share level) and UxChipInputComponent (reusable chip/tag input with autocomplete). Integrated into Memory Manager replacing the old textarea+comma-string form.

Options Considered:

• No alternatives documented

💭 Reasoning

The existing memory edit UX is a raw textarea dumping internal format text ([channel-message]\n[Current context: vitto]) with comma-separated tags. This is developer-grade, not user-grade. Memory editing will become critical as Vitto's memory grows — bad edits = bad AI behavior. The structured editor surfaces all backend-editable fields (summary, type, tags, keyEntities, outcome) as intuitive UI controls. Built as @libs-ux (not @libs-ai) because it's a UI concern, reusable by Memory Manager, Vitto Maker, and future consumers. UxChipInputComponent is independently reusable for any string[] field. The editor supports 3 modes (edit/create/quick) for different contexts.

📁 Files Involved

• libs/libs-ux/ux-memory-editor/src/lib/components/ux-memory-editor/ux-memory-editor.component.ts
• libs/libs-ux/ux-memory-editor/src/lib/components/ux-chip-input/ux-chip-input.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.ts

🔗 Related

• Decision ID: dev_1772485820780_y2ihxh3
• Session: 165
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation