🏗️ Architecture: Should platform generation include backend code generation, ...

Date: 2026-03-16
Time: 19:23:19 UTC
Session: gspace1-226.5
Agent: backend
Confidence: 88%
Status: ✅ Documented

📋 Decision Context

Question:

Should platform generation include backend code generation, or is the generic UniverseDataController sufficient?

Task: S226.2: Platform Generation v2 architecture design

🎯 Decision Made

Chosen:

Generate per-entity backend code (schemas, DTOs, services, controllers). Generic UniverseDataController remains as fallback only. This REVERSES the S226.1 decision (dev_1773682086326_mk7lvwo) that said 'NO backend code generation is needed.'

Options Considered:

1. Keep generic UniverseDataController as sole backend (S226.1 recommendation)
2. Generate per-entity backend code with generic controller as fallback (chosen)
3. Generate standalone microservice per universe (Option B - too premature)
4. Serverless functions per entity on Cloudflare Workers (Option C - too premature)

💭 Reasoning

Root cause: The generic UniverseDataController accepts ANY JSON with zero validation, zero business logic, zero relationship enforcement, zero per-entity access control, zero schema enforcement at DB level. This is fine for prototyping but completely inadequate for 'robust platforms that manage real businesses.' The S226.1 analysis was correct that the frontend generation needs fixing FIRST, but wrong that backend generation is unnecessary. The vision is full-stack generated platforms: validated inputs, enforced relationships, typed API endpoints. Same entity field definition drives frontend controls (PropertyControlType), backend schemas (Mongoose), AND backend validation (class-validator). One definition, three outputs. Deployment starts with Option A (dynamic modules on shared backend-api), with generic controller as permanent fallback for entities not yet generated.

📁 Files Involved

• APIs/backend-api/src/app/data/data.controller.ts
• APIs/backend-vitto-api/src/app/module-generation/platform-generation.service.ts
• APIs/backend-vitto-api/src/app/module-generation/fullstack-orchestration.service.ts
• docs/superpowers/specs/2026-03-16-platform-generation-v2-design.md

🔗 Related

• Decision ID: dev_1773688996355_1ptvia9
• Session: 226
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation