Architecture: How to build the Vitto Maker — a workspace for composing and...

Documentation for Sessions

🏗️ Architecture: How to build the Vitto Maker — a workspace for composing and...

Date: 2026-03-02
Time: 17:38:21 UTC
Session: gspace1-165.7
Agent: angular
Confidence: 90%
Status: ✅ Documented

📋 Decision Context

Question:

How to build the Vitto Maker — a workspace for composing and configuring Vitto as an AI agent?

Task: Build Vitto Maker workspace for session 165.5

🎯 Decision Made

Chosen:

New NX library @libs-ai/vitto-maker with 3 core services (VittoProfileService for data aggregation, MakerHistoryService for undo/redo, MakerActionService for mutation coordination) + shell component with hybrid panels layout (left accordion segments + center profile preview). Live-with-undo model: optimistic signal updates → API call → push to history stack with inverse operation. 5 segment categories: Capabilities, Knowledge, Character, Connections, Governance.

Options Considered:

  1. New @libs-ai/vitto-maker library with profile aggregation + undo
  2. Add Maker as component within existing vitto-hub
  3. Full D3/Canvas workspace with visual nodes
  4. Wizard/step-by-step configuration flow

💭 Reasoning

User clarified the original brain interactive was wrong direction (navigation hub, not configuration workspace). The Maker is fundamentally different: it's a character builder for an AI agent. New library needed because (1) it's architecturally distinct from vitto-hub's page-level components, (2) it has its own state management (unified profile aggregation + undo history), (3) clean dependency boundary. Undo uses snapshot-based approach (proven in PageHistoryService) with inverse API operations for server-side rollback. Segments lazy-load to avoid hammering all APIs on mount.

📁 Files Involved

🔗 Related

Auto-generated by MCP Smart Consolidation