What it measures
Agents navigate enterprise tools and change state across business workflows.
How to read the result
Database-state grading helps distinguish a verbal claim of completion from actions that actually changed the system.
Limits and comparison traps
Pin the environment and starting state. Tool availability and search friction can dominate an apparent model difference.
Benchmark reference notes
Stateful multi-step enterprise workflows across 8 business domains graded on final database state.
Where this fits in an evaluation suite
A transcript that says “done” is weaker evidence than the verified final state. Track policy violations, recoveries, and invalid attempts alongside success.
Start with a capability hypothesis, then choose a second test with a different failure mode. Keep the checkpoint, reasoning effort, agent tools, sampling policy, and scoring procedure fixed when measuring a training intervention. Record failures and missing outputs in the denominator.
A reproducible comparison
Use the exact implementation, version, task subset, tool access, attempt budget, and judge described by the source.
Publish the exact run configuration, item coverage, score units, and available uncertainty. If a source supplies only an aggregate or a single run, preserve that limit. A new model name or a rounded score alone does not establish a capability improvement.
PRIMARY EVIDENCE & FURTHER READING
Reviewed 2026-10-26. Explanation and interpretation by RLTasks. Benchmark ownership remains with its original authors.