🏗️ Architecture: How should the Universe Architect generate meaningful hierar...

📋 Decision Context

Question:

How should the Universe Architect generate meaningful hierarchy instead of flat pages?

Task: Session 32.2: Universe Architecture Redesign - Phase 1

🎯 Decision Made

Chosen:

3-level semantic hierarchy: Galaxy (Application Section with layout) → World (Feature Group with entity context) → Page-Module (Actual Page with widgets)

Options Considered:

1. Flat page generation (current)
2. 2-level Galaxy-Page hierarchy
3. 3-level Galaxy-World-PageModule hierarchy
4. 4-level with Universe Core

💭 Reasoning

The previous flat generation (all 'page' types) had no semantic meaning. By defining Galaxy as a route container with layout template, World as entity-based feature grouping, and Page-Module as the actual renderable page with widgets, the hierarchy maps directly to modular-universe runtime concepts. This enables: 1) Layout templates per Galaxy (split-sidebar, dashboard), 2) Entity context per World (member, booking), 3) Widget-based pages with pageType (list, detail, form). Icons stored in metadata for TypeScript compatibility.

📁 Files Involved

• libs/libs-api/llm-integration/src/lib/services/generation.service.ts
• libs/libs-ai/gograb-ai/src/lib/services/vibe-coding-orchestrator.service.ts
• libs/libs-space/universe-architect/src/lib/services/architect-module-converter.service.ts

🔗 Related

• Decision ID: dev_1767965517282_y0da4fy
• Session: 31
• Workspace: editor2

Auto-generated by MCP Smart Consolidation