What it measures

Frontier Risk Evaluation for National Security and Public Safety (dual-use CBRN, critical infrastructure, autonomous cyber risk).

Reading the measurement

Lower error is better on this measure. Inspect substitutions, omissions and additions, and retain the language, acoustic conditions and normalization policy. A clean-audio average can conceal failures in noisy or specialist speech.

Published evaluation

The linked publication documents the task and scoring procedure. Model results retain the source’s evaluation setting, native score units and available uncertainty.

Where this fits in an evaluation suite

Format compliance, preference, truthfulness, and safety require separate measurements. Keep desirable writing style from masking factual errors.

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

Record the source publication, benchmark version, scoring units, denominator, tool access and attempt budget. Preserve uncertainty and distinguish developer-reported results from independent evaluations.

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

  1. Scale Labs — evaluation methodology and results ↗

    Scale Labs / SEAL · 2026

Reviewed 2026-10-26. Explanation and interpretation by RLTasks. Benchmark ownership remains with its original authors.