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

Rowspace's CLO builds, the physics-agent wish list and grant paperwork sit at three points on the same line: a written source of truth, a mechanical checker, and nothing at all. The first two get faster, the third gets noisier, and the line is drawn by who built the checking layer, not by which model is underneath.

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.

3 reads

Amazon's vans, Waymo's Philippine call centers and a 2014 architecture without residual connections are all the unglamorous layer where the outcome gets settled. Whoever owns or can read that layer wins; the demo on top is mostly a distraction.

Barron's Streetwise 2026-10-18-1

Barron's Streetwise — The Disruption Scorecard

Disruption lands where the challenger already owns a cost or distribution asset, and Amazon is the proof: it is now the top US parcel carrier, and FedEx stock beat UPS by 110 points over five years after FedEx walked away in 2019 while UPS loaded up on Amazon's cheap e-commerce volume. The loudest threat, SpaceX against telecom, is the smallest: a real Verizon/AT&T rival would cost about $250B. Capital One moving its own volume onto Discover rails is the same template, available to any holder of captive volume.

The New Yorker 2026-10-18-2

Robot, Take the Wheel

Waymo runs 4,000+ cars in 15 US cities on a $126 billion valuation, but about 70 remote agents on duty at any time, split between US and Philippine call centers, are the layer the marketing leaves out. The riders cannot steer, so safety depends on how fast a human answers, and the least disclosed metric is that response time. Like Amazon's logistics, the moat is operational, and here it also includes winning permission city by city.

Goodfire 2026-10-18-3

Neural Networks Are Already Clean

Goodfire argues that superposition was the wrong explanation for interpretability's canonical messy neurons: redoing OpenAI's neuron project, about 70% of neurons look like roughly one thing, against under 2% originally. The 2014 InceptionV1 lacked residual connections and LayerNorm, so some of the mess was architecture and tooling. That makes the Waymo escalation layer the opposite case: a human layer you can see and staff, where the network inside may be more readable than assumed.

3 reads

Rieseberg's last prompt question asks what other than you or the model shows the work is right, VAGEN answers it with a verifier that can read state, and Postgres shows the bill that arrives next. Finding defects got cheap; triaging, reviewing and backpatching them did not.

felixrieseberg.com 2026-10-17-1

How to be more ambitious: A tutorial for humans with models

Rieseberg's tutorial reads as ambition advice, but every example that worked rested on a verifier. The crash-free app workflow needed crash-report access, version-to-commit mapping, and Windows, macOS and Linux machines to reproduce bugs, and his fourth prompt question asks what other than you or the model shows the result is right. He dates the outside-judge rule to October 2026, which makes it a workaround with an expiry, and the VAGEN paper is one attempt to build the real thing.

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.

The Register 2026-10-17-3

Postgres 19 delayed after AI reviewers find more bugs than humans can fix

Postgres 19 GA slipped from late September or early October to about November 19, 2026, and 8 to 10 features went back to PG20, because LLM-assisted review found more than the beta window could absorb. Eisentraut's example is about 40 reports averaging a three-line fix, each still carrying triage, patch, review, commit and backpatch overhead. PG20 was expected to be bug-fix-only and now inherits the leftovers, so a verifier like VAGEN pays off only if remediation capacity grows to match.