Bugfix: How should GenerationHubService forward Vitto-generated modu...
Documentation for Sessions
🐛 Bugfix: How should GenerationHubService forward Vitto-generated modu...
Date: 2026-02-12
Time: 04:41:21 UTC
Session: gspace1-109.3
Agent: angular
Confidence: 100%
Status: ✅ Documented
📋 Decision Context
Question:
How should GenerationHubService forward Vitto-generated modules to the receiver?
Task: Session 109: Connect GenerationHub to AIModuleReceiverService
🎯 Decision Made
Chosen:
Injected AIModuleReceiverService into GenerationHubService and added forwardVittoModulesToReceiver() called from module-gen.completed SSE handler
Options Considered:
- Add another signal-based effect (wouldn't work for Vitto events)
- Direct injection + forwarding in SSE handler (chosen)
- Event bus decoupling (over-engineering for now)
💭 Reasoning
The original orchestration flow used an effect watching lastOrchestrationResult signal, but Vitto SSE events use different event types (module-gen.completed vs orchestration_complete). The signal-based effect never fires for Vitto. Direct injection and forwarding in the SSE handler is the correct pattern — it bridges the two codepaths without modifying the existing orchestration flow. Verified no circular dependency: modularity-lib doesn't import ai-generation-hub.
📁 Files Involved
libs/libs-ai/ai-generation-hub/src/lib/services/generation-hub.service.tslibs/libs-structural/modularity-lib/src/lib/services/ai-module-receiver.service.ts
🔗 Related
- Decision ID:
dev_1770871281530_o9fjs9e - Session: 109
- Workspace: gspace1
Auto-generated by MCP Smart Consolidation