# One agent, one job, one output

Status: DRAFT, nothing posted. Single-image infographic, 2 slide(s), no cover. Idea IB-0169.

## What it shows

How a batch of work is split across parallel agents so each owns one slice and one output file, then merged by one conductor. Slide 2 contrasts fan-out work with work that must stay serial.

No numbers appear on the slides unless listed below.

## Claims and sources

| Claim | Source (agency-operator unless stated) | Read-date |
|---|---|---|
| Partition into non-overlapping batches; each agent gets one item or one disjoint slice; no two items resolve to the same output path | `.claude/skills/fan-out/SKILL.md` (Process step 1) | 2026-10-11 |
| Dispatch all agents in one message | `.claude/skills/fan-out/SKILL.md` (Process step 3) | 2026-10-11 |
| Agents never deploy or commit; the orchestrator merges serially | `.claude/skills/fan-out/SKILL.md` (Process steps 5-6) | 2026-10-11 |
| Do not fan out when items poll each other, share one output file or depend on each other's results | `.claude/skills/fan-out/SKILL.md` (When to Use) | 2026-10-11 |