🏗️ Architecture: How should we unify all universe-level tools into a single b...

📋 Decision Context

Question:

How should we unify all universe-level tools into a single builder experience?

Task: Create comprehensive plan for unifying universe tools

🎯 Decision Made

Chosen:

Create comprehensive unification plan with 11 phases: Route restructuring (default to /builder), Tool tab system, Architect integration, Page Builder integration, Singularity integration, Deployment integration, Universe Map integration, Modular Universe grid integration, Enhanced tool orchestration, Unified state management, and Visual polish

Options Considered:

1. Extend current unified builder with tool tabs and embeddables
2. Create entirely new unified component from scratch
3. Keep tools separate but improve navigation between them
4. Use micro-frontend architecture with iframes

💭 Reasoning

The platform has 15+ specialized tools spread across libs-space and libs-structural. Currently users land at /canvas (single-purpose tool) and must manually navigate between tools, losing context. The existing unified builder successfully combines AI + Canvas via split-view with ToolOrchestrationService for module handoff. This pattern should be extended to embed ALL tools as swappable workspace views with synchronized state, keyboard shortcuts, and bi-directional sync across tools.

📁 Files Involved

• docs/english/Plans/current-plans/unifying-universe-tools.md
• libs/libs-space/universe-canvas/src/lib/components/unified-builder/
• libs/libs-structural/vibe-universe/src/lib/services/tool-orchestration.service.ts
• apps/gograb-space/src/app/app.routes.ts

🔗 Related

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

Auto-generated by MCP Smart Consolidation