---
type: "synthesis"
tags: ["tension", "scope", "future-work"]
spans: ["video", "paper"]
id: "tension-voice-future-vs-paper-non-support"
sources: ["cross-day"]
---
# Tension: The Voice Finale Lives Outside the Paper's Scope

The most exciting moment in the video is the finale — see [[concept-voice-collaboration]], [[claim-voice-future]], [[quote-voice-control]]: real-time voice-driven AI collaboration during a live call.

The paper's most honest limitation is **its explicit non-support** of exactly that use case. ICM ([[concept-icm-d2]]) is for **sequential, human-reviewed** workflows. Real-time multi-agent collaboration and high-concurrency systems are explicitly out of scope; the paper recommends [[entity-autogen]], [[entity-langchain]], or [[entity-semantic-kernel]] for those.

## How to hold both honestly

1. **The voice demo is real but lives outside ICM as the paper defines it.** It uses an ICM-shaped folder substrate, but the loop (voice → STT → Claude → file I/O during a live call) is exactly the **real-time multi-agent class** the paper excludes.
2. **Security ([[question-voice-security]]) is unresolved.** The paper doesn't engage it because it doesn't claim it.
3. **Forward extension, not contradiction.** The video sketches a future where ICM's folder substrate becomes the shared workspace for live voice collaboration. The paper would call this a separate research program.

## A reconciliation

The voice finale is best read as **"ICM workspaces become the shared state for live collaboration"** — folder-as-substrate persists, but the orchestration moves from human-paced review gates ([[action-review-gates]]) to live voice commands. The paper would require that program be benchmarked separately before being claimed.

See [[arc-talk-vs-paper-altitude]], [[open-arc-what-remains]].