concept · concepts/The Human Sandwich.md
The Human Sandwich
The work pattern for complex agent collaboration, coined by an Every employee: humans are the bread on either side of the AI's work — a human sets the frame, the AI collapses the task, and a human judges and extends the result.
The pattern
For any complex, original task, Dan Shipper reports the best results come from "an AI and a human going back and forth in the same workspace" (Codex, Claude Code, "Claude Cowork") — not from handing work off and walking away. The three beats:
- Human sets the frame — what we're trying to do and what counts as good.
- AI collapses the task — drafts, searches, codes, summarizes, compares.
- Human judges and extends — Is this good? Where does it belong? What should happen next?
The human owns the start and end of each agent task: defining the frame, verifying the output is done well, and finding the next piece of work. This is why, per Shipper, "both of these modes require you or another human in order to work well." The sandwich is the concrete shape of the collaboration mode (as opposed to fully delegated "employee" agents).
Why it matters
The human's contribution sits exactly where models are weak: judgment about what needs to be done right now and what counts as different rather than default (AI Commoditizes Expertise). The sandwich is the operational reason agents "still need humans."
The sandwich in a wet lab (2026)
Anthropic — Investigating Vault Particles with Claude is the pattern outside knowledge work. The team's own verbs: Claude worked "under our direction," they "advised on the analysis decisions," and when the cryo-EM processing went off-script they "told it to stop improvising" — "Please let's do normal things unless they don't work." Humans chose the 44 candidate proteins (frame) and judged the resulting maps (extend); Claude searched 15 billion sequences, designed constructs and ran RELION (collapse).
Two refinements the case adds:
- The bread has to be load-bearing. The team's errors were caught fast where they had expertise and ran for two weeks where they didn't. The judging slice only works if the judge knows the domain (Verification Requires Domain Knowledge).
- The frame step includes overruling the model. Claude argued against the purification method that ended up working. A human who only approves or rejects what the model proposes would have lost the 48× speedup.
Connections
- Verification Requires Domain Knowledge — the precondition for the "judge" slice.
- Agents as Employees vs Human-Agent Collaboration — the sandwich is the signature pattern of the collaboration mode.
- AI Commoditizes Expertise — the "judge and extend" slice is where human difference defeats Slop.
- The Infinite Backlog — the human's "what's next?" step is how the backlog gets prioritized.
- Agent Autonomy Spectrum — the sandwich implies semi-synchronous working, not full autonomy.
- The Bottleneck Shift — the human "frame" and "what's next?" steps are exactly the what-to-do judgment Ethan Mollick calls the new bottleneck.
- Communication and Control Are Intertwined — see also: framing + steering is control exercised through communication.
- Human-in-the-Loop by Exception — cross-domain twin: the data-pipeline version of the same pattern — automate the collapsible bulk, reserve the human for the judgment slice (and bank that judgment so it's paid once).
- Placement and Judgment Over Raw Execution — the sandwich is the AI-side instance of Move 2 ("reserve human judgment for the exception") in that synthesis.
Sources
- The AI Daily Brief — Why Agents Still Need Humans — via Dan Shipper — After Automation.
- Anthropic — Investigating Vault Particles with Claude — the pattern observed in a biology lab, including its failure mode when the human lacks the domain.