Architecture: Should we remove embeddable-schemas or fix its build?
Documentation for Sessions
🏗️ Architecture: Should we remove embeddable-schemas or fix its build?
Date: 2026-01-27
Time: 16:59:13 UTC
Session: editor2-71.10
Agent: architecture
Confidence: 100%
Status: ✅ Documented
📋 Decision Context
Question:
Should we remove embeddable-schemas or fix its build?
Task: Not specified
🎯 Decision Made
Chosen:
Remove embeddable-schemas - confirmed zero external usage, only self-references. Build errors indicate it's misconfigured and unused. User explicitly requested removal if unused.
Options Considered:
- Fix embeddable-schemas build configuration
- Remove embeddable-schemas as it's unused
💭 Reasoning
Verified embeddable-schemas has zero external imports. Search across codebase found no usage outside its own directory. Build fails with module resolution issues. User's initial request: 'check to see if its being used anywhere, if not, remove it'. Decision: Remove as unused.
📁 Files Involved
- No files specified
🔗 Related
- Decision ID:
dev_1769533150313_h81q7g0 - Session: 71
- Workspace: editor2
Auto-generated by MCP Smart Consolidation