Architecture: How should the embeddable-bridge library be organized archit...

Documentation for Sessions

🏗️ Architecture: How should the embeddable-bridge library be organized archit...

Date: 2026-01-28
Time: 21:22:42 UTC
Session: editor2-73.12
Agent: architecture
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

How should the embeddable-bridge library be organized architecturally?

Task: Not specified

🎯 Decision Made

Chosen:

Move from @libs-ai/ai-embeddable-bridge to @libs-ux/embeddable-bridge

Options Considered:

Keep in @libs-ai
Move to @libs-ux
Move to @libs-core
Create new @libs-embedding group

💭 Reasoning

Embedding is infrastructure, not AI-specific. The library provides cross-app communication patterns (postMessage, drag-drop, auth forwarding) that could be used for embedding any app, not just AI. Moving to libs-ux makes the purpose clear and allows future reuse for widget embedding, external tools, etc.

📁 Files Involved

libs/libs-ux/embeddable-bridge/src/index.ts
tsconfig.base.json

🔗 Related

Decision ID: dev_1769635362548_4jhlsjr
Session: 73
Workspace: editor2

Auto-generated by MCP Smart Consolidation