Thread
verification-infrastructure
8 reads · chronological order
ArXiv to Ban Researchers for a Year if They Submit AI Slop
ArXiv's one-year ban targets only 'incontrovertible' cases, meaning LLM meta-comments left in manuscripts and hallucinated references, which leaves sophisticated AI use untouched by design. The Columbia biomedical data behind the policy shows fabricated citations running from 1 in 2,828 papers in 2023 to 1 in 277 in early 2026, and the policy's narrow scope isn't a bug: detection scales with submissions times sophistication, deterrence scales flat, and when the first exceeds budget you switch to the second. bioRxiv, SSRN, and PubMed Central are next, and arXiv's nonprofit transition in July is explicitly fundraising for the verification cost center that every major research repository will have to build.
AI Is Causing a Crisis of Agency
Every essay mourning AI's death of human consultation is describing the product the labs refuse to build. Trust, not truth, is the scarce asset: provenance and positive human-attribution become priced layers once the Granta prize scandal supplies the consumer-grade catalyst. Detection stays a losing arms race; attestation that a human was load-bearing is the durable, unbuilt trade the AI companies keep leaving on the table.
The Death of the Code Review: What the Data Actually Says — Laurie Voss, Arize AI
Review isn't disappearing; the unit of human review is moving from the diff to the definition of good. Every no-human showcase, from OpenAI's roughly 1M lines and 1,500 merged PRs with three engineers to Bun's 6-day Rust port, had humans authoring the verifier, and the Bun port still carries 13,044 unsafe blocks against about 74 in comparable human code. Whoever codifies mergeability into rubrics and evals sets what agents treat as done.
I Believe Everything My Agents Tell Me: Three Levels of Review — Corey Gallon, Rexmore
Gallon's agent produced a letter whose numbers were right to the cent and whose premise was wrong, which is exactly the failure reconciliation can't see. Only the role-based cold reviewers attacked the frame; the invoice check would have passed it. In about 4 in 10 analysed 2026 sessions an agent got something wrong that mattered, so self-reported completion plus a spot-check is no longer a defensible default, and verification effort will have to scale with stakes.
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.
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.
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.
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.