🏗️ Architecture: How should drag-drop from unified chat integrate with the ex...

Date: 2026-02-21
Time: 18:20:11 UTC
Session: gspace1-133.4
Agent: angular
Confidence: NaN%
Status: ✅ Documented

📋 Decision Context

Question:

How should drag-drop from unified chat integrate with the existing canvas/builder infrastructure?

Task: Not specified

🎯 Decision Made

Chosen:

Extend existing @libs-ux/drag-drop + DropListConnectionService + CanvasDragData

Options Considered:

1. Build new drag-drop system from scratch
2. Extend existing @libs-ux/drag-drop + DropListConnectionService + CanvasDragData

💭 Reasoning

The existing pipeline (CanvasDragData → DropListConnectionService → CanvasSectionComponent → ModuleRegistryService → DynamicRouteService) is proven and handles AI module detection, outcome tracking, and cross-tool sync. The unified chat just needs to produce the same CanvasDragData format that AIPanelComponent already produces. No new infrastructure needed — just ensure the ActionPlugin outputs CanvasDragData.

📁 Files Involved

• No files specified

🔗 Related

• Decision ID: dev_1771698011374_uz306ae
• Session: 133
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation