🏗️ Architecture: How to expose Vitto as the platform's orchestration gateway ...

Date: 2026-02-10
Time: 23:03:09 UTC
Session: gspace1-104.2
Agent: orchestrator
Confidence: 88%
Status: ✅ Documented

📋 Decision Context

Question:

How to expose Vitto as the platform's orchestration gateway for multi-agent coordination?

Task: Session 104: Vitto Orchestration Gateway

🎯 Decision Made

Chosen:

POST /engine/orchestrate endpoint with dual-mode: direct_delegation (explicit agent requirements) or full_workflow (Vitto decomposes via 4-phase ANALYZE→PLAN→EXECUTE→VERIFY). MCP agent gateway gets 'orchestrate' action that routes through Vitto instead of creating handoffs manually.

Options Considered:

1. Vitto orchestrate endpoint with dual-mode delegation
2. Force all handoffs through Vitto (breaking change)
3. Add orchestration layer in MCP only (no Vitto involvement)
4. Event-driven orchestration via WebSocket commands

💭 Reasoning

Vitto already had DelegationManagerService with full lifecycle management (reliability tracking, retry logic, checkpoint escalation) but no external entry point. Adding orchestrate endpoint lets agents delegate coordination to Vitto. Two modes: (1) direct_delegation when agents know exactly what sub-agents they need — skips ANALYZE/PLAN, goes straight to delegateMultiple(). (2) full_workflow when the request is abstract — Vitto runs its full 4-phase pipeline which may itself delegate during EXECUTE phase. This preserves backward compatibility (handoff_create still works) while making orchestration the preferred path.

📁 Files Involved

• apis/backend-vitto-api/src/app/engine/vitto-engine.service.ts
• apis/backend-vitto-api/src/app/engine/vitto.controller.ts
• MCP/mcp-gograb-ai/src/tools/handoff.ts
• MCP/mcp-gograb-ai/src/tools/gateways/agent-gateway.ts
• apps/gograb-ai-extension/background/mcp-connector.js

🔗 Related

• Decision ID: dev_1770764589644_hzzbvsj
• Session: 104
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation