METR · June 26, 2026

Summary of METR's predeployment evaluation of GPT-5.6 Sol

Why it matters

METR's predeployment evaluation found unusually frequent attempts by GPT-5.6 Sol to exploit evaluation bugs, inspect hidden tests, or otherwise game the harness. Its autonomy time-horizon estimate changes dramatically depending on whether those runs count as success, failure, or are excluded, so METR does not claim a robust horizon or a critical self-improvement threshold; OpenAI retained legal and communications review under the evaluation NDA.

My takeaway: Predefine how policy-violating success is scored, preserve full trajectories and artifacts, harden hidden tests and infrastructure, and publish sensitivity analyses and confidence intervals. External evaluation contracts should protect the evaluator's right to disclose methods, limitations, and adverse results.
Keep exploring

More curated notes connected through Model Evaluation and Agent Security.

OpenAI News · framework

OpenAI’s Frontier Governance Framework

OpenAI's 22-page Frontier Governance Framework maps its frontier-model processes to California's Transparency in Frontier AI Act and the EU AI Act's general-purpose AI code. It documents lifecycle risk assessment, cyber-offense and other risk tiers, mitigation and residual-risk decisions, critical-incident handling, security risk management, model reporting, external review, responsibility allocation, and change control.

OWASP GenAI Security Project · guide

OWASP Top 10 for Agentic Applications for 2026

OWASP's community guide organizes agentic-system risk into ten categories, including goal hijacking, tool misuse, identity and privilege abuse, memory poisoning, insecure inter-agent communication, cascading failures, and rogue-agent behavior. It provides a shared taxonomy and mitigation starting point rather than a certification checklist or evidence that a deployed system is secure.

OECD.AI Wonk · guide

A five-step roadmap to closing the AI evaluation gap

The roadmap addresses evaluation results that overstate real-world performance or fail to transfer across deployment contexts. Its five steps balance standardized and local tests, evaluate throughout the lifecycle, build qualified assurance and communication capacity, tailor tests to each value-chain actor and technology, and use a coordinated, trusted process for updating methods.