From Score to Ship: How Evaluation Results Become a Launch Decision
A frontier model reaches launch day with hundreds of numbers attached: benchmark scores, judge win rates, arena previews, agent results, red-team findings, dangerous-capability measurements and outside testers' reports. None of them decides anything on its own. This final part follows how labs turn that pile into a go or no-go, what they publish in a system card, three launches where the process was tested in public, and the rules that now require parts of it.
1. Case file
2. The decision flow
Labs describe broadly similar steps. Evaluation results (Parts 2โ6) are compiled into a capability report and a safety report. A safety body reviews them against the lab's framework thresholds (Part 6) and recommends what safeguards are needed. Leadership decides: ship, ship with conditions, delay, or stop. In OpenAI's published framework, for example, a Safety Advisory Group makes recommendations and the CEO or a designee makes the final call and accepts any residual risk. Alongside the safety question runs a product question: is the new model actually better for users, with no regressions in behaviour? That second question is where the most visible failures have happened.
3. Release-gate simulator
You are the release committee
Tick what the evaluation results show. Our illustrative rules: safety thresholds can block or add safeguards, behaviour regressions can block, missing documentation delays a full release.
4. Anatomy of a system card
A model card (a format proposed by researchers in 2019) describes what a model is for and how it performs. A system card, the term OpenAI and Anthropic use, also covers safeguards, safety evaluations and the deployed system around the model. Reviewers report that recent Anthropic system cards run past 200 pages โ ๏ธ, while some launches have shipped with only a few pages.
What is usually inside
Tap a section.
5. Three launches that tested the process
6. The rules
From voluntary commitments to law
For the most capable "systemic-risk" models, the EU AI Act requires model evaluation including adversarial testing, risk assessment and mitigation, serious-incident reporting and cybersecurity. The voluntary Code of Practice's Safety and Security chapter is the main route to show compliance; signatories listed by the Commission include Anthropic, Amazon, Google, IBM, Microsoft, Mistral AI and OpenAI, with xAI signing only that chapter. California's SB 53 requires large frontier developers to publish safety frameworks and transparency reports and to report critical safety incidents. Evaluation results, in other words, are becoming regulated documents. Our Data Layer Part 8 covers the Act's training-data rules.
7. After launch
Evaluation does not stop at release. Labs watch usage for new failure modes, run staged rollouts (a share of users first), monitor for misuse, and update or roll back. Independent evaluators and arenas re-test within days (Part 4). Each problem found in production becomes a new test for the next model, which closes the loop back to Part 1.
8. The series, complete
Inside the Evaluation Layer: seven parts
9. Reading the numbers
- Primary / widely confirmed
- GPT-4o sycophancy update 25 Apr 2025, rollback from 28 Apr; expert testers' concerns; positive A/B results (OpenAI post-mortem). Gemini 2.5 Pro six-page model card ~3 weeks after preview; letter from 60 UK lawmakers; Google's response (Fortune, Time coverage). Claude Opus 4 under ASL-3 (Anthropic). OpenAI framework governance (Preparedness Framework v2). EU Code of Practice Safety and Security chapter and signatories (European Commission). SB 53 signed 29 Sep 2025 (Office of the Governor).
- Reported โ ๏ธ
- System-card page counts (reviewers' figures for 2026 Anthropic cards).
- Our illustrations
- Release-gate simulator; anatomy list (typical contents).
- Sources
- OpenAI: Expanding on what we missed with sycophancy
- British lawmakers accuse Google DeepMind of a breach of trust
- European Commission: General-Purpose AI Code of Practice
- Governor of California: SB 53 signed ยท FPF: SB 53 explained
- Anthropic: model system cards ยท Mitchell et al.: Model Cards for Model Reporting