🏗️ Architecture: Why is Universe Architect using VibeCodingOrchestratorServic...

📋 Decision Context

Question:

Why is Universe Architect using VibeCodingOrchestratorService instead of WorkflowStateService?

Task: Session 31.1: Critical analysis of generation service architecture

🎯 Decision Made

Chosen:

Historical mistake - VibeCodingOrchestrator was first attempt, WorkflowStateService replaced it, but old service was never removed and architect still uses it

Options Considered:

1. Keep VibeCodingOrchestrator
2. Switch to WorkflowStateService
3. Create new unified service
4. Use different service per context

💭 Reasoning

VibeCodingOrchestratorService (1800 lines) is a god-object anti-pattern that generates empty UniversalModule structures only - no entities, actions, or widgets. It completes in 2-6 seconds which proves it's not generating real code. WorkflowStateService connects to backend-ai-api's 7-phase workflow system (analyze, plan, validate, implement, integrate, verify, test-e2e) that generates 20-50 actual TypeScript files with entities, services, components, and tests. Vibe-universe-generator correctly uses WorkflowStateService. Universe Architect incorrectly uses VibeCodingOrchestrator. Result: vibe-universe generates real platforms, architect generates navigation skeletons. Solution: Replace vibeCodingOrchestrator with workflowState in architect-canvas, subscribe to SSE events, stream generated files to side panel Code tab. This is P0 critical - system is useless without real code generation.

📁 Files Involved

• libs/libs-ai/gograb-ai/src/lib/services/vibe-coding-orchestrator.service.ts
• libs/libs-ai/gograb-ai/src/lib/services/workflow-state.service.ts
• libs/libs-space/universe-architect/src/lib/components/architect-canvas/architect-canvas.component.ts

🔗 Related

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

Auto-generated by MCP Smart Consolidation