🏗️ Architecture: SESSION 46 PREP: What is THE-ONE-WAY architecture and how sh...

📋 Decision Context

Question:

SESSION 46 PREP: What is THE-ONE-WAY architecture and how should generation work?

Task: Session 46 Preparation: THE-ONE-WAY Architecture

🎯 Decision Made

Chosen:

THE-ONE-WAY (Session 40.2) defines: (1) ONE FORMAT: UniversalModule[] with moduleRef for code modules, (2) ONE SAVE: universeModuleService.replaceTree() → persistTreeToFlatArchitecture(), (3) ONE LOAD: load() → loadFlatArchitecture(), (4) Business modules have moduleRef pointing to space_modules, structural modules (layout, navigation) have NO moduleRef. Storage: MongoDB space_{spaceId}/ with universes/, modules/, pages/, widgets/ collections.

Options Considered:

• No alternatives documented

💭 Reasoning

Session 46 must verify ALL generation paths follow THE-ONE-WAY. Critical files: universe-module.service.ts, vibe-universe generator, module-code-generator.service.ts, backend-ai-api workflow services. Must ensure moduleRef links business modules to generated code in /modules/business/.

📁 Files Involved

• docs/english/GoGrab-Space/architecture/THE-ONE-WAY.md
• libs/libs-foundational/core-angular/src/lib/services/universe-module.service.ts
• apis/backend-ai-api/src/app/workflow/generators/module-code-generator.service.ts
• libs/libs-structural/vibe-universe/src/lib/services/tool-orchestration.service.ts

🔗 Related

• Decision ID: dev_1768510622553_t1qnnf3
• Session: 45
• Workspace: editor2

Auto-generated by MCP Smart Consolidation