Architecture: How should the Universe Canvas represent modules?

Documentation for Sessions

🏗️ Architecture: How should the Universe Canvas represent modules?

📋 Decision Context

Question:

How should the Universe Canvas represent modules?

Task: Session 24.1: Rethink universe canvas - modules + routes, not page layout

🎯 Decision Made

Chosen:

Simple flat list with route information

Options Considered:

Force visual layout (header, sidebar, content, footer)
Simple flat list with route information
Complex nested structure with positions

💭 Reasoning

The Universe is NOT a page - it's a PROJECT canvas. Forcing visual layouts (sidebar, content area) doesn't make sense at this level. Modules should be shown as a simple list with their routes - that's how they connect. Visual page layouts belong in the Page Builder, not the Universe Canvas. Routes are the primary connection mechanism between modules.

📁 Files Involved

libs/libs-space/universe-canvas/src/lib/services/canvas-module-converter.service.ts
libs/libs-structural/vibe-universe/src/lib/components/vibe-universe-generator/vibe-universe-generator.component.ts

🔗 Related

Decision ID: dev_1767664429972_dbmimxk
Session: 22
Workspace: editor2

Auto-generated by MCP Smart Consolidation