SecurityTechInsider AI security & governance
EN/ NL
Governance

Trump's voluntary AI safety pact lacks oversight

Trump and AI leaders like Anthropic signed a voluntary safety pact with four layers of oversight on frontier AI. What does that mean for verifiability?

30 September 2026 4 min
Illustration for this article: Trump's voluntary AI safety pact lacks oversight. Water sheeting down a matte dark surface, breaking around an unseen obstruction.
Voluntary commitments without enforcement authority or common standards cannot substitute for independent public oversight of frontier AI systems. Image: SecurityTechInsider — original editorial illustration

You must now treat any voluntary safety commitment from an AI provider as a supplement to public oversight, not a replacement for it. Without independent authority to halt training, common evaluation standards and enforceable remediation, control remains internal to the company itself.

An analysis of 30 September 2026 of the voluntary safety pact on frontier AI oversight argues that the announced four-layer structure lacks the independence and enforcement authority needed to function as genuine external control. The pact describes internal controls, independent auditors and measures to prevent unintended system access to technical environments, but does not establish who sets evaluation standards, how auditors are accredited, what disclosure duties apply or what follows a negative finding. In our assessment, the distinction between a promise and evidence turns on whether a provider can produce a traceable record of testing, findings and remediation—and the pact as published does not clearly establish that chain.

What does the four-layer structure actually commit to?

The White House Accord on Superintelligence names four points as voluntary commitments by participating companies. The document explicitly frames these as sector discipline, not binding legal obligations. That framing determines the weight the structure carries. For a reader who recognises a layered safety case—in which each safety claim ties to evidence before a run proceeds—the structure aligns with that principle. But alignment with a principle is not the same as enforceability.

Where does the structure break down?

Three critical gaps emerge from the published text:

  • No common evaluation standard — companies may work toward standards and best practices, but no baseline applies across signatories.
  • No auditor accreditation system — the accord does not specify how evaluators are chosen, qualified or held accountable for their findings.
  • No enforcement authority — embedded evaluators may be given extensive access to systems and data, but cannot require corrective measures, restrict training or halt rollout.
  • No disclosure duties — the accord does not require companies to publish findings, negative verdicts or remediation actions.
  • No defined remediation deadlines — a negative finding triggers no specified response or timeline.

What does access without enforcement actually deliver?

Access without enforcement mainly delivers reassurance, not accountability. The distinction matters in practice. Banking supervisors can require corrective measures, restrict growth or close an institution. Embedded AI evaluators, by contrast, observe and report—but cannot act on what they find. That asymmetry is the core weakness: the pact describes who looks, but not against what standard the testing is done or what follows a negative finding.

The same tension surfaces in any self-regulation framework. A company that draws up its own rules and executes them itself may shift from self-regulation to self-interest. Without public standards and enforceable consequences, internal discipline cannot replace government oversight.

How should you assess a provider's safety commitment?

When a provider claims to operate under a voluntary safety pact or similar framework, you should verify the following:

  1. Obtain the evaluation standard in writing — the provider must name the specific criteria against which its systems are tested.
  2. Identify the evaluator and their independence — confirm that the auditor is not chosen, funded or directed by the provider itself.
  3. Request the testing record — ask for documentation of what was tested, when, by whom and against which standard.
  4. Confirm the remediation trail — verify that negative findings are recorded, assigned to an accountable owner and resolved within a defined timeframe.
  5. Check publication rights — establish whether findings are disclosed to you, to regulators or only to the provider.
  6. Clarify the stopping authority — confirm whether the evaluator can halt training or rollout, or only recommend that the provider do so.

Without these elements, the question remains open: who chooses the auditor, which standard do they apply and what follows a negative verdict. A comparable principle applies to any reporting framework, including those for model misalignment or frontier model duty of care—reporting a category has practical value only when there is a traceable record, an accountable owner and a defined response.

What tooling can and cannot do

Automated testing and audit frameworks can generate consistent evidence and flag anomalies at scale. They cannot substitute for human judgment about what standard to apply, how to weight competing risks or what remediation is proportionate. The pact shows that self-regulation can yield useful internal discipline and audit evidence. But the choice of standard, the independence of the evaluator and the authority to enforce consequences remain yours to assess and negotiate. Treat the provider's commitment as a starting point, not a conclusion.

Sources: This article draws on reporting and guidance from Reuters, Donald J. Trump (social-media post met de tekst van het akkoord), POLITICO, CNBC and Brookings Institution.

Marit Halversen

Written by

Marit Halversen

Covers AI governance and regulatory design, with a focus on how compliance obligations land on architecture rather than on paperwork.