🏗️ Architecture: Should unified-builder tools be in separate NX libraries or ...

📋 Decision Context

Question:

Should unified-builder tools be in separate NX libraries or grouped?

Task: Not specified

🎯 Decision Made

Chosen:

Hybrid approach - keep tools grouped by domain, not one lib per tool

Options Considered:

1. Separate NX library for each tool (7+ libs)
2. Keep all tools in universe-canvas
3. Hybrid - group by domain (current with fixes)

💭 Reasoning

1. Separate libs per tool creates too much boilerplate overhead. 2) Current grouping by domain (universe-canvas has canvas+structure+preview, vibe-universe is separate for AI) follows single responsibility at the domain level. 3) Tools within the same domain often share internal utilities. 4) Only split when a tool has distinct dependencies or deployment needs.

📁 Files Involved

• libs/libs-space/universe-canvas/src/lib/components/
• libs/libs-space/unified-builder/src/lib/components/dock-integration/builder-tool-panel.component.ts
• libs/libs-structural/vibe-universe/

🔗 Related

• Decision ID: dev_1768486145287_241mof9
• Session: 45
• Workspace: editor2

Auto-generated by MCP Smart Consolidation