AI, three at a time · read · watch · listen

Entity

Verification Infrastructure

7 reads

The Economist · 2026-10-20 2026-10-23-w2

AI and scientific paperwork: productivity boon or slop flood

Grants are the version of this problem with no checker at all, which is why the Economist piece matters beside the code stories. A typical application takes about 34 days and succeeds about 20% of the time, so a researcher cutting a day a week to 45 minutes still loses most rounds once rivals do the same. Fabricated citations in 2.5m biomedical papers rose 12-fold to about 0.5%, and ICML submissions doubled to 24,000, with the cost landing on reviewers. Where Postgres has committers and PHP has maintainers, science has reader attention, and no mechanical test to ration it. Triage and digest agents start to look less like conveniences and more like core infrastructure.

The Wall Street Journal · 2026-10-23 2026-10-23-w3

AI Just Found a Bug That Puts up to 70% of the World's Websites at Risk

PHP2Shell puts a clock on the week's argument. Ryan Austin used GPT-5.6 Sol to take control of in-memory code in as few as a few dozen requests, in a bug class flagged decades ago and dismissed as too hard to exploit. The roughly ten-week embargo, from the Aug 11 call to the Oct 21 patch, broke on one Hacker News post, and a patch of close to 200 files now works as a blueprint. Finding was cheap for the researcher and the attacker alike; absorbing the fix across the long tail of unpatched servers is the slow part. For internet-facing open source, time-to-deploy is measured in hours, so mitigations have to ship before the diff does.

The Wall Street Journal 2026-10-23-1

AI Just Found a Bug That Puts up to 70% of the World's Websites at Risk

PHP2Shell had a patch ready and the exposure still sits with the long tail of unpatched PHP servers. Ryan Austin used GPT-5.6 Sol to take control of in-memory code in as few as a few dozen requests, in a bug class flagged decades ago and dismissed as too hard to exploit. The roughly ten-week embargo, from the Aug 11 call to the Oct 21 patch, broke on one Hacker News post. A patch of close to 200 files now doubles as a blueprint, so time-to-deploy is measured in hours.

YouTube 2026-10-20-1

AI Agents Cut 3-Day Portfolio Builds to Minutes — Jack McDonald, Apollo & Michael Manapat, Rowspace

Rowspace cut a CLO mock-portfolio build across 200-400 credit names from 2-3 days in Excel to minutes, about 80-90% complete, with the PM finishing the last 10%. The trust comes from staff encoding which of 20 sources wins, worked out with the client's finance team on site. That human-adjudicated rulebook is what the physics and grant-writing reads are missing.

arXiv 2026-10-20-2

Can Theoretical Physics Research Benefit from Language Agents?

The physics-agents paper names its promising uses (quantum error-correcting code search, Mathematica-verified constructions, proof checking), and each one has an external checker. The weak spots, taste and choice of approximation, have none, and the paper's two worked failures, reusing 'H' after a Jordan-Wigner transform and picking a path at random on a fork, are ambiguity errors. Rowspace shows the checker can be built by hand; this paper says where to build the next one.

The Economist 2026-10-20-3

AI and scientific paperwork: productivity boon or slop flood

Grant writing is the case with no checker at all. A typical application takes about 34 days and succeeds about 20% of the time, so one researcher cutting a day a week to 45 minutes still loses most rounds once rivals do the same. Fabricated citations across 2.5m biomedical papers rose 12-fold to about 0.5%, and ICML submissions doubled to 24,000. The cost lands on reviewers, and effort stops working as a signal of seriousness.

arXiv 2026-10-17-2

Agentic Reward Modeling: Verifying GUI Agent via Progressive Trajectory-Grounded Interaction

VAGEN treats verification as an agent job: read the trajectory first, then probe state only where evidence is thin. On OSWorld-Verified with a Sonnet actor, the same model checks tasks at 83.1% success in 17.4 steps versus 55.9% in 28.5 steps when it does them, and it hits 94.6 F1 against ProRe's 90.4. That is the validator Rieseberg says ambition depends on, and it works because it can touch the environment. The Postgres delay is what a verifier this effective does to a release schedule.