🏗️ Architecture: Does vibe-universe need architectural changes to route throu...

Date: 2026-03-11
Time: 16:32:43 UTC
Session: gspace1-204.6
Agent: angular
Confidence: 98%
Status: ✅ Documented

📋 Decision Context

Question:

Does vibe-universe need architectural changes to route through Vitto?

Task: Not specified

🎯 Decision Made

Chosen:

No. Vibe-universe was already correctly routed through Vitto via WorkflowStateService. The workflowType: 'full-configuration' field was never transmitted to the backend — it was dead code in the TypeScript type. Only cosmetic cleanup was needed: remove the dead field, remove the fallback check, and document the architecture.

Options Considered:

• No alternatives documented

💭 Reasoning

Deep code review revealed that WorkflowStateService.startWorkflow() (line 182) sends directly to ${vittoApiUrl}/module-generation/start with only description, spaceId, universeId, userId, maxModules, outputMode as query params. The workflowType field from StartWorkflowRequest is NEVER included in the URLSearchParams construction. This means vibe-universe generation was already working through Vitto's 6-phase pipeline — the 'full-configuration' string was misleading dead code. The real issue was PlatformGenerationService (fixed in S204.4) and GenerationHubService (fixed in S204.5), not vibe-universe.

📁 Files Involved

• libs/libs-ai/gograb-ai-lib/src/lib/services/workflow-state.service.ts
• libs/libs-structural/vibe-universe/src/lib/components/vibe-universe-generator/vibe-universe-generator.component.ts

🔗 Related

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

Auto-generated by MCP Smart Consolidation