🏗️ Architecture: How should the LLM prompt handle DataController's non-standa...

Date: 2026-02-25
Time: 14:47:20 UTC
Session: gspace1-138.7
Agent: backend
Confidence: 97%
Status: ✅ Documented

📋 Decision Context

Question:

How should the LLM prompt handle DataController's non-standard API URLs?

Task: DataController URL integration strategy

🎯 Decision Made

Chosen:

Auto-correct to UniverseDataService (no prompt changes)

Options Considered:

1. Modify implement.prompt.md to teach LLM DataController URL patterns
2. Auto-correct standard REST URLs to DataController format post-generation
3. Use UniverseDataService abstraction in auto-correction

💭 Reasoning

Plan reviewer correctly identified that changing the LLM prompt for DataController URLs is high-risk. DataController uses non-standard patterns (POST .../query for listing, POST .../insert for create). LLMs are trained on millions of standard REST examples. Changing the prompt would destabilize output quality. Instead: let LLM generate clean standard REST services (which it's good at), then auto-correction mechanically rewrites HttpClient to UniverseDataService which already handles spaceId/universeId resolution, caching, and DataController URL construction. This is a string transformation, not an LLM task.

📁 Files Involved

• apis/backend-vitto-api/src/app/module-generation/validation/auto-correction.service.ts
• libs/libs-foundational/core-angular/src/lib/services/universe-data.service.ts

🔗 Related

• Decision ID: dev_1772030840342_o4lxiqe
• Session: 138
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation