Architecture: How should the platform builder architecture be refactored f...

Documentation for Sessions

🏗️ Architecture: How should the platform builder architecture be refactored f...

Date: 2026-01-16
Time: 20:35:34 UTC
Session: editor2-48.2
Agent: architecture
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

How should the platform builder architecture be refactored for Session 48?

Task: Session 48: Platform Builder Architecture Refactor

🎯 Decision Made

Chosen:

Three-pronged refactor: (1) Fresh libs-renderable components (Angular + Flutter), (2) Merge singularity-lib INTO modularity-lib for unified module generation, (3) Clean cosmic types by removing widget/data/flow/page

Options Considered:

Migrate existing modules to libs-renderable
Create fresh implementations in libs-renderable
Keep current structure with patches

💭 Reasoning

User confirmed: singularity became isolated and should be integrated into modularity-lib for unified CRUD generation. Layout-builder should support both Angular and Flutter from the start. Fresh implementations are preferred over migrating legacy code to ensure new components are perfectly adjusted to the new architecture. This approach separates structure (cosmic hierarchy) from implementation (NX libraries with moduleRef).

📁 Files Involved

libs/libs-renderable/
libs/libs-structural/modularity-lib/
libs/libs-structural/singularity-lib/
libs/libs-foundational/core-models/src/lib/types/modules/

🔗 Related

Decision ID: dev_1768595734879_oetskj4
Session: 48
Workspace: editor2

Auto-generated by MCP Smart Consolidation