---
type: "synthesis"
tags: ["foil", "frameworks", "contrarian"]
spans: ["video", "paper"]
id: "recurring-foil-frameworks"
sources: ["cross-day"]
---
# Recurring Foil: The Framework Triumvirate

Both sources need an opponent to argue against. The cast:

- **[[entity-langchain]]** — appears in both. The canonical orchestration foil.
- **[[entity-semantic-kernel]]** — appears in both. Microsoft's competitor; ironic because it also uses the term "skill" (different sense).
- **[[entity-autogen]]** — appears only in the paper. Microsoft's multi-agent conversation framework.

## Treatment evolution

**Video** ([[contrarian-frameworks]], [[quote-absurdities]]): blanket dismissal as "absurdities." Rhetorical.

**Paper** ([[contrarian-frameworks-overkill]]): bounded claim — overhead for sequential human-reviewed workflows; **recommended** for the use cases ICM excludes (real-time multi-agent, high concurrency). Analytic.

## The scope rule

The paper effectively divides the design space:

| Use case | Recommended |
|---|---|
| Sequential pipeline, human review at each step | ICM ([[concept-icm-d2]]) |
| Real-time multi-agent collaboration | AutoGen / LangChain |
| Heavy programmatic branching, automated error recovery | Airflow / Temporal / Prefect |
| Regulated context with formal traceability requirements | Frameworks with audit tooling |
| High concurrency / high throughput | Specialized agent frameworks |

## Why this matters

A reader who only watches the video will think frameworks are bad. A reader who only reads the paper sees a respectful design-space partition. The corpus position is the latter; the video's rhetoric should be treated as **provocation**, not the considered claim.

See [[tension-absurdities-vs-bounded-scope]], [[tension-voice-future-vs-paper-non-support]].