🏗️ Architecture: Which service should Universe Architect use for platform gen...

📋 Decision Context

Question:

Which service should Universe Architect use for platform generation?

Task: Session 31.2: Replace VibeCodingOrchestrator with WorkflowStateService in Universe Architect

🎯 Decision Made

Chosen:

WorkflowStateService instead of VibeCodingOrchestratorService

Options Considered:

1. Keep VibeCodingOrchestratorService (quick but empty results)
2. Use WorkflowStateService (7-phase real generation)
3. Create new hybrid service

💭 Reasoning

VibeCodingOrchestratorService returns empty navigation skeletons in 2-6 seconds - it doesn't generate real entities, actions, or widgets. WorkflowStateService connects to backend-ai-api with SSE streaming, runs 7 phases, and generates real platform code with entities, actions, and widgets. This is the same service used by vibe-universe-generator which produces working platforms. The VibeCodingOrchestratorService is kept for submitAIPrompt() which handles quick inline additions.

📁 Files Involved

• libs/libs-space/universe-architect/src/lib/components/architect-canvas/architect-canvas.component.ts
• libs/libs-space/universe-architect/src/lib/components/architect-side-panel/architect-side-panel.component.ts

🔗 Related

• Decision ID: dev_1767903404660_8og39xp
• Session: 31
• Workspace: editor2

Auto-generated by MCP Smart Consolidation