🏗️ Architecture: What is the updated plan for the 7 remaining Jarvis evolutio...

Date: 2026-03-18
Time: 00:16:29 UTC
Session: gspace1-231.11
Agent: documentation
Confidence: 91%
Status: ✅ Documented

📋 Decision Context

Question:

What is the updated plan for the 7 remaining Jarvis evolution gaps after S231.2 completion?

Task: S231.4 — Updated Jarvis evolution plan

🎯 Decision Made

Chosen:

3-tier priority plan: Tier 1 (do next): Teams channel adapter (1 session), VM snapshot auth persistence (1.5 sessions), OAuth plugin interface code-only (0.5 session). Tier 2 (after Tier 1): Human takeover VNC modal (1.5 sessions), Cross-channel genome (2 sessions). Tier 3 (defer): Browser extension relay (3 sessions), Voice pipeline (2 sessions). Resolved: OTEL gap closed by in-app observability alternative.

Options Considered:

1. OTEL first (rejected: already solved via in-app alternative)
2. Browser extension before VM snapshots (rejected: VM snapshots are more versatile)
3. Voice pipeline now (rejected: user explicitly deferred)
4. Teams last (rejected: highest ROI/effort ratio, should be first)

💭 Reasoning

Prioritization based on ROI/effort ratio and dependency chains. Teams channel is highest ROI (enterprise unlock, 1 session, no external deps, 4 existing adapters as templates). VM snapshots enable the entire Phase 2 CU vision. OAuth plugin code can be written without deploying Nango. VNC modal depends on VM snapshots working. Browser extension solves 80% of same problem as VM snapshots — defer unless users avoid VMs. Voice explicitly deferred by user. OTEL marked resolved because in-app observability covers 80% of the need using existing execution-traces data and taskId as correlation key.

📁 Files Involved

• docs/superpowers/specs/2026-03-17-vitto-jarvis-evolution-spec.md
• docs/english/Infrastructure/vitto-infrastructure-and-gaps..md

🔗 Related

• Decision ID: dev_1773792988956_ct8l1dp
• Session: 231
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation