ibl.ai Agentic AI Blog

Insights on building and deploying agentic AI systems. Our blog covers AI agent architectures, LLM infrastructure, MCP servers, enterprise deployment strategies, and real-world implementation guides. Whether you are a developer building AI agents, a CTO evaluating agentic platforms, or a technical leader driving AI adoption, you will find practical guidance here.

Topics We Cover

Featured Research and Reports

We analyze key research from leading institutions and labs including Google DeepMind, Anthropic, OpenAI, Meta AI, McKinsey, and the World Economic Forum. Our content includes detailed analysis of reports on AI agents, foundation models, and enterprise AI strategy.

For Technical Leaders

CTOs, engineering leads, and AI architects turn to our blog for guidance on agent orchestration, model evaluation, infrastructure planning, and building production-ready AI systems. We provide frameworks for responsible AI deployment that balance capability with safety and reliability.

Back to Blog

University of Oxford: Who Should Develop Which AI Evaluations?

Jeremy WeaverFebruary 11, 2025
Premium

The memo proposes a framework for assigning AI evaluation development to various actors—government, contractors, third-party organizations, and AI companies—by using four approaches and nine criteria that balance risk, method requirements, and conflicts of interest, while advocating for a market-based ecosystem to support high-quality evaluations.

University of Oxford: Who Should Develop Which AI Evaluations?



Summary of Read Full Report (PDF)

This research memo examines the optimal actors for developing AI model evaluations, considering conflicts of interest and expertise requirements. It proposes a taxonomy of four development approaches (government-led, government-contractor collaborations, third-party grants, and direct AI company development) and nine criteria for selecting developers.

The authors suggest a two-step sorting process to identify suitable developers and recommend measures for a market-based ecosystem fostering diverse, high-quality evaluations, emphasizing a balance between public accountability and private-sector efficiency.

The memo also explores challenges like information sensitivity, model access, and the blurred boundaries between evaluation development, execution, and interpretation. Finally, it proposes several strategies for creating a sustainable market for AI model evaluations.

The authors of this document are Lara Thurnherr, Robert Trager, Amin Oueslati, Christoph Winter, Cliodhna Ní Ghuidhir, Joe O'Brien, Jun Shern Chan, Lorenzo Pacchiardi, Anka Reuel, Merlin Stein, Oliver Guest, Oliver Sourbut, Renan Araujo, Seth Donoughe, and Yi Zeng.

Here are five of the most impressive takeaways from the document:

  • A variety of actors could develop AI evaluations, including government bodies, academics, third-party organizations, and AI companies themselves. Each of these actors have different characteristics, and different strengths and weaknesses. The document outlines a framework for deciding which of these actors is best suited to develop specific AI evaluations, based on risk and method criteria.
  • There are four main approaches to developing AI evaluations: AI Safety Institutes (AISIs) developing evaluations independently, AISIs collaborating with contracted experts, funding third parties for independent development, and AI companies developing their own evaluations. Each approach has its own advantages and disadvantages. For instance, while AI companies developing their own evaluations might be cost-effective and leverage their expertise, this approach may create a conflict of interest.
  • Nine criteria can help determine who should develop specific evaluations. These criteria are divided into risk-related and method-related categories. Risk-related criteria include required risk-related skills and expertise, information sensitivity and security clearances, evaluation urgency, and risk prevention incentives. Method-related criteria include the level of model access required, evaluation development costs, required method-related skills and expertise, and verifiability and documentation.
  • A market-based ecosystem for AI evaluations is crucial for long-term success. This ecosystem could be supported by measures such as developing and publishing tools, establishing standards and best practices, providing legal certainty and accreditation for third-party evaluators, brokering relationships between third parties and AI companies, and mandating information sharing on evaluation development. Public bodies could also offer funding and computational resources to academic researchers interested in developing evaluations.
  • The decision of who develops AI evaluations is complex and depends on the specific context. The document emphasizes the importance of considering multiple factors, including the risk being assessed, the methods used, the capabilities of the potential developers, and the potential for conflicts of interest. It suggests that a systematic approach to decision-making can improve the overall quality and effectiveness of AI evaluations.

 

Related Articles

Shadow AI Is Already Inside Every Government Agency

Unsanctioned AI use is already routine across federal agencies, and in government the exposure is statutory rather than commercial — Privacy Act records sent to commercial providers, federal records generated in systems the agency cannot subpoena, supply-chain restrictions under EO 13873, and mosaic classification spillage. This post maps each exposure to its legal basis and gives the data-classification tiers that decide which workloads need managed cloud, agency-controlled infrastructure, or a fully air-gapped deployment.

ibl.ai EngineeringAugust 4, 2026

The Open-Weight Tipping Point: Two 2-Trillion-Parameter Models

Two models above 2 trillion parameters became available as open weights in a single week: Moonshot's Kimi K3 at 2.8T with a 1M-token context, and Alibaba's Qwen 3.8-Max at 2.4T with 95B active per token. This post does the memory arithmetic on what it actually takes to serve models that size, prices the alternatives, and explains why the durable advantage is model-agnostic infrastructure rather than any single model.

ibl.ai EngineeringAugust 3, 2026

AI Agent Security Is an Infrastructure Problem, Not a Feature

Uber's security lead says securing AI agents is what keeps him up at night, and Google just shipped agent evaluation tooling to production. The tooling layer is maturing; the infrastructure question underneath it is not. This post explains why you cannot fully secure an agent whose reasoning runs on someone else's servers, and gives the five-question perimeter test to run on any agent platform before you sign.

ibl.ai EngineeringAugust 2, 2026

Q2 2026 Earnings: AI Infrastructure Pays — For Whoever Owns It

The quarter ending June 30, 2026 settled the question of whether AI infrastructure pays off: AWS grew 37% to $42.2B, Google Cloud 82% to $24.8B, Azure crossed $100B annualized, and Copilot passed 30 million paid seats. This post does the arithmetic on what those seats cost a 10,000-person enterprise versus token-priced and self-hosted alternatives, and shows where the return actually lands.

ibl.ai EngineeringAugust 1, 2026

See the ibl.ai AI Operating System in Action

Discover how leading universities and organizations are transforming education with the ibl.ai AI Operating System. Explore real-world implementations from Harvard, MIT, Stanford, and users from 400+ institutions worldwide.

View Case Studies

Get Started with ibl.ai

Choose the plan that fits your needs and start transforming your educational experience today.