Architecture: How should service responsibilities be divided between backe...

Documentation for Sessions

🏗️ Architecture: How should service responsibilities be divided between backe...

Date: 2026-01-16
Time: 23:12:53 UTC
Session: editor2-49.7
Agent: backend
Confidence: 90%
Status: ✅ Documented

📋 Decision Context

Question:

How should service responsibilities be divided between backend-api and backend-ai-api?

Task: Define service boundaries for platform generation

🎯 Decision Made

Chosen:

backend-api: GiteaClient, DraftService, BuildPipeline, Deployment. backend-ai-api: Code generation (vibe-universe), AI operations. Generation calls backend-api to push code.

Options Considered:

All in backend-ai-api
All in backend-api
Split: AI ops in backend-ai-api, infrastructure in backend-api

💭 Reasoning

backend-api already handles deployment, CRUD, user management. 2. backend-ai-api is for AI operations and code generation. 3. Git operations (push, branch, tag) are infrastructure operations, belong in backend-api. 4. Draft management is business logic, belongs in backend-api. 5. Build pipeline is deployment-related, belongs in backend-api. 6. Clean separation: AI generates files[], backend-api handles storage/deployment.

📁 Files Involved

apis/backend-api/
apis/backend-ai-api/

🔗 Related

Decision ID: dev_1768605173778_j78zl57
Session: 49
Workspace: editor2

Auto-generated by MCP Smart Consolidation