How AI governance works

What can and cannot be guaranteed about an AI system?

Last reviewed

Share

Short answerA named deterministic control can permit only defined actions when all relevant traffic and actions cross that control. That guarantee applies to the constrained action layer. It does not apply to a general model with changing tools, retrieval, and integrations. You can never prove that a perception is correct.

These are two kinds of claim. The first is about a system's permissions. A named deterministic control can permit only defined actions when all relevant traffic and actions cross that control. This applies to the constrained action layer. It does not apply to a general model with changing tools, retrieval, and integrations or to traffic that bypasses the control.

The second is about the world: whether an image is real, whether a document is what it claims to be, whether a situation is what it appears to be. These are judgments about external reality, made from incomplete information. No amount of engineering converts them into proofs.

Left: a named control permits only a closed set of operations, such as read record, draft reply, summarize, and flag for review, for traffic that crosses it; an attempt to send funds is refused at that boundary. Right: a perception maps an open world of images, documents, and unseen situations onto a claim such as "this document is authentic," and no boundary can be drawn around it.
A named control can permit only a closed set of operations for traffic that crosses it. The world cannot be listed, so there is nothing to draw a boundary around.

This is a structural feature of every system that acts on perception, including human beings. A better model, more data, or more money changes how often a perception is right. None of them makes it provable.

Two consequences

  • Requirements that depend on perfect perception cannot be met. "Detect every deepfake" and "never misclassify" are requirements to solve an unsolved problem. A policy, contract, or vendor promise built on one is a commitment nobody can keep.
  • Verification lives at runtime. Action can be bounded and behavior can be recorded, so observing a system while it runs is where the available verification is. It is the part of assurance anyone can check.

Three claims, decoded

Vendor facts read October 8, 2026. Check the current page and your contract before relying on them.
ClaimWhat it can honestly meanProof to request
Zero data retentionNamed products or endpoints keep no copy of prompts and outputs after processing under an approved agreement. Anthropic and OpenAI list exceptions.The contract clause, covered products and models, and everything still kept.
We do not train on your dataCustomer content from a named business product stays out of training by default. OpenAI and Anthropic describe different exceptions.Which prompts, outputs, files, feedback, and flagged content are covered, and whether admins can prevent opt-in.
Your data stays in regionListed content is stored, and sometimes processed, in a chosen region. OpenAI separates storage, inference, metadata, and connected services.A split answer for storage, inference, routing, metadata, backups, support access, and connected apps.

The clearest example: deepfakes

Deciding whether a recording is genuine is a perception problem, so it inherits the limit. Three approaches are in use, and each has its own ceiling:

  • Detection models trained to spot synthetic media generalize poorly to generation methods they were not trained on. Reported performance falls sharply outside test conditions.
  • Provenance metadata, credentials attached when content is created, is usually stripped in transit. Recompression, screenshots, and re-sharing remove it, so the content reaching the widest audience is the least likely to carry any.
  • Watermarking is probabilistic. It produces false positives and false negatives, and a watermark that can be detected can eventually be forged.

What can be enforced sits on the provable side:

  • Bound the action. Where content is generated or distributed inside a governed system, the system can be prevented from producing or passing certain categories of content at all.
  • Observe the output. What a deployed system produced is a matter of record, if something is recording it.
  • Assign accountability. Obligations can attach to the platform, the model provider, or the person who prompted it. That is a policy choice, and it holds whether or not detection works.

The TAKE IT DOWN Act, signed in May 2025, is an enacted example. It criminalizes non-consensual intimate imagery, including synthetic material, and requires platforms to remove it within 48 hours. It places a duty on a named party and asks nobody to detect anything perfectly.

Next

Keep going

Take it into the vendor call

Free practical kitWhat can be audited and guaranteed: vendor claims, decoded. Fourteen claims AI vendors make, from zero data retention to hallucination-free: what each can honestly mean, the proof to request, and the red flag. Includes a one-page worksheet for the call. Eight pages, PDF.
Share this page

Sources

  1. Coalition for Content Provenance and Authenticity, C2PA Technical Specification 2.2. The publisher specification for signed provenance manifests; it does not guarantee that metadata will remain attached.
  2. TAKE IT DOWN Act, signed May 2025. Criminalizes non-consensual intimate imagery, including synthetic material, and requires platforms to remove it within 48 hours.