⚙️ Implementation: How should the VibeUniverseGenerator handle existing univers...

📋 Decision Context

Question:

How should the VibeUniverseGenerator handle existing universe context when embedded in UnifiedBuilder?

Task: Session 24.1: Fix complete platform building workflow

🎯 Decision Made

Chosen:

Check universeContext.universeId() and add modules to existing universe if available

Options Considered:

1. Always create new universe during deployToUniverse()
2. Check universeContext.universeId() and add modules to existing universe if available
3. Pass universeId as input to vibe generator

💭 Reasoning

When VibeUniverseGenerator is embedded in the UnifiedBuilder, the UnifiedBuilder already sets the universe context via universeContext.setContext(). The deployToUniverse() method should check if there's an existing universe ID in context and add modules to that universe instead of always creating a new one. This allows the AI Enhance flow (Hub -> UnifiedBuilder -> Generate -> Deploy) to correctly add modules to the current universe being edited.

📁 Files Involved

• libs/libs-structural/vibe-universe/src/lib/components/vibe-universe-generator/vibe-universe-generator.component.ts
• libs/libs-foundational/core-angular/src/lib/services/space.service.ts

🔗 Related

• Decision ID: dev_1767659750885_3u5ac0q
• Session: 22
• Workspace: editor2

Auto-generated by MCP Smart Consolidation