🏗️ Architecture: How should Vitto broadcast orchestration events to Chrome/VS...

Date: 2026-02-07
Time: 20:34:12 UTC
Session: gspace1-99.5
Agent: backend
Confidence: 90%
Status: ✅ Documented

📋 Decision Context

Question:

How should Vitto broadcast orchestration events to Chrome/VSCode extensions?

Task: Not specified

🎯 Decision Made

Chosen:

Relay pattern: Vitto POST → backend-ai-api /infrastructure/orchestration/events → NativeWsGateway broadcasts to all workspaces

Options Considered:

• No alternatives documented

💭 Reasoning

Vitto runs on its own port (3003) without direct WS connections to clients. Backend-ai-api already has NativeWsGateway connected to Chrome/VSCode extensions. Using a relay controller keeps Vitto decoupled while leveraging existing WS infrastructure. In-memory snapshot cache at relay enables REST status queries without hitting Vitto directly. Events broadcast to both gspace1 and editor2 workspaces.

📁 Files Involved

• apis/backend-ai-api/src/app/infrastructure/controllers/orchestration-relay.controller.ts
• apis/backend-vitto-api/src/app/connectivity/backend-ai-client.service.ts

🔗 Related

• Decision ID: dev_1770496452133_mbq2yo4
• Session: 99
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation