Skip to main content
PrincipalBench measures a model as an orchestrator: the principal that decomposes work, supervises worker agents and synthesises their outputs. Use version 2. Version 1 cannot support model comparisons, and its published rankings are withdrawn.
The repository README still shows v1 results, including a ranking with Llama-3.1-70B first. Those rankings are withdrawn by the PrincipalBench v2 paper. Do not cite them.

Why v1 was withdrawn

An audit of v1 against its own code and data found that a model-free policy that flags every output scores 0.52 PrincipalScore.

How v2 works

1

Planning phase

The orchestrator decomposes the task from the question alone, and is scored on that plan.
2

Supervision phase

The orchestrator reviews gold-aligned worker reports. Half of the episodes are clean controls. Failures are derived from each hop’s own gold output.
3

Synthesis

The final step is withheld, so the orchestrator must synthesise the answer itself.
4

Scoring

Detection is chance-corrected with Youden’s J. Coherence is measured on the orchestrator’s own ledger.

v2 dataset

Reference policies

v2 behaves as a benchmark should: degenerate strategies score 0.00 on detection and at most 0.50 PrincipalScore, and only a full oracle reaches 1.00. The paper reports reference policies, not model rankings. It releases v2 as the basis for future, reproducible orchestrator evaluations.

Get the code

PrincipalBench v2 paper

The audit, the v2 protocol and the reference-policy results.

Repository

Harness, tasks, failure library and scoring code.
Last modified on November 15, 2026