---
type: "synthesis"
tags: ["synthesis", "precision", "claims"]
spans: ["video", "paper"]
id: "synthesis-single-agent-clarified"
sources: ["cross-day"]
---
# Synthesis: 'Single Agent' is Actually 'Single Orchestrator'

The video ([[claim-icm-superiority]], [[concept-icm-d1]]) repeatedly says **single agent**. The paper sharpens this — see [[entity-claude-code]]:

> All ICM testing used Opus 4.6 as primary orchestrator + Sonnet 4.6 as subagent workers. Within a stage, Opus delegates sub-tasks to faster Sonnet subagents — and the delegation is itself folder-driven (the agent reads `CONTEXT.md` to decide what to delegate).

## The precise claim

ICM is **single-ORCHESTRATOR with folder-driven subagent delegation**, not strictly single-agent in execution. The paper's exact claim is **"no orchestration framework,"** not **"no second model."**

## Why this matters

The claim survives the nuance: the **engineering** complexity ICM avoids is the framework layer (LangChain graphs, AutoGen routing, Semantic Kernel planners — see [[entity-langchain]], [[entity-autogen]], [[entity-semantic-kernel]]). Whether one model or two run within a stage is an internal implementation detail driven by [[entity-claude-code]]'s own subagent feature.

## Communication discipline

When summarising ICM to a sceptic, **say "single orchestrator, no orchestration framework"** rather than "single agent." The skeptic who finds out about Sonnet subagents will accuse the source of overselling otherwise.

See [[arc-talk-vs-paper-altitude]], [[entity-claude]], [[entity-claude-code]].