Architecture: How to enrich the platform generation pipeline with building...

Documentation for Sessions

🏗️ Architecture: How to enrich the platform generation pipeline with building...

Date: 2026-03-20
Time: 17:30:58 UTC
Session: gspace1-244.4
Agent: backend
Confidence: 93%
Status: ✅ Documented

📋 Decision Context

Question:

How to enrich the platform generation pipeline with building block patterns from gmodules1?

Task: S244: Platform generation quality v3

🎯 Decision Made

Chosen:

6-change pipeline enrichment: (1) Update implement.prompt.md with 5 building block sections — workflow definitions, filter definitions, entity lookups, module registration, seed data. (2) Enrich system-analyze.prompt.md to detect buildingBlocks per entity. (3) Add BuildingBlockSpec/SchemaSpec/SeedDataSpec types. (4) Wire ANALYZE→EXECUTE metadata flow. (5) Extract schemas/seedData from LLM output. (6) Seed data to backend-api in INTEGRATE phase. Platform-base-template also updated to include @libs-core/workflow-engine.

Options Considered:

Prompt-only update (no code changes)
Template + Prompt (chosen — additive, low risk)
Full 13-phase pipeline redesign (over-engineering)

💭 Reasoning

gspace1 had 21 libs/core libraries covering workflow, events, media, filters, entity-lookup, module-base — all available in the platform-base-template's tsconfig. But implement.prompt.md only taught ~30% of them. gmodules1's product-catalog module (most mature) uses all these patterns. The gap was not infrastructure — it was prompt completeness. The ANALYZE phase also needed buildingBlocks detection (hasWorkflow, foreignKeys, hasMedia, filterableFields) so the EXECUTE phase LLM knows WHICH patterns to apply per entity. normalizeAnalyzeResult() silently stripped buildingBlocks — critical fix. Schema registration already handled by BackendSetupPhaseService — only seed data added to INTEGRATE phase to avoid duplication.

📁 Files Involved

APIs/backend-vitto-api/src/prompts/module-gen/implement.prompt.md
APIs/backend-vitto-api/src/prompts/module-gen/system-analyze.prompt.md
APIs/backend-vitto-api/src/app/module-generation/phases/execute.phase.ts
APIs/backend-vitto-api/src/app/module-generation/phases/integrate.phase.ts
APIs/backend-vitto-api/src/app/module-generation/module-generation.types.ts
repo-templates/platform-base-template/tsconfig.base.json

🔗 Related

Decision ID: dev_1774027858330_t40mkst
Session: 244
Workspace: gspace1

Auto-generated by MCP Smart Consolidation