# Model Tiers

The tier → model mapping — **the only file in this harness that names a model.** Policy, skills, and agent bodies speak in tier labels; when a model generation changes, this file and the owned agents' frontmatter `model:` pins are the two surfaces to edit, and nothing else moves.

## The mapping

| Tier | Model | Frontmatter pin | Character |
| --- | --- | --- | --- |
| **economy** | Claude Haiku 4.5 (`claude-haiku-4-5`) | `model: haiku` | Mechanical throughput: eval execution, data generation, regression sweeps |
| **standard** | Claude Sonnet 5 (`claude-sonnet-5`) | `model: sonnet` | The iteration workhorse: drafting, revising, comparing |
| **frontier** | Claude Opus 5 (`claude-opus-5`) | `model: opus` | Judgment: the ship gate, adversarial probing, second opinions |

## Updating the mapping

1. Edit the table above to the new generation.
2. Update the six owned agents' `model:` pins in `.claude/agents/` to match (`eval-runner`, `data-generator`, `regression-runner` → economy; `prompt-iterator` → standard; `judge`, `red-team` → frontier).
3. A generation change invalidates prompt certifications — `regression-runner` re-certifies the library and runs fresh demotion experiments (cheaper generations routinely absorb work from the tier above; the experiments are how the routing table finds out).
4. The `maintenance` audit checks the three-way parity — this table ↔ the pins ↔ the routing table's tiers — and flags any mismatch as drift.