Architecture: What is the correct architecture for Universe as the foundat...
Documentation for Sessions
🏗️ Architecture: What is the correct architecture for Universe as the foundat...
📋 Decision Context
Question:
What is the correct architecture for Universe as the foundation of AI-trainable, reusable platforms?
Task: Session 24.2: Deep analysis of Universe foundation architecture
🎯 Decision Made
Chosen:
Universe as Project Container (module registry + route map)
Options Considered:
- Universe as Page Layout (current - forcing visual positions)
- Universe as Project Container (module registry + route map)
- Universe as Component Tree
- Universe as Widget Canvas
💭 Reasoning
Universe is NOT a page - it's a PROJECT CANVAS. The correct mental model is: Universe (project container with installed modules + route config + nav config) → Module (business feature with pages + actions + events) → Page (visual layout with widgets). Routes are the primary connection mechanism between modules, not visual positions. Visual layout (flexbox, grid, positions like sidebar/content) belongs at the PAGE level, not Universe level. This separation enables: 1) AI-trainability (clear schemas), 2) Reusability (modules can be shared), 3) Expandability (add features without breaking layout).
📁 Files Involved
docs/english/sessions/editor2/session-24/SESSION-24.2-UNIVERSE-FOUNDATION-ANALYSIS.mdlibs/libs-foundational/core-models/src/lib/types/multiverse.types.tslibs/libs-foundational/core-models/src/lib/types/modules/universal-module.types.ts
🔗 Related
- Decision ID:
dev_1767664756076_snd5cnx - Session: 22
- Workspace: editor2
Auto-generated by MCP Smart Consolidation