posts · 2026-05-14

Three outlets covered arXiv’s new rule with the same core frame: a one-year ban tied to hallucinated references or obvious AI residue. That alignment points to one central policy source, not independent digging. The disclosed hook is concrete: one year off the repository; The Verge’s visible body also mentions leftover prompts or “incontrovertible evidence,” but the full enforcement workflow is not shown here. I like this policy more than generic campus ChatGPT bans. arXiv is not trying to measure whether Claude, GPT-5, or a local model touched the draft. It is punishing checkable failure modes: fake citations, prompt scraps, and papers where the author skipped basic cleanup. For AI-assisted research writing, that is the right pressure point: use models if you want, but own the bibliography.

Two arXiv categories carry the same FutureSim paper with identical framing; this is paper distribution, not independent corroboration. The benchmark replays real news and question resolutions from January to March 2026, then asks agents to forecast post-cutoff events. The best agent reaches only 25% accuracy, and many score worse on Brier skill than making no prediction. I like how unforgiving this setup is. It tests belief updating inside an information stream, not trivia retrieval with a nicer harness. A lot of agent demos look competent because tool calls and long context hide weak calibration. Chronological replay exposes that quickly: memory, search policy, and uncertainty reasoning all have to work together. The abstract does not name the tested models, so cross-model claims stop there. Still, this is a healthier direction than another static QA leaderboard.

Two arXiv categories list the same position paper, with identical framing from the authors’ abstract rather than independent reporting. The paper hits the weakest seam in AI safety governance: 21 instruments from 2019 to early 2026 ask for evidence on hidden objectives, loss-of-control precursors, and bounded catastrophic capability, while the evidence base is mostly behavioral evals and red-teaming. I buy the critique. SWE-bench or MMLU-style behavior scores can rank product capability; they cannot verify the absence of long-horizon agentic failure modes. Linear probes, activation patching, and before/after-training comparisons are not magic either. But they at least force legal language to stop treating “passed the eval suite” as auditable safety proof.

Two outlets center the same Cerebras IPO upsizing: Bloomberg frames the $4.8 billion raise, while IT Home adds 20x oversubscription, 30 million shares, and a $150–$160 range. The alignment smells like one capital-markets leak spreading through different desks. I don’t read this as wafer-scale AI chips being commercially proven. It looks like the GPU scarcity premium spilling into public-market pricing. The concrete tell is the midpoint moving from $120 to $155, a 29.17% lift, while the article only says Amazon and OpenAI placed large orders. It gives no gross margin, delivery cadence, or cluster utilization. Cerebras has a real decoding-side argument, but the IPO demand is paying first for Nvidia-adjacent scarcity, not proven substitution.

Four sources covered the same launch with aligned framing: Codex is entering preview inside ChatGPT on iOS and Android, and OpenAI claims more than 4 million weekly Codex users. The coverage reads like official-product-note amplification, not independent discovery. I don’t buy the “coding from your phone” gloss. The useful move is narrower: OpenAI is turning mobile into an approval, steering, and review surface for long-running coding agents. Files, credentials, and permissions stay on the local or remote machine; the phone sees live state through a secure relay, including diffs, test results, terminal output, screenshots, and approvals. Remote SSH and Hooks are now generally available; programmatic tokens are limited to Enterprise and Business. That is aimed at workplace code flows, not hobbyist convenience. Compared with Copilot-style chat in an editor, Codex is trying to own the human checkpoint layer while the actual work runs elsewhere.