---
id: "contrarian-frameworks-overkill"
type: "contrarian-insight"
source_timestamps: ["§1", "§5.1", "§5.2"]
tags: ["contrarian", "frameworks"]
related: ["concept-icm", "entity-autogen", "claim-token-efficiency"]
challenges: "The default assumption that agentic workflows require a multi-agent orchestration framework (LangChain, AutoGen, Semantic Kernel)."
sources: ["paper"]
sourceVaultSlug: "icm-paper-folder-architecture-2026Jun02"
originDay: 2
---
# Multi-agent frameworks are overhead for sequential, human-reviewed workflows

## What this challenges

The default assumption that agentic workflows *require* a multi-agent orchestration framework — LangChain, [[entity-autogen]], Semantic Kernel, and similar.

## The argument

For sequential workflows where a human reviews each step, frameworks introduce engineering overhead the problem does not require. The token-efficiency story ([[claim-token-efficiency]]) and observability story ([[concept-observability-side-effect]]) both come for free from the filesystem layout; the message-passing, branching, and coordination infrastructure of a framework adds cost without benefit for this workflow class.

## Bounded, not absolute

ICM **concedes the cases frameworks are built for**:

- real-time multi-agent collaboration,
- high-concurrency,
- programmatic branching,
- automated error recovery.

It claims only the *sequential / reviewable / repeatable* class. "Frameworks are absurd" overshoots; "frameworks are overhead **for this class**" is the defensible version.

## Validation status

The mechanical substitution (folders instead of framework orchestration) is technically sound and consistent with traditional software architecture patterns (Unix pipes, multi-pass compilation) — see [[prereq-unix-pipelines]] and [[concept-icm-as-compilation]]. The judgment that frameworks are *overkill* for this class is **defensible but value-laden and not experimentally demonstrated** — there is no published controlled comparison; that gap is [[question-controlled-comparison]].

## Counter-perspective

A critical reviewer might counter: for nontrivial workflows (branching logic, conditional steps, parallelism), the complexity may just be *shifted* from explicit code into conventions and human discipline. Orchestration tools (Airflow, Temporal, Prefect) earn their keep once flows become nontrivial. ICM is likely best suited to *linear or mildly branching workflows with strong human oversight*; beyond that, conventional orchestration retains advantages in correctness, monitoring, and scalability.


## Related across days
- [[contrarian-frameworks]]
- [[tension-absurdities-vs-bounded-scope]]
- [[recurring-foil-frameworks]]