Architecture: What is Vitto's role relative to libraries, routes, and comp...

Documentation for Sessions

🏗️ Architecture: What is Vitto's role relative to libraries, routes, and comp...

Date: 2026-03-16
Time: 19:23:58 UTC
Session: gspace1-226.8
Agent: angular
Confidence: 97%
Status: ✅ Documented

📋 Decision Context

Question:

What is Vitto's role relative to libraries, routes, and components in the platform generation ecosystem?

Task: S226.2: Platform Generation v2 architecture design

🎯 Decision Made

Chosen:

Vitto is ALWAYS the supreme orchestrator. Libraries are tools Vitto wields. Every route, component, and tool is a surface that Vitto orchestrates. Modularity-lib workbench is not 'a standalone module builder with an AI button' — it's 'a UI where Vitto builds modules and the user watches/guides.' Same pattern as vitto-studio.

Options Considered:

Vitto as one of many independent generators (status quo — modularity-lib has its own AI)
Vitto as supreme orchestrator with libraries as tools (chosen)
No AI orchestration — manual generation only

💭 Reasoning

This is the foundational architectural principle for the entire platform. Without it, each library develops its own independent AI generators (like modularity-lib's pattern-matching AIModuleGeneratorService that uses heuristics, not LLM). With it, all generation flows through Vitto's orchestration pipeline — the backend-vitto-api. Libraries provide the canvas, controls, rendering. Vitto provides the intelligence. This means: no independent AiModuleGeneratorService inside modularity-lib. Instead, Vitto knows 'when user is at /modularity/workbench, I can use these tools: define entities, configure state, build flows, design UI, test, deploy.' Each step is a Vitto capability, not a standalone feature. This principle also affects how Vitto learns: every generation cycle feeds back through log_decision → outcome → intelligence(reflect) → getAITrainingContext(). The more Vitto generates, the smarter it gets.

📁 Files Involved

libs/libs-structural/modularity-lib/src/lib/services/ai-module-generator.service.ts
libs/libs-structural/vitto-studio/src/lib/services/studio-vitto-bridge.service.ts
APIs/backend-vitto-api/src/app/module-generation/platform-generation.service.ts

🔗 Related

Decision ID: dev_1773689038875_urfrm8f
Session: 226
Workspace: gspace1

Auto-generated by MCP Smart Consolidation