---
id: "claim-agent-equation"
type: "claim"
source_timestamps: ["§ Can Someone Please Define a \"Harness\"?"]
tags: ["definitions", "architecture"]
related: ["concept-agent-harness", "quote-harness-definition", "quote-intelligence-vs-usefulness"]
confidence: "high"
testable: false
speakers: ["Vivek Trivedy"]
---
# Agent = Model + Harness

## The Claim

A raw model is **not an agent**. An agent is strictly the combination of:

- a **model** (which provides intelligence), and
- a **harness** ([[concept-agent-harness]]) (which provides state, tool execution, feedback loops, and constraints).

If a component in the system is not the model, it is part of the harness — captured pithily by [[quote-harness-definition]].

## Confidence: High

This framing is now mainstream across practitioner essays (Martin Fowler), vendor docs (Anthropic's evals guide), and research surveys on agent architectures. The equation is partly definitional, but it converges with how LangChain, Anthropic, OpenAI, and academic taxonomies all describe agents.

## Why It Matters

- It separates the **intelligence axis** (model post-training, RLHF, scale) from the **engineering axis** (harness primitives, orchestration, state).
- It implies that harness engineering is a **first-class discipline** orthogonal to model R&D — reinforced by [[contrarian-harness-optimization]] and [[contrarian-harness-longevity]].
- It anchors the [[framework-harness-derivation|working-backwards framework]] for designing new agent features.

## Testable?

Not directly — the equation is a definitional decomposition. The downstream consequences (e.g., [[claim-long-horizon-compounds]], [[claim-harness-overfitting]]) are empirically testable.