---
id: "concept-can-it-carry"
type: "concept"
source_timestamps: ["00:03:56", "00:04:02"]
tags: ["evaluation-metrics", "workflow-automation"]
related: ["concept-system-matters", "framework-private-bench-suite", "quote-can-it-carry"]
definition: "The ability of an AI model to sustain context, manage risk, and execute complex deliverables across multiple formats over a long workflow."
sources: ["s26-gpt55-claude-gemini"]
sourceVaultSlug: "s26-gpt55-claude-gemini"
originDay: 26
---
# Can It Carry?

## Definition
The ability of an AI model to sustain context, manage risk, and execute complex deliverables across multiple formats over a long workflow.

## The Paradigm Shift
This is the **central thesis** of the source. The old frontier question — 'can the model answer this?' — was suited for chatbots and Q&A. The new question is: **'can the model carry this?'** (See [[quote-can-it-carry]].)

## What 'Carrying' Means Operationally
A carrying-capable model can:
- **Maintain context** over a long thread without losing the thread (cf. [[prereq-llm-context-windows]]).
- **Carry a deliverable across multiple file formats**: docs, spreadsheets, PDFs, code, images.
- **Manage legal and ethical risk** without smoothing over the dangerous parts.
- **Execute a data migration** far enough that a human only checks the *edge cases* rather than rebuilding the whole database (see [[framework-data-migration-pipeline]]).

## Why It's a Bigger Bar
Most frontier models look interchangeable on single-turn answers (see [[claim-public-benchmarks-flatten]]). The carry test is multi-step, messy, and exposes architectural and system-level differences that one-shot benchmarks hide. This is what motivates the [[framework-private-bench-suite|Private Bench]] methodology.

## Related
- [[concept-system-matters]] — carrying requires tools, not just weights.
- [[entity-gpt-5-5]] — the model the speaker claims is best at carrying.
- [[action-route-complex-execution]] — the practical routing implication.


## Related across days
- [[concept-spec-quality-bottleneck]]
- [[concept-intent-engineering]]
- [[claim-bottleneck-shift]]
- [[concept-specification-vs-execution]]
- [[arc-spec-and-intent-bottleneck]]