🏗️ Architecture: When should GitLab repo initialization happen in the generat...

Date: 2026-03-11
Time: 15:04:33 UTC
Session: gspace1-203.5
Agent: backend
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

When should GitLab repo initialization happen in the generation pipeline?

Task: S203: Platform generation pipeline — fail fast

🎯 Decision Made

Chosen:

PRE-FLIGHT: Initialize GitLab repo BEFORE any LLM phases (ENHANCE, ANALYZE, etc). Fail fast if GitLab unavailable. Only admin/dev/executive users can fall back to local-only generation. Regular users get immediate abort with clear error.

Options Considered:

1. Keep GitLab init in DEPLOY phase (Phase 7)
2. Move to PRE-FLIGHT before any LLM phases
3. Validate connectivity only, init in DEPLOY

💭 Reasoning

The previous flow initialized GitLab in the DEPLOY phase (Phase 7), AFTER spending all LLM tokens on ENHANCE→ANALYZE→DECOMPOSE→PLAN→EXECUTE. If GitLab failed, all those tokens were wasted — the generated code had nowhere to be stored. Moving initialization to pre-flight means: (1) zero wasted tokens on failure, (2) gitConfig is available throughout the pipeline, (3) the DEPLOY phase reuses the pre-initialized config instead of re-calling initializeRepo(). The admin/dev fallback to local preserves development flexibility while protecting regular users from silent failures.

📁 Files Involved

• APIs/backend-vitto-api/src/app/module-generation/phases/module-gen-phase.executor.ts
• APIs/backend-vitto-api/src/app/module-generation/module-generation.types.ts

🔗 Related

• Decision ID: dev_1773241473104_ohjcp2h
• Session: 203
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation