Provider and attribution
Microsoft STATE-Bench
- Registry state
- registered
- Rights state
- approved
- Provider group
- microsoft
STATE-Bench by Microsoft and STATE-Bench contributors (MIT License)
Release planning · no model scores
Exact V3 collection, facet, metric, lineage, identity and rights mapping for STATE-Bench v0.8 main from Microsoft STATE-Bench.
Provider and attribution
STATE-Bench by Microsoft and STATE-Bench contributors (MIT License)
V3 evidence records
A repeated upstream benchmark can map to several collections. Each record below preserves its own task role, facets, capability atoms, subject identity, metrics, lineages and exclusions.
primary evidence · business-automation/statebench/state-bench-v0-8-main
Which models are best at business workflow automation?
Collection facets
Workflow completion · objective · 25%
Reach the correct end state across multiple dependent steps.
Exception recovery · hybrid · 25%
Recover from missing data, failed tools, and conflicting state.
Approval and action safety · hybrid · 25%
Pause for authorization before consequential or irreversible actions.
Operational communication · hybrid · 25%
Explain progress, blockers, and handoffs without excess narration.
Capability atoms
Subject identity
Usable evidence lineages
statebench-v0-8-main/harnessed-modelExact metric contract
| Metric | Lineage | Subject | Protocol | Use |
|---|---|---|---|---|
v0.8.main.overall.pass_at_1STATE-Bench Main v0.8 — Overall — Task completion pass@1 | statebench-v0-8-main | harnessed-model | statebench-v0.8.main | usable |
v0.8.main.overall.mean_ux_scoreSTATE-Bench Main v0.8 — Overall — Mean UX score | statebench-v0-8-main | harnessed-model | statebench-v0.8.main | usable |
Exclusions and blockers
No mapping-level exclusion is recorded; the page-level release gate still applies.
Mapping note
Keep benchmark version and system configuration as hard partitions.