3 items

All three stories are about the same structural problem: verification is failing faster than the tools that were supposed to provide it. OpenAI declaring networking a non-moat, AI text saturating peer review, and vibe-coded apps leaking PHI at scale are each a version of the same dynamic — the layer that was supposed to enforce quality or security has been dissolved by the same technology it was meant to govern. The question of where trust gets rebuilt, and who captures value doing it, runs through all three.

The Deep View 2026-05-07-1

OpenAI MRC Protocol: What Gets Open-Sourced Is the Non-Moat

What frontier labs open-source is a map of the non-moats. OpenAI released its GPU networking protocol through OCP with Microsoft, AMD, Broadcom, NVIDIA, and Intel as coalition partners, two years in development, already running at Stargate's Abilene site and used to train GPT-5.5. The corollary lands hardest for Microsoft: they have the protocol, run it on Fairwater, and still ship mid-class models, which means networking efficiency was never the binding constraint.

Nature 2026-05-07-2

How much of the scientific literature is generated by AI?

Three independent studies converge on the same finding: 30% of peer reviews at Organization Science, 1 in 8 top-tier biomedical papers, and 43% of arXiv CS review preprints now contain AI-generated text. The verifier and the verified are using the same tool. This is the fourth domain in 30 days where verification has emerged as the binding constraint on AI-era knowledge work, after enterprise dev, frontier math, and frontier physics. The investable thesis is no longer single-domain. The next moat in scientific publishing is detection-vendor integration; pre-2026 literature becomes a scarcity asset; mid-tier journals collapse.

WIRED 2026-05-07-3

5,000 Vibe-Coded Apps Are Leaking on the Open Web — and the S3 Analogy Misses the Legal Novelty

RedAccess found 5,000-plus exposed apps on the four leading vibe-coding platforms with around 2,000 leaking real PHI, customer chat logs, and strategy decks. The S3 analogy is reaching for the right pattern but missing the legal twist: AWS could credibly say it didn't write your bucket policy. Lovable, Replit, and Base44 wrote the auth logic that doesn't exist. The first court that holds a code-generation platform partially liable for a generated vulnerability resets the entire industry's product roadmap overnight.