There are not many items today, but the signal is strong: AI coding and agents are moving from personal productivity into organizational production lines. Claude Code team management, Cloudflare temporary deployment accounts, Samsung’s global rollout, and the mundane problem of sharing Claude Code context all point to the same shift: AI competition is no longer just about model capability; it is about owning real engineering workflows.

Today’s thread is clear: AI does not lack model news; it lacks the discipline needed for production systems. MCP auth boundaries, OpenAI’s narrow medical use case, Claude Code artifacts, open-model specialization, and Anthropic’s safety policy all point to the same shift: AI products are moving from chat interfaces into workflows, risk controls, and long-term retention.

Today’s AI news has a clear theme: the industry is moving from capability theater to controlled delivery. OpenAI is putting $150 million behind an enterprise partner network. Anthropic is pulling Mythos and Fable after U.S. regulatory pressure. Braintrust is treating evals and CI as the operating system for agentic software. Meanwhile, the engineering side is getting serious about inference systems, permissions, and capability minimization. OpenAI’s Partner Network says enterprise AI is not a solo sport Source: OpenAI News

This digest covers news from March 22 to March 24. OpenAI Discloses Sora Safety Design Details Source: https://openai.com/index/creating-with-sora-safely OpenAI published safety design documentation for Sora 2 and the Sora app, centered on “safety built in from the start.” Every video carries both visible and invisible provenance signals, embeds C2PA metadata, and OpenAI maintains internal reverse-image and audio search tools to trace videos back to Sora. For human likenesses, OpenAI introduced a “characters” mechanism: users can create digital versions of themselves, control who can use these characters, and revoke access at any time. Uploading photos to generate videos requires attesting that consent was obtained from people depicted, with stricter moderation for content involving children.

This edition covers news from March 22 to March 23. Mozilla sketches a Stack Overflow built for agents Source: https://blog.mozilla.ai/cq-stack-overflow-for-agents/ Mozilla AI makes a blunt but useful observation: today’s agents keep running into the same problems that human developers used to solve by searching old forum threads and Q&A archives. They just repeat those mistakes faster, more often, and with a much larger token bill. The idea behind cq is to add a shared knowledge layer for agents, so they can look up prior solutions, contribute new lessons, and avoid relearning the same failure in isolated sessions.

This edition covers news from March 21 to March 23. The Rust community starts debating where AI should fit Source: https://nikomatsakis.github.io/rust-project-perspectives-on-ai/feb27-summary.html The Rust project has finally started discussing AI in public, in a way that feels serious rather than performative. Niko Matsakis published a long summary of community comments and made it explicit that this is not an official Rust position. It is a map of the arguments: people who find real value in AI tools, people who remain skeptical, and quite a few who sit awkwardly in the middle.

Give different LLMs the same persona file, and they’ll behave like completely different people. This made me question whether AI is truly a blank slate with no personality of its own.

We assume that remembering more leads to better decisions. But for both humans and AI, recording everything without distinction is not diligence — it’s deferring the work of filtering to your future self.

Last year I was still religiously following the “functions under 20 lines” rule. This year I had AI write a 300-line data processing function. It worked fine. I stared at the screen for a while thinking—who was this rule even for? For humans. Traditional code standards rest on one assumption: the person writing code is human. Humans make mistakes. Humans have limited working memory. Humans will name variables tmp2_final_v3 at 3 AM. So we invented a whole system of rules to constrain ourselves.

As AI drives the cost of execution toward zero, the scarce human advantage is no longer speed itself, but the ability to judge what is worth doing, what still requires direct involvement, and which consequences must be owned by people.