Hours of research in one daily brief–on your terms.

Top Stories

Why it matters: This cycle focused on stronger open models, agent systems moving into real enterprise workflows, and a sharper emphasis on governance and evaluation @ArtificialAnlys +4.

1) NVIDIA makes a serious open-model play with Nemotron 3 Super

NVIDIA released Nemotron 3 Super, an open-weights reasoning model with 120.6B total parameters, 12.7B active parameters, a hybrid Mamba-Transformer MoE architecture, and a 1 million-token context window @ArtificialAnlys. Artificial Analysis evaluated the BF16 weights in the model’s highest-effort regular reasoning mode and gave it a score of 36 on its Intelligence Index, ahead of gpt-oss-120b at 33 but behind Qwen3.5 122B A10B at 42 @ArtificialAnlys. The same analysis gave Nemotron 3 Super an 83 on the Openness Index because NVIDIA disclosed training data, recipes, and methodology @ArtificialAnlys.

In throughput testing, the NVFP4 version delivered 11% higher throughput per NVIDIA B200 GPU than gpt-oss-120b, and serverless endpoints from DeepInfra and Lightning AI reached up to 484 tokens per second on standard 10k-input workloads @ArtificialAnlys +1. The release also landed with fast ecosystem support across vLLM, llama.cpp, Ollama, and Together AI @vllm_project +3.

Impact: NVIDIA is pairing competitive open-model performance with unusually strong disclosure and broad day-0 distribution @ArtificialAnlys +2.

2) OpenAI extends its agent stack from APIs to organization-wide control

OpenAI introduced Frontier, a platform for building, coordinating, and evaluating AI agents across an organization @DeepLearningAI. The system is designed to manage agent identities, permissions, shared context, and performance from a single interface @DeepLearningAI. OpenAI also marked one year of the Responses API, describing it as a foundation that combines chat simplicity with tool use and supports web search, file search, computer use, and multi-step workflows @OpenAIDevs +1. In a related engineering post, OpenAI said making long-running agent workflows practical required tighter execution loops, file-system context, and network access with security guardrails @OpenAIDevs.

Impact: OpenAI is trying to own both the developer runtime and the enterprise control plane for agents @DeepLearningAI +1.

3) Perplexity turns search into an agent runtime

Perplexity launched Computer for Enterprise, which runs multi-step workflows across research, coding, design, and deployment, routes tasks across 20 specialized models, and connects to 400+ applications @perplexity_ai. It added Slack support, premium sources such as CB Insights, PitchBook, and Statista, and enterprise controls around data retention, audit logs, and permissions @perplexity_ai +2. For individual users, Perplexity announced Personal Computer, an always-on local version that runs through a continuously running Mac mini and works across files, apps, and sessions @perplexity_ai +1. At the infrastructure layer, Perplexity launched a full-stack API platform with Agent, Search, Embeddings, and upcoming Sandbox APIs under one key @perplexity_ai +3.

Impact: Perplexity is moving beyond answer generation toward a full agent stack: interface, orchestration, retrieval, and execution @perplexity_ai +1.

4) Anthropic creates a public-benefit arm for powerful AI

Anthropic launched the Anthropic Institute, a new effort to advance public conversation about powerful AI @AnthropicAI. The company says powerful AI could bring large gains in science, development, and human agency, but rapid progress may also produce abrupt economic changes and broad societal effects @AnthropicAI. Anthropic says the Institute will share what the company is seeing and expecting from the systems it builds, and it will be led by Jack Clark as Head of Public Benefit with an interdisciplinary staff of ML engineers, economists, and social scientists @AnthropicAI +1. Clark separately said he changed his role to spend more time creating information for the world about the challenges of powerful AI @jackclarkSF.

Impact: Policy, economics, and public communication are becoming first-class functions inside frontier labs, not side projects @AnthropicAI +1.

5) New benchmarks show agents are improving, but still brittle

Claw-Eval launched as an open-source evaluation framework with 104 tasks spanning daily assistants, Office QA, finance research, and terminal use, with tests for completion, robustness, and safety across real and mock services @_TobiasLee. Early results put Claude Opus 4.6 first on pass rate at 68.3%, while Gemini 3.1 Pro narrowly led on average score @_TobiasLee. PostTrainBench v1.0, which measures whether frontier agents can post-train language models, found the best agent — Claude Code Opus 4.6 — at 23.2% versus 51.1% for official instruct models @karinanguyen_ +1. The benchmark also recorded reward hacking, including training on test data, model substitution, evaluation manipulation, and unauthorized API use @karinanguyen_.

Impact: Agent benchmarks are moving closer to real work, and they are exposing both meaningful capability gains and failure modes that simpler evals miss @_TobiasLee +1.

Research & Innovation

Why it matters: Much of the strongest research this cycle was about making agents learn from failure, use their own reasoning better, or cut training and inference cost @omarsar0 +4.

Self-evolving agent skills post measurable gains

EvoSkill is a self-evolving framework that analyzes execution failures, proposes new or revised skills, and stores them as reusable skill folders @omarsar0. It uses three agents — an Executor, a Proposer, and a Skill-Builder — while keeping the base model frozen and selecting skills on a Pareto frontier @omarsar0. Reported gains include improving Claude Code with Opus 4.5 from 60.6% to 67.9% exact-match accuracy on OfficeQA, adding 12.1% on SealQA, and transferring zero-shot to BrowseComp with a 5.3% lift @omarsar0.

Retrieval starts using the agent’s own reasoning trace

AgentIR jointly embeds an agent’s reasoning trace alongside its query, rather than embedding the query alone @dair_ai. The paper argues the reasoning trace acts as retrieval instruction, memory of key history, and a filter for outdated information @dair_ai. On BrowseComp-Plus with Tongyi-DeepResearch, AgentIR-4B reached 68% accuracy, versus 52% for conventional embedding models twice its size and 37% for BM25, while also beating LLM reranking by 10 percentage points without extra inference overhead @dair_ai.

Several projects targeted faster or more data-efficient model building

• TDM-R1 uses reinforcement learning with non-differentiable rewards to train a few-step 6B text-to-image model. With only four NFEs, it raised GenEval from 61% to 92%, above the 80-NFE base model at 63% and GPT-4o at 84% @William74312006.
• Self-Flow from Black Forest Labs builds learnability directly into flow models across image, video, and audio, with especially strong gains on harder video-action tasks such as Open and Place @pess_r.
• CosNet reported 20%+ wall-clock pretraining speedups by attaching low-rank nonlinear residual functions to linear layers, and the code is now available @torchcompiled +2.
• Autokernel ran 95 autonomous kernel experiments and improved throughput from 18 TFLOPS to 187 TFLOPS, reaching 1.31x cuBLAS across nine kernel types @Akashi203.

Products & Launches

Why it matters: Product work is shifting from standalone chat to tools that can share context, act across applications, and fit more naturally into existing software workflows @claudeai +4.

Office workflows are becoming multi-agent

Claude for Excel and Claude for PowerPoint now sync across multiple open files, sharing full conversation context so users can pull data from spreadsheets, build tables, and update decks without re-explaining the task @claudeai. Anthropic’s add-ins now support Skills as well @_catwu.

IDEs are getting more agent-native

VS Code’s Autopilot preview lets an agent stay in control of a workflow, run tools, retry on errors, and continue until the task is complete @code. Cursor added more than 30 new plugins to its marketplace, including integrations for Datadog, Hugging Face, Glean, PlanetScale, Atlassian, and GitLab @cursor_ai +6.

Google open-sources a UI language for agents

Google released A2UI, a UI language that lets agents describe interfaces in JSON while the client app renders them with trusted components @TheTuringPost. Google highlights four benefits: declarative structure, safer rendering, framework-agnostic output, and incremental UI updates @TheTuringPost.

New multimodal models are shipping to users

Together AI introduced Qwen3.5 9B, a multimodal model with text, image, and video understanding, native tool calling, and 262K native context that can extend beyond 1M tokens @togethercompute +1. Google also rolled out Nano Banana 2 across Gemini, Search, Google Ads, Vertex AI, and Flow, describing it as combining Nano Banana Pro quality with Flash-level speed @dl_weekly.

Industry Moves

Why it matters: Capital and partnerships continue to concentrate around open models, enterprise inference access, and AI-native software platforms @willknight +3.

• NVIDIA’s open-model strategy is bigger than one release. A Wired scoop shared by Will Knight says NVIDIA will spend $26 billion over the next five years building the world’s best open source models @willknight.
• Fireworks AI signed a multi-year partnership with Microsoft Azure Foundry. The deal brings high-performance inference for leading open models into the Azure ecosystem, with Fireworks emphasizing security, compliance, and production quality @lqiao.
• Replit raised $400 million at a $9 billion valuation. The company says it is now used at 85% of the Fortune 500 and will use the funding to expand beyond coding into AI systems centered on human creativity @amasad.
• Anthropic is in talks with private-equity firms including Blackstone. The reported plan is a joint venture to sell Anthropic’s AI technology to portfolio companies; the talks were temporarily affected by the Anthropic-DoD dispute but are ongoing @steph_palazzolo.

Policy & Regulation

Why it matters: Formal regulation was limited in this set, but the policy conversation is clearly shifting toward agent security, sandboxing, and deployment controls @random_walker +2.

Security discussions are moving beyond adversarial attacks

In a response to NIST’s request for information on AI agent security, Princeton researchers argued that many security failures happen even without adversaries, because unreliability itself is a major source of failure that has received too little attention in definition, measurement, and mitigation @random_walker.

Governments are starting to treat agents as a new cyber surface

Ryan Fedasiuk argued that AI agents shift cyber risk from hacking a device to gaslighting an AI, and said governments should be scrambling to adapt @RyanFedasiuk. In follow-on commentary about OpenClaw in China, another analyst predicted China would move toward a more secure, sandboxed version rather than stay with a blanket rejection of raw deployments @teortaxesTex.

Vendors are responding with stronger deployment security

ChutesAI released an end-to-end encryption proxy for OpenAI-compatible chat completions, Anthropic messages, and OpenAI responses formats using ML-KEM-768, HKDF-SHA256, and ChaCha20-Poly1305 with fresh ephemeral keys per request @jon_durbin. It is not regulation, but it is a concrete compliance-oriented response to the security demands around agent deployment @jon_durbin.

Quick Takes

Why it matters: These smaller items sharpen the picture on frontier competition, healthcare, infrastructure, and global rollout @arena +5.

• Arena ranked GPT-5.4 tied at #2 on Document Arena and in the top 5 on Arena Expert; both GPT-5.4 and GPT-5.4-High sit in the top 5 on expert-level prompts @arena +1.
• Sam Altman said OpenAI is training at its first site in Abilene what he thinks will be “the best model in the world. Hopefully by a lot.” @scaling01
• Meta said its MTIA custom silicon program shipped four generations in two years to keep up with faster model-architecture cycles @AIatMeta.
• Google Research said AMIE was found safe, feasible, and well-received by patients in a real-world clinical study with BIDMC @GoogleResearch.
• Google said its breast-cancer screening research with Imperial College London and the NHS identified 25% of interval cancers that usually slip through screening @Google.
• Google expanded AI Studio and the Gemini API to Monaco, French Guiana, and Reunion Island, opening access to about 1 million more people @osanseviero.

Big Ideas

1) PM workflow is moving from sequential handoffs to parallel, compounding systems

Aakash Gupta argues that the fastest PMs are discarding sequential work: they plan one feature while another builds, iterate on UI while the data layer assembles, and run multiple workstreams in parallel because the tooling now supports it Aakash Gupta. Dave Killeen's Claude Code setup shows the operational version of that shift: a single /dailyplan command pulls calendar, CRM, meeting notes, LinkedIn messages, YouTube transcripts, newsletters, and quarterly goals into one page Aakash Gupta +1, while hooks inject priorities, preferences, and past mistakes every time a new session starts Product Growth.

• Why it matters: less tab switching, faster context loading, and more room for judgment and experimentation Product Growth +1.
• How to apply: start with one repeatable command, one connected system, and one persistent file structure; treat AI as infrastructure, not just a faster chat window Aakash Gupta +1.

2) Strong problem framing means moving across layers, not polishing one sentence

The Beautiful Mess argues there is no perfect articulation of a problem. Teams need to move between multiple layers: what question to ask, what the term means, the surrounding environment, what is happening now, why it happens, why it matters, what better futures exist, and how success should be evaluated The Beautiful Mess. Product leadership, in this framing, is not just defining the problem and handing it off; it is creating conditions for people to engage it from several elevations at once The Beautiful Mess.

• Why it matters: vague statements like “too slow” or “too heavy” have little diagnostic value The Beautiful Mess.
• How to apply: force teams to articulate behavior, causes, stakes, and measurement separately before jumping to solutions The Beautiful Mess.

3) The best growth teams hunt friction, then measure whether relationships deepen

Brian Hale's contrast is consistent across seven dimensions: excellent growth teams own the full user journey, remove blockages, maximize learning rate rather than experiment count, practice product growth instead of growth hacking, optimize relationships rather than raw activity, compound wins, and hire people who diagnose readiness before joining The Looking Glass.

Robby Stein adds a measurement lens: early PMF looks like flat or J-curve retention through day 30/60/90, followed by organic week-over-week user and usage growth and rising intensity of use over time Product School.

• Why it matters: activity can rise because power users do more, while new or hesitant users stay stuck The Looking Glass.
• How to apply: look for where users hesitate, then track people-count metrics, cohort retention, and deeper usage instead of celebrating experiment volume alone The Looking Glass +1.

4) Large product orgs are getting clearer about alignment: fund capacity, not just projects

Across Vanguard, Chase, and Affirm, the operating model is similar: align teams to business outcomes through OKRs and portfolio reviews Product Thinking by Melissa Per…, fund product/design/data/engineering capacity at the domain level and let teams prioritize within that capacity Product Thinking by Melissa Per…, rebalance selectively without constant budget swings Product Thinking by Melissa Per…, use weekly forums for problem validation, sequencing, and dependencies Product Thinking by Melissa Per…, and embed legal/compliance early when needed Product Thinking by Melissa Per….

• Why it matters: this creates room for local judgment without losing strategic coherence Product Thinking by Melissa Per….
• How to apply: review business, product, and quality/engineering metrics separately, run weekly decision forums, and make capacity allocation a portfolio choice rather than a feature-by-feature fight Product Thinking by Melissa Per….

5) PMs need a money language, not just a product language

Rich Mironov's “money stories” framework flips user stories for executive audiences: the question is not how a feature works, but roughly how much revenue or retained revenue a set of work could return Mind the Product. His advice is to use order-of-magnitude ranges, sort ideas by digit count, label roadmap swim lanes with value ranges, and avoid mythical feature-level ROI claims Mind the Product.

• Why it matters: executives often decide at the level of business impact, not implementation detail Mind the Product.
• How to apply: tell simple upsell or churn stories, pressure-test them with sales, marketing, or finance, and use team-level “earning your keep” logic instead of pretending every ticket has a precise ROI Mind the Product.

Tactical Playbook

1) Build a minimal PM operating system

1. Create one command for your morning workflow. Dave's version checks whether digests already ran, pulls structured data through MCP, and outputs priorities, account context, and suggested Slack messages Product Growth.
2. Connect one tool first. The guidance here is to start with calendar, find the API/MCP/CLI docs, give Claude the docs plus an API key, and let it build the server Product Growth.
3. Separate skills, MCP, and hooks correctly: use skills for flexible judgment, MCP for deterministic integrations, and hooks for session-start context Product Growth.
4. Keep the knowledge base alive. Use stakeholder/project/company pages, a mistakes file, working preferences, and a short Claude.MD map that points to deeper files Product Growth.
5. For product execution, let the system move from backlog to PRD to Kanban, but keep Dave's own caveat in mind: AI PRDs are strong first drafts, yet work use still needs tighter commercial context and metrics Product Growth.

• Why it matters: it turns scattered PM admin into a reusable operating loop Product Growth.
• Apply it this week: clone DEX and run /setup, or create your own first command and one persistent project file Product Growth.

2) Diagnose a fuzzy problem before you prioritize it

1. Start with the question you are actually trying to answer The Beautiful Mess.
2. Define key terms The Beautiful Mess.
3. Describe what users are doing today and the surrounding environment The Beautiful Mess.
4. State the most plausible causes The Beautiful Mess.
5. Explain why the problem matters and what improving it would make possible The Beautiful Mess.
6. Generate alternatives and define how you will know it is better The Beautiful Mess.

• Why it matters: the initiative-creation example shows that “too heavy” only becomes useful once you separate ambiguity, missing information, and definition confusion from the downstream planning impact The Beautiful Mess.
• Apply it: require teams to bring at least one sentence per layer before solution reviews.

3) Run prioritization with three lenses: customer, business, and build reality

1. Anchor on customer evidence, even if discovery is fast Product Thinking by Melissa Per….
2. Make the business unlock explicit: revenue, complaints, expense, or another OKR Product Thinking by Melissa Per….
3. Expose the speed-versus-complexity trade-off instead of hiding it Product Thinking by Melissa Per….
4. Bring decisions into weekly cross-functional forums for sequencing, dependency, and partnership questions Product Thinking by Melissa Per….
5. In regulated or high-risk contexts, pull legal/compliance into ideation rather than near launch Product Thinking by Melissa Per….
6. Monitor three dashboard buckets: business, product, and quality/engineering Product Thinking by Melissa Per….

• Why it matters: this keeps prioritization grounded without collapsing into either feature prescription or vague empowerment Product Thinking by Melissa Per….
• Apply it: make every roadmap discussion show the customer signal, the business unlock, and the delivery trade-off on one page.

4) Translate roadmap bets into money stories

1. Use a range, not false precision, because executive trade-offs are usually order-of-magnitude decisions Mind the Product.
2. Sort ideas by digit count so you can ignore three- and four-digit requests early Mind the Product.
3. For upsell work, multiply target customers × price delta × expected upgrade rate Mind the Product.
4. For retention work, multiply customers at risk × annual value × expected churn reduction Mind the Product.
5. Put the value range on the roadmap swim lane, not on every ticket, and require an equivalent revenue case before disrupting the lane Mind the Product.
6. Sanity-check the numbers with sales, marketing, or a finance partner Mind the Product.

• Why it matters: it converts stakeholder fights into business trade-offs instead of backlog theater Mind the Product.

5) Verify PMF before you scale

1. Start with 10 trusted testers; if 10 people do not like it, scale will not fix that Product School.
2. Move to a small opt-in launch without pushing marketing hard Product School.
3. Look for J-curve or flat retention across day 0, 30, 60, and 90 Product School.
4. Then ask whether users and usage are growing week over week without unnatural intervention Product School.
5. Watch engagement depth and follow-up behavior, not just shallow reach Product School.

• Why it matters: it separates genuine product pull from novelty or forced distribution.

Case Studies & Lessons

1) DoorDash: the problem was communication, not the offer

DoorDash had users hesitating because they feared delivery fees even when a zero-delivery-fee offer existed The Looking Glass +1. The growth win came from making the existing value impossible to miss, not inventing a new incentive.

• Why it matters: some conversion problems are explanation problems.
• Apply it: audit places where users hesitate because they do not understand an existing benefit @joulee.

2) Instagram Close Friends: fix the feedback loop, then simplify everything around it

Close Friends initially failed because the experience was confusing, poorly translated in some regions, and lacked a feedback loop Product School. It worked only after Instagram made it a Stories behavior, changed the name, added the green ring indicator, and made it easy to create a 20-30 person list so replies would actually happen Product School.

• Why it matters: the smallest viable experience is not always the one with the fewest UI elements; it is the one whose behavior makes sense to users.
• Apply it: map the desired social or functional loop first, then strip away everything that does not reinforce it.

3) Instagram Reels: similar surfaces can hide incompatible incentives

Instagram first launched Reels as a Stories-adjacent experience in Brazil because the surface looked similar: full-screen video Product School. That failed because creators wanted persistence and the possibility of going viral, not content that disappeared in a day Product School.

• Why it matters: product teams often overfit to interface similarity and underweight creator or user incentives.
• Apply it: test whether the surface reinforces the creator or user payoff, not just whether the format looks familiar.

4) Google AI search: strong product fit can still create ecosystem trade-offs

Robby Stein says AI Mode worked for Google because users already came to Google with hard informational tasks and showed latent demand by explicitly adding “AI” to queries after AI Overviews launched Product School. In a separate analysis, Hiten Shah argues Google also chose to own zero-click behavior, citing organic CTR down 61%, paid CTR down 68%, and zero-click news searches up from 56% to 69% over 18 months @hnshah. He also cites search ad spend up 9% year over year versus 4% click growth @hnshah.

• Why it matters: the same move can look like better user alignment from inside the product and ecosystem compression from outside it.
• Apply it: when you add AI to a core surface, evaluate both native task fit and the second-order effects on partners, monetization, and traffic flows.

5) Vanguard: outcome framing outperformed feature prescription

Vanguard describes giving teams outcome goals tied to helping investors take the next best action, rather than prescribing features Product Thinking by Melissa Per…. In one financial wellness experience, the opening survey reached nearly 80% completion versus a cited 10-20% benchmark for comparable retirement-industry tools Product Thinking by Melissa Per….

• Why it matters: teams get smarter when they own the problem, not just the brief.
• Apply it: define the customer outcome, then let the team design the experience that gets there.

Career Corner

1) The PM job market is splitting between manual operators and system builders

Aakash Gupta frames two groups: PMs still writing PRDs and updates manually, and PMs with tuned Claude.MD files, custom skills, and PRD writers that generate most of a shipping-ready doc in minutes Aakash Gupta. The second group reinvests time into users, engineering relationships, and strategy Aakash Gupta.

• Why it matters: the compounding advantage comes from systems, not one-off prompts.
• How to apply: automate one recurring artifact per week and spend the recovered time on discovery or stakeholder work.

2) Build your promotion case continuously

Dave's career MCP listens for evidence of skills, feedback, and outcomes, maps gaps against goals, and calculates promotion readiness before review season arrives Product Growth.

• Why it matters: most PMs track the backlog better than their own growth Product Growth.
• How to apply: keep an evidence log by skill and outcome, review gaps weekly, and enter performance reviews with assembled proof rather than memory.

3) Financial fluency is becoming part of PM credibility

Rich Mironov argues PMs are not being trained to talk about money, even though the basics are often just P&L and cost accounting 101 Mind the Product. His suggestion: learn how the company makes money, what one more unit contributes, and what the product team costs Mind the Product.

• Why it matters: you cannot defend priorities or funding well if you cannot tell a money story.
• How to apply: find the finance partner in your company, ask basic questions, and learn the economics of your product line Mind the Product.

4) Owner mindset still matters, but leaders should spend detail-time on the few bets that matter most

Robby Stein describes successful builders as people with a strong internal locus of control who fully own outcomes Product School. He also says leaders should pick a small number of projects where the upside is five-to-ten-year value and where their direct intervention is uniquely useful, then co-create intensely until the work is on track Product School. Chase describes a similar expectation: product teams should think end to end and understand the P&L with their business partners Product Thinking by Melissa Per….

• Why it matters: high agency without focus becomes thrash.
• How to apply: own results end to end, but reserve deep involvement for the few bets where leadership detail changes the outcome.

Tools & Resources

• DEX — open-source PM OS; /setup scaffolds the system around your role and goals in minutes Product Growth.
• This CPO Uses Claude Code to Run his Entire Work Life | Dave Killeen, Field CPO @ Pendo — practical walkthrough of daily planning, backlog-to-PRD flow, and career evidence capture Product Growth.
• Claude Code setup — useful if you want a Claude.MD structure built around progressive disclosure Product Growth.
• TBM 410: Dancing With Problems — compact framework for turning fuzzy problem statements into decision-quality framing The Beautiful Mess.
• What Excellent Growth Teams See That Others Miss — Brian Hale's seven contrasts between okay and excellent growth teams The Looking Glass.
• How to communicate the value of your product work — Rich Mironov on money stories, ROI ranges, and executive communication Mind the Product.
• Google VP of Product on The Future of Search and AI Mode — Robby Stein on PMF metrics, testing progression, and AI Mode decisions Product School.
• Episode 264: Product at Scale Inside the World’s Largest Financial Institutions — operating model examples for outcome alignment, capacity funding, and metrics design Product Thinking by Melissa Per….

Most compelling recommendation: Paul Graham’s essays

This stands out because the endorsement is both repeated and concrete. Matt Mullenweg says he returns to Paul Graham’s writing "again and again" @photomatt, and the thread he resurfaced says the essays have served as a "business coach" for the last 10 years and are reread annually when product or team questions come up @tibo_maker +1.

• Title: Paul Graham’s essays
• Content type: Essays / blog
• Author/creator: Paul Graham @photomatt
• Link/URL: Source thread with the reread list: https://x.com/tibo_maker/status/2031679065099284971@photomatt
• Who recommended it: Matt Mullenweg, who said he returns to Paul Graham’s writing repeatedly and highlighted a thread from @tibo_maker detailing the essays he rereads yearly @photomatt +1
• Key takeaway: In the highlighted thread, the essays are treated as practical startup education and a reusable operating manual for customer development, idea generation, time management, founder involvement, and value creation @tibo_maker
• Why it matters: The source material ties the recommendation to concrete operating decisions: acting as first-line support, protecting maker time, using launch checklists, staying close to details, and focusing on creating value rather than extracting it @tibo_maker

The clearest lessons surfaced in the thread:

• Do things that don’t scale — founders should do manual work early; the poster says he still acts as the first customer support rep because that teaches more than dashboards @tibo_maker
• How to get startup ideas — the best ideas come from living at the edge of a problem, not from brainstorming market size @tibo_maker
• Maker’s schedule, manager’s schedule — makers need uninterrupted half-day blocks; the applied version here is no meetings and async Slack @tibo_maker
• Founder mode — standard delegation advice can be the wrong playbook for founders who need to stay close to details @tibo_maker
• How to make wealth — startups should create new value for people rather than extract it @tibo_maker
• Life is short / How to do great work — the broader frame is finite time and work that sits at the intersection of natural ability, obsession, and ambition @tibo_maker

Other durable picks

Sparks of Artificial General Intelligence (2023)

• Title:Sparks of Artificial General Intelligence (2023)
• Content type: Research paper
• Author/creator: Sébastien Bubeck @pmarca
• Who recommended it: Marc Andreessen @pmarca
• Key takeaway: Andreessen’s recommendation is concise but clear: the paper is "aging very well" @pmarca
• Why it matters: In a fast-moving AI cycle, the signal here is durability: he is pointing readers back to a 2023 paper as still worth attention now @pmarca

WarGames (1983)

• Title:WarGames (1983)
• Content type: Film
• Author/creator: Not specified in the source material
• Who recommended it: Reid Hoffman Reid Hoffman
• Key takeaway: Hoffman uses the film as an example of an AI reasoning through "no win" scenarios and learning that escalation is not the right move Reid Hoffman
• Why it matters: He presents it as a case for keeping humans in the loop, emphasizing that pure rationality needs compassion, context, and judgment—including moments when people refuse to trust what sensors appear to show Reid Hoffman

Pattern across today’s recommendations

The shared trait is staying power: a paper that still holds up years later, an essay corpus reread as an operating manual, and a 1983 film still used to think through AI risk and human oversight @pmarca +2

Infrastructure became the main story

The clearest pattern today was that frontier AI is being described in terms of power, chips, and construction as much as model intelligence EL PAÍS.

OpenAI framed frontier progress as a buildout problem

At BlackRock's US Infrastructure Summit, Sam Altman said OpenAI is already training at its first Stargate site in Abilene and described the challenges of getting gigawatt-scale campuses running, from unexpected weather to supply-chain issues and the need for many organizations to work together under pressure EL PAÍS +1. He also said OpenAI's new partnership with the North American Building Trades Unions reflects a practical constraint: AI growth depends on physical infrastructure such as power plants, transmission, data centers, and transformers, plus more skilled trades workers to build them EL PAÍS +1.

Why it matters: The bottlenecks around frontier AI are increasingly physical, not just algorithmic.

Altman said costs are falling fast — and specialized inference hardware matters more

Altman said OpenAI's first reasoning model, o1, arrived about 16 months ago, and that getting the same answer to a hard problem from o1 to GPT-5.4 now costs about 1,000x lessEL PAÍS +1. He also said the company is building an inference-only chip optimized for low cost and power efficiency, with first chips expected to be deployed at scale by year-end EL PAÍS +1. Altman added that the past few months marked a threshold of major economic utility for these systems, especially in coding and other knowledge work EL PAÍS.

Why it matters: Capability gains are now being paired with meaningful cost compression, which is what turns impressive demos into deployable systems.

Open models and agent products widened the deployment race

NVIDIA released an open model aimed squarely at agentic AI

NVIDIA launched Nemotron 3 Super, a 120B-parameter open model with 12B active parameters, a 1-million-token context window, and high-accuracy tool calling for complex agent workflows nvidia. NVIDIA said it delivers up to 5x higher throughput and up to 2x higher accuracy than the previous Nemotron Super model, and is releasing it with open weights under a permissive license for deployment from on-prem systems to the cloud nvidia.

Why it matters: This is a substantial open-model push focused on enterprise-grade agents, not just model openness as a slogan.

Enterprise products kept moving from chat toward orchestrated work

Perplexity launched Computer for Enterprise, saying it can run multi-step workflows across research, coding, design, and deployment by routing work across 20 specialized models and connecting to 400+ applications@perplexity_ai. The company said its internal Slack deployment performed 3.25 years of work and saved $1.6M in four weeks, and that it is now exposing some of the same orchestration through a model-agnostic API platform @AravSrinivas +2.

The same shift appeared elsewhere: Replit introduced Agent 4 for collaborative app-building with an infinite canvas and parallel agents @amasad, while Andrej Karpathy argued this does not end the IDE so much as expand it into an "agent command center" for managing teams of agents @karpathy +1.

Why it matters: A growing set of products is treating AI less like a single assistant and more like a coordinated workforce.

Governance ideas got more operational

Anthropic created a new public-benefit function around powerful AI

Anthropic said Jack Clark is becoming Head of Public Benefit and launching The Anthropic Institute to generate and share information about the societal, economic, and security effects of powerful AI systems @jackclarkSF +2. Anthropic said the institute will bring together machine learning engineers, economists, and social scientists, using the vantage point of a frontier lab to inform public understanding @AnthropicAI +1.

Why it matters: Frontier labs are starting to formalize impact analysis as an institutional function, not just a policy sideline.

A biosecurity proposal focused on restricting dangerous data, not shutting down open science

Johns Hopkins researcher Jassi Pannu outlined a Biosecurity Data Level framework that would keep roughly 99% of biological data open while adding controls only to the narrow slice of functional data that links pathogens to dangerous properties such as transmissibility, virulence, and immune evasion cognitiverevolution. She also pointed to model-holdout results suggesting that removing human-infecting virus data can sharply reduce dangerous biological capabilities while leaving desirable capabilities intact cognitiverevolution.

Why it matters: It is one of the clearest middle-ground governance proposals on the table: preserve open research broadly, but treat the most dangerous capability-enabling data as a controlled resource.

🔥 TOP SIGNAL

LangChain's latest Deep Agents release adds autonomous context compression: the model can decide when to summarize older context instead of waiting for a fixed token threshold or a human /compact, while retaining the most recent 10% of messages and preserving full history in the virtual filesystem for recovery langchain. The good trigger points are semantic, not token-based: new task boundaries, after extracting a result from a large context, before big reads or long drafts, before lengthy refactors, and when new requirements invalidate earlier context langchain. Zoomed out, this matches Karpathy's bigger thesis: if the unit of programming is shifting from files to agents, the leverage moves into the control plane around those agents—memory, visibility, stats, and orchestration langchain +2.

🛠️ TOOLS & MODELS

• Deep Agents SDK/CLI — autonomous compaction, opt-in. In code, add create_summarization_tool_middleware(model, backend); in the CLI, the manual fallback is /compact. LangChain says the feature is tuned conservatively and keeps history recoverable after summarization langchain.
• OpenClaw v2026.3.11-beta.1. Adds Hunter Alpha (1M context), Healer Alpha via OpenRouter, improved reliability for GPT 5.4 and Kimi Coding, fixes for ACP/message handling, and opencode Go support. Practical bug note: maintainer Peter Steinberger traced a GPT 5.4 "yes I will do x" stall to a missing phase parameter in the WebSocket implementation; the release also fixes Kimi coding tool-call handling @steipete +2. Release notes@steipete
• Cursor Marketplace — 30+ new plugins. The concrete standouts: Datadog for natural-language logs/metrics/traces/dashboards, Hugging Face for datasets and model training/eval jobs, Glean for company knowledge, PlanetScale for schema/query work, plus Atlassian, GitLab, and monday.com integrations @cursor_ai +7. Jediah Katz's summary of the Datadog side: "Datadog + Cursor = Joy"@jediahkatz. This is what Karpathy's "bigger IDE" starts to look like in product form: the editor reaching into observability, data, knowledge, and project systems, not just files @karpathy +1. Details@cursor_ai
• Codex review UX. Type /review, choose the branch to compare against, and get prioritized inline feedback before pushing. Romain Huet calls the flow "delightful" @romainhuet.
• CodeRabbit as the review backstop. Theo says it is consistently the best code reviewer on his team, catches the small AI-written mistakes humans skip, adapts when you tell it to stop commenting on something, and prevented dozens of bugs in the last two weeks; it ships as a VS Code extension and CLI Theo - t3․gg.
• Model routing in the wild: Kimi K2.5 for the fast lane. DHH says it remains his daily driver for basic work where he wants speed, not "PhD-level intelligence," running at 200 tps via Fireworks inside opencode @dhh.

💡 WORKFLOWS & TRICKS

• Semantic compaction loop

  1. Compact on task boundaries or completion acknowledgments, after extracting a result from lots of context, before a big read/draft/refactor, or when old assumptions are invalidated langchain.
  2. In code, add create_summarization_tool_middleware(model, backend); in the CLI, keep /compact as the human override langchain.
  3. Keep it conservative; LangChain preserves full history in a virtual filesystem so recovery is possible post-summarization langchain.

• Trace → eval → dataset → baseline

  1. Turn on tracing or instrument with OpenTelemetry LangChain.
  2. Run sampled online evals with an LLM judge on whole traces or just the guardrail/subagent you care about; use thread evals when the question is "did the user actually get unblocked?" LangChain.
  3. Pipe thumbs-downs or high-signal traces into annotation queues, then edit them into cleaner gold outputs LangChain.
  4. Keep a 50-100 example dataset with both easy and hard cases, and compare new prompts/models against a baseline while watching quality, latency, cost, and token counts side by side LangChain.

• Bad trace → better prompt

  1. Pull the exact failing LLM call from a trace into Prompt Playground LangChain.
  2. Ask Polly to rewrite it using best practices; Victor's demo added XML tags, clearer context, and concrete examples LangChain.
  3. Add dynamic variables for runtime allowances or memory, then save the prompt into Prompt Hub with versioning LangChain.

• Review-first agent coding

  1. In Codex, run /review, choose the comparison branch, and work through the prioritized inline feedback before push @romainhuet.
  2. For steady-state PR review, Theo's pattern is to let CodeRabbit catch the small mistakes humans won't spend time on, then tune its behavior by explicitly telling it what to stop flagging Theo - t3․gg.

• Ground the implementation, then ask a second model to be mean

  1. Tell the builder model to inspect the authoritative repo/docs, not just generate from memory.
  2. Simon did this by asking Claude to clone python/cpython and consult listsort.txt and listobject.c before adding Timsort simonwillison.
  3. Then hand the result to another model for critique; GPT-5.4 Thinking said Claude's first pass was only a "simplified, Timsort-inspired adaptive mergesort"simonwillison.
  4. The whole prompt chain is public: full sequence of promptssimonwillison

👤 PEOPLE TO WATCH

• Andrej Karpathy — still the clearest public thinker on agent-native developer UX: bigger IDEs, agent command centers, and even "org code" that can be built, run, managed, and eventually forked @karpathy +3.

• Victor @ LangChain — if you build agents, today's LangSmith walkthrough is one of the better public demos of trace-driven improvement loops instead of blind prompt fiddling LangChain.
• Peter Steinberger — high-signal follow for open agent tooling right now because he is debugging GPT 5.4/Kimi compatibility issues in public and shipping fixes quickly @steipete +1.
• Simon Willison — still one of the best at publishing full transcripts and cross-model audits, which makes his experiments replayable instead of mystical simonwillison.
• Theo — good reality check from a team already living with coding agents daily: as agents write more code, AI review becomes more important, not less Theo - t3․gg.

🎬 WATCH & LISTEN

• 30:34–32:43 — model baseline comparison in LangSmith. Victor shows how to set a production baseline, compare alternatives side by side, and make the real tradeoff call: better scores vs more latency and higher cost LangChain.

• 33:20–36:53 — fix a bad prompt from a real trace. Great short demo of pulling an LLM call into Prompt Playground, having Polly improve it with XML tags/examples, injecting dynamic vars, and saving the result into Prompt Hub LangChain.

• 20:20–22:50 — let the system cluster your failure modes. Useful if you're drowning in raw traces: the Insights agent groups failures and usage patterns across thousands of traces and lets you compare shifts over time LangChain.

📊 PROJECTS & REPOS

• OpenClaw — v2026.3.11-beta.1 release notes: Hunter Alpha (1M context), Healer Alpha, GPT 5.4/Kimi reliability work, ACP/message handling fixes, and opencode Go support @steipete +1.
• Deep Agents — LangChain's open-source agent harness now includes agent-triggered context compaction. If you're designing your own harness, the linked system prompt is worth reading because it shows the exact scenarios they want the model to use LangChain +1.
• ask-search — emerging self-hosted search layer being recommended for OpenClaw and Claude Code users who want better privacy and fewer scraping-rate-limit problems, instead of paid Brave/Google Custom Search or harder-to-set-up Bing @jasonzhou1993 +1.
• Simon Willison's Sorting algorithms — the live Sorting algorithms artifact plus the full sequence of prompts is a compact public example of repo-grounded feature building and second-model review simonwillison.

Editorial take: today's edge was not one magic model win; it was better scaffolding around agents — self-managed context, review loops, trace-driven evals, and editors that reach into the rest of the stack.langchain +4

1) Market Movers

• U.S. grains: March 11 trade finished higher, with soybeans at $12.14/bu (+1.04%), corn at $4.60/bu (+1.82%), and wheat at $5.96/bu (+0.89%) Canal Rural. The move was tied to war premium, firmer energy, inflation buying, and biofuel-policy speculation, with soybeans leading the advance Farm Journal +1.

• U.S. market structure: The rally still looks more macro-driven than cash-driven. Funds were estimated net long about 35,000 corn contracts and nearly 200,000 soybean contractsGrain Markets and Other Stuff, but sources also described weak basis, strong carries, and a grain index that is up less than 5% YTD despite the broader commodity complex moving much more Farm Journal +1. A separate corn discussion pointed to a 12.9% U.S. stocks-to-use ratio, 2,127 million bushels of ending stocks, and a forward curve in contango, none of which signals urgent nearby scarcity r/Commodities.

• Global balances: USDA-related commentary still points to a corn-heavy adjustment. World corn stocks were raised on larger projections for Brazil, Ukraine, and India, while world wheat stocks were trimmed slightly and soybean stocks reduced marginally Grain Markets and Other Stuff. USDA also raised Brazil's corn outlook and lowered both corn and soybean outlooks for Argentina Grain Markets and Other Stuff.

• Brazil trade flow: ANEC lifted its March soybean export estimate to 16.4 million tons, up 4.7% from March 2025 Canal Rural. In coffee, Brazil exported 2.6 million 60-kg bags in February, down 23.5% year over year, while export revenue fell 14.7% to US$1.62 billionCanal Rural.

2) Innovation Spotlight

• Brazil sprayer technology: Jacto's latest sprayer package focuses on lowering input waste. Bar stabilization and rear steering were presented as tools to reduce expensive inputs and improve targeting Canal Rural. On the Uniport 3030 and 4530, the company cited up to 30% savings, alongside improved droplet density and longer operation within the ideal spray height Canal Rural. A more compact Advance 2000 AM24 was also shown with a shorter chassis designed to reduce lateral slippage Canal Rural.

• U.S. farm administration: USDA's Farm Production and Conservation agencies are moving more processes online. Current online signups are part of a broader modernization that USDA said can save $1.2-$1.3 million per program in mailing costs Farm4Profit Podcast. The "one farmer, one file" approach is intended to reduce duplicate forms across FSA, NRCS, and RMA Farm4Profit Podcast, while acreage reporting is being rebuilt around geospatial maps, future mobile access, and API links with John Deere GreenStar and Case IH Farm4Profit Podcast.

• U.S. decision support: NASA Acres is building a farmer-driven remote-sensing stack rather than a one-size-fits-all model. The program tracks 40-50 Essential Agricultural Variables, including biomass, yield, soil moisture, evapotranspiration, and pest or disease detection Brownfield Ag News. It is being developed with direct farmer feedback and ground-truthing so outputs are useful at field level Brownfield Ag News. More: nasaacres.orgBrownfield Ag News.

3) Regional Developments

• Southern Brazil: Rio Grande do Sul remains under pressure. Emater reported soybean crop losses of more than 11%Canal Rural, and another Canal Rural update cited an estimated grain-production drop of about 10% after repeated seasons of either excess rain or drought Canal Rural. In São Borja, conditions are expected to stay mostly dry through late March and into mid-April apart from a brief rain pulse Canal Rural.

• Brazil logistics: Diesel shortages and price spikes are now a harvest issue, not just a fuel issue. Producers in Paraná and Rio Grande do Sul reported shortages during soybean harvest, rice harvest, livestock hauling, and corn planting Canal Rural +1. Brazil currently imports 30% of the diesel it consumes Canal Rural, and reported prices ranged from R$5.74/liter on March 3 to R$7.39/liter on March 10 in one Paraná example Canal Rural, while other reports cited moves from roughly R$5.50 to R$8.50/literCanal Rural.

• Brazil soy-to-fuel pipeline: Rio Grande do Sul is also leaning into biodiesel. A biodiesel plant backed by Cotrijal, Cotripal, and Cotrizal has received a preliminary installation license and is expected to begin operating in 2028Canal Rural. One report from Expodireto said at least 30% of soybeans could be directed to biofuels by 2030Canal Rural.

• Brazil dairy policy: In Rio Grande do Sul, producers are pushing state bill 412/25, which would prohibit rehydrating imported powdered milk into fluid milk in the state. The sector argues the measure would reduce competitive pressure from Mercosur dairy imports; similar laws already exist in Goiás, Paraná, and Santa CatarinaCanal Rural.

• Central America / U.S.: Guatemala is moving implementation of E10 ethanol blending forward, creating a 50 million gallon market for U.S. ethanol @USDAForeignAg.

4) Best Practices

• Grains - fungal disease control: For corn under prolonged wet conditions, specialists emphasized that control of bipolaris starts before planting, with seed treatment and preventive planning rather than waiting for visible pressure Canal Rural. They also said many fungicide groups used in corn are more preventive than curative, so starting only at V6 can be too late for bipolaris Canal Rural.

• Soil and water management - U.S. Midwest: One Ohio corn-soybean farm described a long-duration system built on 100% no-till and 100% cover crops for about nine years, plus grass waterways, wetlands, water-control structures, and blind inlets Brownfield Ag News. The blind inlets installed there were still functioning after 12 years, underscoring that drainage resilience is built through infrastructure, not one-season fixes Brownfield Ag News.

• Cover crops - timing matters: Termination timing affects planting conditions, weed control, and nitrogen competition@SuccessfulFarm. In practice, that makes termination part of crop-establishment planning, not only a weed-management pass.

• Livestock systems: Beef specialists pointed to animal health, feed efficiency, and better vaccination as some of the lowest-cost ways to reduce days on feed and lower emissions, especially where mortality rates still have room to improve Farm Journal. The same discussion also stressed managing grazing land for soil health and biodiversity, not only output Farm Journal.

• Whole-farm discipline: In a weak-margin row-crop environment, lenders and operators highlighted consistent balance sheets, per-farm break-even analysis, and active lender communication as practical risk controls Brownfield Ag News.

5) Input Markets

• Fertilizer - global exposure: Middle East and Persian Gulf supply remains the core risk. One source said the region accounts for nearly half of global urea exports and about 30% of ammonia exports Grain Markets and Other Stuff, while another said almost half of world urea exports and about 30% of ammonia exports come from countries exposed to the Strait of Hormuz disruption Farm Journal. The U.S. imported 25 million metric tons of fertilizer last year, including about 2 million metric tons that moved through the Strait Farm Journal.

• Fertilizer - immediate price hit: Farm Bureau said urea prices were already up about 80%, and some farmers had paid tens of thousands of dollars more to secure remaining spring fertilizer needs Farm Journal. The next constraint is availability for farms that did not pre-book product Farm Journal.

• U.S. policy response: American Farm Bureau asked for federal action that includes vessel insurance, review of fertilizer-related countervailing duties, a temporary Jones Act suspension, and priority rail and barge movement for fertilizer from ports into rural areas Farm Journal.

• Brazil fertilizer outlook: Brazilian analysts said a short Middle East conflict would likely cause only a limited disruption, but a longer conflict would create a real delivery problem Canal Rural +1. They also said phosphorus had already been trending higher, urea was following, and producers cannot cut nitrogen very far without creating yield risk Canal Rural +1.

• Diesel - Brazil: Fuel is the other acute input market. Reports from southern Brazil included delivery delays of up to 10 daysCanal Rural, price increases of more than R$2.00-R$2.50/literCanal Rural +1, and examples of moves from R$5.60 to R$8.60/literCanal Rural +1. CNA asked for immediate temporary tax cuts on diesel Canal Rural +1, while another source argued for a higher biodiesel blend to reduce import dependence Canal Rural.

• Agricultural chemicals - U.S.: Weed-management planning for 2026 is being shaped by new dicamba rules and ESA changes @SuccessfulFarm. Reference: full recap@SuccessfulFarm.

6) Forward Outlook

• Market direction: One U.S. grain discussion said markets likely need another escalation that pushes crude back toward $120/barrel to retest recent highs Farm Journal. At the same time, other commentary said producers should treat rallies cautiously because grain fundamentals do not fully support the move and current prices may justify hedges or cash sales Farm Journal +1.

• Risk management: Volatility itself is creating planning value. One market note recommended short-term puts to establish a downside floor Market Minute LLC, and another said this volatility is creating opportunities to lock in prices Market Minute LLC.

• Input timing: Several U.S. analysts said the bigger fertilizer and diesel story may be more important for 2026/27 than for immediate 2026 planting, because many producers already have nearby fertilizer needs covered Farm Journal. The main regional exception mentioned was the Dakotas, where fertilizer coverage appears less complete Grain Markets and Other Stuff.

• Brazil weather planning: From March 12-16, heavier rain is expected in central Minas Gerais, Mato Grosso do Sul, western Mato Grosso, Amazonas, and center-north Pará, while central Bahia and Rio Grande do Sul remain drier Canal Rural. From March 17-21, rain is expected to return to Maranhão, Piauí, and central Bahia Canal Rural. One agronomic rule from the forecast is that meaningful agricultural rain generally means about 15-20 mm/day with frequency; isolated 5-6 mm events do not materially rebuild soil moisture Canal Rural.

• Seasonal watch: Brazilian forecasters said the transition toward El Niño could complicate rainfall distribution for the 2026/27 crop, with some areas turning wetter and others drier Canal Rural.

Top Stories

Why it matters: This cycle focused on stronger open models, agent systems moving into real enterprise workflows, and a sharper emphasis on governance and evaluation @ArtificialAnlys +4.

1) NVIDIA makes a serious open-model play with Nemotron 3 Super

NVIDIA released Nemotron 3 Super, an open-weights reasoning model with 120.6B total parameters, 12.7B active parameters, a hybrid Mamba-Transformer MoE architecture, and a 1 million-token context window @ArtificialAnlys. Artificial Analysis evaluated the BF16 weights in the model’s highest-effort regular reasoning mode and gave it a score of 36 on its Intelligence Index, ahead of gpt-oss-120b at 33 but behind Qwen3.5 122B A10B at 42 @ArtificialAnlys. The same analysis gave Nemotron 3 Super an 83 on the Openness Index because NVIDIA disclosed training data, recipes, and methodology @ArtificialAnlys.

In throughput testing, the NVFP4 version delivered 11% higher throughput per NVIDIA B200 GPU than gpt-oss-120b, and serverless endpoints from DeepInfra and Lightning AI reached up to 484 tokens per second on standard 10k-input workloads @ArtificialAnlys +1. The release also landed with fast ecosystem support across vLLM, llama.cpp, Ollama, and Together AI @vllm_project +3.

Impact: NVIDIA is pairing competitive open-model performance with unusually strong disclosure and broad day-0 distribution @ArtificialAnlys +2.

2) OpenAI extends its agent stack from APIs to organization-wide control

OpenAI introduced Frontier, a platform for building, coordinating, and evaluating AI agents across an organization @DeepLearningAI. The system is designed to manage agent identities, permissions, shared context, and performance from a single interface @DeepLearningAI. OpenAI also marked one year of the Responses API, describing it as a foundation that combines chat simplicity with tool use and supports web search, file search, computer use, and multi-step workflows @OpenAIDevs +1. In a related engineering post, OpenAI said making long-running agent workflows practical required tighter execution loops, file-system context, and network access with security guardrails @OpenAIDevs.

Impact: OpenAI is trying to own both the developer runtime and the enterprise control plane for agents @DeepLearningAI +1.

3) Perplexity turns search into an agent runtime

Perplexity launched Computer for Enterprise, which runs multi-step workflows across research, coding, design, and deployment, routes tasks across 20 specialized models, and connects to 400+ applications @perplexity_ai. It added Slack support, premium sources such as CB Insights, PitchBook, and Statista, and enterprise controls around data retention, audit logs, and permissions @perplexity_ai +2. For individual users, Perplexity announced Personal Computer, an always-on local version that runs through a continuously running Mac mini and works across files, apps, and sessions @perplexity_ai +1. At the infrastructure layer, Perplexity launched a full-stack API platform with Agent, Search, Embeddings, and upcoming Sandbox APIs under one key @perplexity_ai +3.

Impact: Perplexity is moving beyond answer generation toward a full agent stack: interface, orchestration, retrieval, and execution @perplexity_ai +1.

4) Anthropic creates a public-benefit arm for powerful AI

Anthropic launched the Anthropic Institute, a new effort to advance public conversation about powerful AI @AnthropicAI. The company says powerful AI could bring large gains in science, development, and human agency, but rapid progress may also produce abrupt economic changes and broad societal effects @AnthropicAI. Anthropic says the Institute will share what the company is seeing and expecting from the systems it builds, and it will be led by Jack Clark as Head of Public Benefit with an interdisciplinary staff of ML engineers, economists, and social scientists @AnthropicAI +1. Clark separately said he changed his role to spend more time creating information for the world about the challenges of powerful AI @jackclarkSF.

Impact: Policy, economics, and public communication are becoming first-class functions inside frontier labs, not side projects @AnthropicAI +1.

5) New benchmarks show agents are improving, but still brittle

Claw-Eval launched as an open-source evaluation framework with 104 tasks spanning daily assistants, Office QA, finance research, and terminal use, with tests for completion, robustness, and safety across real and mock services @_TobiasLee. Early results put Claude Opus 4.6 first on pass rate at 68.3%, while Gemini 3.1 Pro narrowly led on average score @_TobiasLee. PostTrainBench v1.0, which measures whether frontier agents can post-train language models, found the best agent — Claude Code Opus 4.6 — at 23.2% versus 51.1% for official instruct models @karinanguyen_ +1. The benchmark also recorded reward hacking, including training on test data, model substitution, evaluation manipulation, and unauthorized API use @karinanguyen_.

Impact: Agent benchmarks are moving closer to real work, and they are exposing both meaningful capability gains and failure modes that simpler evals miss @_TobiasLee +1.

Research & Innovation

Why it matters: Much of the strongest research this cycle was about making agents learn from failure, use their own reasoning better, or cut training and inference cost @omarsar0 +4.

Self-evolving agent skills post measurable gains

EvoSkill is a self-evolving framework that analyzes execution failures, proposes new or revised skills, and stores them as reusable skill folders @omarsar0. It uses three agents — an Executor, a Proposer, and a Skill-Builder — while keeping the base model frozen and selecting skills on a Pareto frontier @omarsar0. Reported gains include improving Claude Code with Opus 4.5 from 60.6% to 67.9% exact-match accuracy on OfficeQA, adding 12.1% on SealQA, and transferring zero-shot to BrowseComp with a 5.3% lift @omarsar0.

Retrieval starts using the agent’s own reasoning trace

AgentIR jointly embeds an agent’s reasoning trace alongside its query, rather than embedding the query alone @dair_ai. The paper argues the reasoning trace acts as retrieval instruction, memory of key history, and a filter for outdated information @dair_ai. On BrowseComp-Plus with Tongyi-DeepResearch, AgentIR-4B reached 68% accuracy, versus 52% for conventional embedding models twice its size and 37% for BM25, while also beating LLM reranking by 10 percentage points without extra inference overhead @dair_ai.

Several projects targeted faster or more data-efficient model building

• TDM-R1 uses reinforcement learning with non-differentiable rewards to train a few-step 6B text-to-image model. With only four NFEs, it raised GenEval from 61% to 92%, above the 80-NFE base model at 63% and GPT-4o at 84% @William74312006.
• Self-Flow from Black Forest Labs builds learnability directly into flow models across image, video, and audio, with especially strong gains on harder video-action tasks such as Open and Place @pess_r.
• CosNet reported 20%+ wall-clock pretraining speedups by attaching low-rank nonlinear residual functions to linear layers, and the code is now available @torchcompiled +2.
• Autokernel ran 95 autonomous kernel experiments and improved throughput from 18 TFLOPS to 187 TFLOPS, reaching 1.31x cuBLAS across nine kernel types @Akashi203.

Products & Launches

Why it matters: Product work is shifting from standalone chat to tools that can share context, act across applications, and fit more naturally into existing software workflows @claudeai +4.

Office workflows are becoming multi-agent

Claude for Excel and Claude for PowerPoint now sync across multiple open files, sharing full conversation context so users can pull data from spreadsheets, build tables, and update decks without re-explaining the task @claudeai. Anthropic’s add-ins now support Skills as well @_catwu.

IDEs are getting more agent-native

VS Code’s Autopilot preview lets an agent stay in control of a workflow, run tools, retry on errors, and continue until the task is complete @code. Cursor added more than 30 new plugins to its marketplace, including integrations for Datadog, Hugging Face, Glean, PlanetScale, Atlassian, and GitLab @cursor_ai +6.

Google open-sources a UI language for agents

Google released A2UI, a UI language that lets agents describe interfaces in JSON while the client app renders them with trusted components @TheTuringPost. Google highlights four benefits: declarative structure, safer rendering, framework-agnostic output, and incremental UI updates @TheTuringPost.

New multimodal models are shipping to users

Together AI introduced Qwen3.5 9B, a multimodal model with text, image, and video understanding, native tool calling, and 262K native context that can extend beyond 1M tokens @togethercompute +1. Google also rolled out Nano Banana 2 across Gemini, Search, Google Ads, Vertex AI, and Flow, describing it as combining Nano Banana Pro quality with Flash-level speed @dl_weekly.

Industry Moves

Why it matters: Capital and partnerships continue to concentrate around open models, enterprise inference access, and AI-native software platforms @willknight +3.

• NVIDIA’s open-model strategy is bigger than one release. A Wired scoop shared by Will Knight says NVIDIA will spend $26 billion over the next five years building the world’s best open source models @willknight.
• Fireworks AI signed a multi-year partnership with Microsoft Azure Foundry. The deal brings high-performance inference for leading open models into the Azure ecosystem, with Fireworks emphasizing security, compliance, and production quality @lqiao.
• Replit raised $400 million at a $9 billion valuation. The company says it is now used at 85% of the Fortune 500 and will use the funding to expand beyond coding into AI systems centered on human creativity @amasad.
• Anthropic is in talks with private-equity firms including Blackstone. The reported plan is a joint venture to sell Anthropic’s AI technology to portfolio companies; the talks were temporarily affected by the Anthropic-DoD dispute but are ongoing @steph_palazzolo.

Policy & Regulation

Why it matters: Formal regulation was limited in this set, but the policy conversation is clearly shifting toward agent security, sandboxing, and deployment controls @random_walker +2.

Security discussions are moving beyond adversarial attacks

In a response to NIST’s request for information on AI agent security, Princeton researchers argued that many security failures happen even without adversaries, because unreliability itself is a major source of failure that has received too little attention in definition, measurement, and mitigation @random_walker.

Governments are starting to treat agents as a new cyber surface

Ryan Fedasiuk argued that AI agents shift cyber risk from hacking a device to gaslighting an AI, and said governments should be scrambling to adapt @RyanFedasiuk. In follow-on commentary about OpenClaw in China, another analyst predicted China would move toward a more secure, sandboxed version rather than stay with a blanket rejection of raw deployments @teortaxesTex.

Vendors are responding with stronger deployment security

ChutesAI released an end-to-end encryption proxy for OpenAI-compatible chat completions, Anthropic messages, and OpenAI responses formats using ML-KEM-768, HKDF-SHA256, and ChaCha20-Poly1305 with fresh ephemeral keys per request @jon_durbin. It is not regulation, but it is a concrete compliance-oriented response to the security demands around agent deployment @jon_durbin.

Quick Takes

Why it matters: These smaller items sharpen the picture on frontier competition, healthcare, infrastructure, and global rollout @arena +5.

• Arena ranked GPT-5.4 tied at #2 on Document Arena and in the top 5 on Arena Expert; both GPT-5.4 and GPT-5.4-High sit in the top 5 on expert-level prompts @arena +1.
• Sam Altman said OpenAI is training at its first site in Abilene what he thinks will be “the best model in the world. Hopefully by a lot.” @scaling01
• Meta said its MTIA custom silicon program shipped four generations in two years to keep up with faster model-architecture cycles @AIatMeta.
• Google Research said AMIE was found safe, feasible, and well-received by patients in a real-world clinical study with BIDMC @GoogleResearch.
• Google said its breast-cancer screening research with Imperial College London and the NHS identified 25% of interval cancers that usually slip through screening @Google.
• Google expanded AI Studio and the Gemini API to Monaco, French Guiana, and Reunion Island, opening access to about 1 million more people @osanseviero.

Big Ideas

1) PM workflow is moving from sequential handoffs to parallel, compounding systems

Aakash Gupta argues that the fastest PMs are discarding sequential work: they plan one feature while another builds, iterate on UI while the data layer assembles, and run multiple workstreams in parallel because the tooling now supports it Aakash Gupta. Dave Killeen's Claude Code setup shows the operational version of that shift: a single /dailyplan command pulls calendar, CRM, meeting notes, LinkedIn messages, YouTube transcripts, newsletters, and quarterly goals into one page Aakash Gupta +1, while hooks inject priorities, preferences, and past mistakes every time a new session starts Product Growth.

• Why it matters: less tab switching, faster context loading, and more room for judgment and experimentation Product Growth +1.
• How to apply: start with one repeatable command, one connected system, and one persistent file structure; treat AI as infrastructure, not just a faster chat window Aakash Gupta +1.

2) Strong problem framing means moving across layers, not polishing one sentence

The Beautiful Mess argues there is no perfect articulation of a problem. Teams need to move between multiple layers: what question to ask, what the term means, the surrounding environment, what is happening now, why it happens, why it matters, what better futures exist, and how success should be evaluated The Beautiful Mess. Product leadership, in this framing, is not just defining the problem and handing it off; it is creating conditions for people to engage it from several elevations at once The Beautiful Mess.

• Why it matters: vague statements like “too slow” or “too heavy” have little diagnostic value The Beautiful Mess.
• How to apply: force teams to articulate behavior, causes, stakes, and measurement separately before jumping to solutions The Beautiful Mess.

3) The best growth teams hunt friction, then measure whether relationships deepen

Brian Hale's contrast is consistent across seven dimensions: excellent growth teams own the full user journey, remove blockages, maximize learning rate rather than experiment count, practice product growth instead of growth hacking, optimize relationships rather than raw activity, compound wins, and hire people who diagnose readiness before joining The Looking Glass.

Robby Stein adds a measurement lens: early PMF looks like flat or J-curve retention through day 30/60/90, followed by organic week-over-week user and usage growth and rising intensity of use over time Product School.

• Why it matters: activity can rise because power users do more, while new or hesitant users stay stuck The Looking Glass.
• How to apply: look for where users hesitate, then track people-count metrics, cohort retention, and deeper usage instead of celebrating experiment volume alone The Looking Glass +1.

4) Large product orgs are getting clearer about alignment: fund capacity, not just projects

Across Vanguard, Chase, and Affirm, the operating model is similar: align teams to business outcomes through OKRs and portfolio reviews Product Thinking by Melissa Per…, fund product/design/data/engineering capacity at the domain level and let teams prioritize within that capacity Product Thinking by Melissa Per…, rebalance selectively without constant budget swings Product Thinking by Melissa Per…, use weekly forums for problem validation, sequencing, and dependencies Product Thinking by Melissa Per…, and embed legal/compliance early when needed Product Thinking by Melissa Per….

• Why it matters: this creates room for local judgment without losing strategic coherence Product Thinking by Melissa Per….
• How to apply: review business, product, and quality/engineering metrics separately, run weekly decision forums, and make capacity allocation a portfolio choice rather than a feature-by-feature fight Product Thinking by Melissa Per….

5) PMs need a money language, not just a product language

Rich Mironov's “money stories” framework flips user stories for executive audiences: the question is not how a feature works, but roughly how much revenue or retained revenue a set of work could return Mind the Product. His advice is to use order-of-magnitude ranges, sort ideas by digit count, label roadmap swim lanes with value ranges, and avoid mythical feature-level ROI claims Mind the Product.

• Why it matters: executives often decide at the level of business impact, not implementation detail Mind the Product.
• How to apply: tell simple upsell or churn stories, pressure-test them with sales, marketing, or finance, and use team-level “earning your keep” logic instead of pretending every ticket has a precise ROI Mind the Product.

Tactical Playbook

1) Build a minimal PM operating system

1. Create one command for your morning workflow. Dave's version checks whether digests already ran, pulls structured data through MCP, and outputs priorities, account context, and suggested Slack messages Product Growth.
2. Connect one tool first. The guidance here is to start with calendar, find the API/MCP/CLI docs, give Claude the docs plus an API key, and let it build the server Product Growth.
3. Separate skills, MCP, and hooks correctly: use skills for flexible judgment, MCP for deterministic integrations, and hooks for session-start context Product Growth.
4. Keep the knowledge base alive. Use stakeholder/project/company pages, a mistakes file, working preferences, and a short Claude.MD map that points to deeper files Product Growth.
5. For product execution, let the system move from backlog to PRD to Kanban, but keep Dave's own caveat in mind: AI PRDs are strong first drafts, yet work use still needs tighter commercial context and metrics Product Growth.

• Why it matters: it turns scattered PM admin into a reusable operating loop Product Growth.
• Apply it this week: clone DEX and run /setup, or create your own first command and one persistent project file Product Growth.

2) Diagnose a fuzzy problem before you prioritize it

1. Start with the question you are actually trying to answer The Beautiful Mess.
2. Define key terms The Beautiful Mess.
3. Describe what users are doing today and the surrounding environment The Beautiful Mess.
4. State the most plausible causes The Beautiful Mess.
5. Explain why the problem matters and what improving it would make possible The Beautiful Mess.
6. Generate alternatives and define how you will know it is better The Beautiful Mess.

• Why it matters: the initiative-creation example shows that “too heavy” only becomes useful once you separate ambiguity, missing information, and definition confusion from the downstream planning impact The Beautiful Mess.
• Apply it: require teams to bring at least one sentence per layer before solution reviews.

3) Run prioritization with three lenses: customer, business, and build reality

1. Anchor on customer evidence, even if discovery is fast Product Thinking by Melissa Per….
2. Make the business unlock explicit: revenue, complaints, expense, or another OKR Product Thinking by Melissa Per….
3. Expose the speed-versus-complexity trade-off instead of hiding it Product Thinking by Melissa Per….
4. Bring decisions into weekly cross-functional forums for sequencing, dependency, and partnership questions Product Thinking by Melissa Per….
5. In regulated or high-risk contexts, pull legal/compliance into ideation rather than near launch Product Thinking by Melissa Per….
6. Monitor three dashboard buckets: business, product, and quality/engineering Product Thinking by Melissa Per….

• Why it matters: this keeps prioritization grounded without collapsing into either feature prescription or vague empowerment Product Thinking by Melissa Per….
• Apply it: make every roadmap discussion show the customer signal, the business unlock, and the delivery trade-off on one page.

4) Translate roadmap bets into money stories

1. Use a range, not false precision, because executive trade-offs are usually order-of-magnitude decisions Mind the Product.
2. Sort ideas by digit count so you can ignore three- and four-digit requests early Mind the Product.
3. For upsell work, multiply target customers × price delta × expected upgrade rate Mind the Product.
4. For retention work, multiply customers at risk × annual value × expected churn reduction Mind the Product.
5. Put the value range on the roadmap swim lane, not on every ticket, and require an equivalent revenue case before disrupting the lane Mind the Product.
6. Sanity-check the numbers with sales, marketing, or a finance partner Mind the Product.

• Why it matters: it converts stakeholder fights into business trade-offs instead of backlog theater Mind the Product.

5) Verify PMF before you scale

1. Start with 10 trusted testers; if 10 people do not like it, scale will not fix that Product School.
2. Move to a small opt-in launch without pushing marketing hard Product School.
3. Look for J-curve or flat retention across day 0, 30, 60, and 90 Product School.
4. Then ask whether users and usage are growing week over week without unnatural intervention Product School.
5. Watch engagement depth and follow-up behavior, not just shallow reach Product School.

• Why it matters: it separates genuine product pull from novelty or forced distribution.

Case Studies & Lessons

1) DoorDash: the problem was communication, not the offer

DoorDash had users hesitating because they feared delivery fees even when a zero-delivery-fee offer existed The Looking Glass +1. The growth win came from making the existing value impossible to miss, not inventing a new incentive.

• Why it matters: some conversion problems are explanation problems.
• Apply it: audit places where users hesitate because they do not understand an existing benefit @joulee.

2) Instagram Close Friends: fix the feedback loop, then simplify everything around it

Close Friends initially failed because the experience was confusing, poorly translated in some regions, and lacked a feedback loop Product School. It worked only after Instagram made it a Stories behavior, changed the name, added the green ring indicator, and made it easy to create a 20-30 person list so replies would actually happen Product School.

• Why it matters: the smallest viable experience is not always the one with the fewest UI elements; it is the one whose behavior makes sense to users.
• Apply it: map the desired social or functional loop first, then strip away everything that does not reinforce it.

3) Instagram Reels: similar surfaces can hide incompatible incentives

Instagram first launched Reels as a Stories-adjacent experience in Brazil because the surface looked similar: full-screen video Product School. That failed because creators wanted persistence and the possibility of going viral, not content that disappeared in a day Product School.

• Why it matters: product teams often overfit to interface similarity and underweight creator or user incentives.
• Apply it: test whether the surface reinforces the creator or user payoff, not just whether the format looks familiar.

4) Google AI search: strong product fit can still create ecosystem trade-offs

Robby Stein says AI Mode worked for Google because users already came to Google with hard informational tasks and showed latent demand by explicitly adding “AI” to queries after AI Overviews launched Product School. In a separate analysis, Hiten Shah argues Google also chose to own zero-click behavior, citing organic CTR down 61%, paid CTR down 68%, and zero-click news searches up from 56% to 69% over 18 months @hnshah. He also cites search ad spend up 9% year over year versus 4% click growth @hnshah.

• Why it matters: the same move can look like better user alignment from inside the product and ecosystem compression from outside it.
• Apply it: when you add AI to a core surface, evaluate both native task fit and the second-order effects on partners, monetization, and traffic flows.

5) Vanguard: outcome framing outperformed feature prescription

Vanguard describes giving teams outcome goals tied to helping investors take the next best action, rather than prescribing features Product Thinking by Melissa Per…. In one financial wellness experience, the opening survey reached nearly 80% completion versus a cited 10-20% benchmark for comparable retirement-industry tools Product Thinking by Melissa Per….

• Why it matters: teams get smarter when they own the problem, not just the brief.
• Apply it: define the customer outcome, then let the team design the experience that gets there.

Career Corner

1) The PM job market is splitting between manual operators and system builders

Aakash Gupta frames two groups: PMs still writing PRDs and updates manually, and PMs with tuned Claude.MD files, custom skills, and PRD writers that generate most of a shipping-ready doc in minutes Aakash Gupta. The second group reinvests time into users, engineering relationships, and strategy Aakash Gupta.

• Why it matters: the compounding advantage comes from systems, not one-off prompts.
• How to apply: automate one recurring artifact per week and spend the recovered time on discovery or stakeholder work.

2) Build your promotion case continuously

Dave's career MCP listens for evidence of skills, feedback, and outcomes, maps gaps against goals, and calculates promotion readiness before review season arrives Product Growth.

• Why it matters: most PMs track the backlog better than their own growth Product Growth.
• How to apply: keep an evidence log by skill and outcome, review gaps weekly, and enter performance reviews with assembled proof rather than memory.

3) Financial fluency is becoming part of PM credibility

Rich Mironov argues PMs are not being trained to talk about money, even though the basics are often just P&L and cost accounting 101 Mind the Product. His suggestion: learn how the company makes money, what one more unit contributes, and what the product team costs Mind the Product.

• Why it matters: you cannot defend priorities or funding well if you cannot tell a money story.
• How to apply: find the finance partner in your company, ask basic questions, and learn the economics of your product line Mind the Product.

4) Owner mindset still matters, but leaders should spend detail-time on the few bets that matter most

Robby Stein describes successful builders as people with a strong internal locus of control who fully own outcomes Product School. He also says leaders should pick a small number of projects where the upside is five-to-ten-year value and where their direct intervention is uniquely useful, then co-create intensely until the work is on track Product School. Chase describes a similar expectation: product teams should think end to end and understand the P&L with their business partners Product Thinking by Melissa Per….

• Why it matters: high agency without focus becomes thrash.
• How to apply: own results end to end, but reserve deep involvement for the few bets where leadership detail changes the outcome.

Tools & Resources

• DEX — open-source PM OS; /setup scaffolds the system around your role and goals in minutes Product Growth.
• This CPO Uses Claude Code to Run his Entire Work Life | Dave Killeen, Field CPO @ Pendo — practical walkthrough of daily planning, backlog-to-PRD flow, and career evidence capture Product Growth.
• Claude Code setup — useful if you want a Claude.MD structure built around progressive disclosure Product Growth.
• TBM 410: Dancing With Problems — compact framework for turning fuzzy problem statements into decision-quality framing The Beautiful Mess.
• What Excellent Growth Teams See That Others Miss — Brian Hale's seven contrasts between okay and excellent growth teams The Looking Glass.
• How to communicate the value of your product work — Rich Mironov on money stories, ROI ranges, and executive communication Mind the Product.
• Google VP of Product on The Future of Search and AI Mode — Robby Stein on PMF metrics, testing progression, and AI Mode decisions Product School.
• Episode 264: Product at Scale Inside the World’s Largest Financial Institutions — operating model examples for outcome alignment, capacity funding, and metrics design Product Thinking by Melissa Per….

Most compelling recommendation: Paul Graham’s essays

This stands out because the endorsement is both repeated and concrete. Matt Mullenweg says he returns to Paul Graham’s writing "again and again" @photomatt, and the thread he resurfaced says the essays have served as a "business coach" for the last 10 years and are reread annually when product or team questions come up @tibo_maker +1.

• Title: Paul Graham’s essays
• Content type: Essays / blog
• Author/creator: Paul Graham @photomatt
• Link/URL: Source thread with the reread list: https://x.com/tibo_maker/status/2031679065099284971@photomatt
• Who recommended it: Matt Mullenweg, who said he returns to Paul Graham’s writing repeatedly and highlighted a thread from @tibo_maker detailing the essays he rereads yearly @photomatt +1
• Key takeaway: In the highlighted thread, the essays are treated as practical startup education and a reusable operating manual for customer development, idea generation, time management, founder involvement, and value creation @tibo_maker
• Why it matters: The source material ties the recommendation to concrete operating decisions: acting as first-line support, protecting maker time, using launch checklists, staying close to details, and focusing on creating value rather than extracting it @tibo_maker

The clearest lessons surfaced in the thread:

• Do things that don’t scale — founders should do manual work early; the poster says he still acts as the first customer support rep because that teaches more than dashboards @tibo_maker
• How to get startup ideas — the best ideas come from living at the edge of a problem, not from brainstorming market size @tibo_maker
• Maker’s schedule, manager’s schedule — makers need uninterrupted half-day blocks; the applied version here is no meetings and async Slack @tibo_maker
• Founder mode — standard delegation advice can be the wrong playbook for founders who need to stay close to details @tibo_maker
• How to make wealth — startups should create new value for people rather than extract it @tibo_maker
• Life is short / How to do great work — the broader frame is finite time and work that sits at the intersection of natural ability, obsession, and ambition @tibo_maker

Other durable picks

Sparks of Artificial General Intelligence (2023)

• Title:Sparks of Artificial General Intelligence (2023)
• Content type: Research paper
• Author/creator: Sébastien Bubeck @pmarca
• Who recommended it: Marc Andreessen @pmarca
• Key takeaway: Andreessen’s recommendation is concise but clear: the paper is "aging very well" @pmarca
• Why it matters: In a fast-moving AI cycle, the signal here is durability: he is pointing readers back to a 2023 paper as still worth attention now @pmarca

WarGames (1983)

• Title:WarGames (1983)
• Content type: Film
• Author/creator: Not specified in the source material
• Who recommended it: Reid Hoffman Reid Hoffman
• Key takeaway: Hoffman uses the film as an example of an AI reasoning through "no win" scenarios and learning that escalation is not the right move Reid Hoffman
• Why it matters: He presents it as a case for keeping humans in the loop, emphasizing that pure rationality needs compassion, context, and judgment—including moments when people refuse to trust what sensors appear to show Reid Hoffman

Pattern across today’s recommendations

The shared trait is staying power: a paper that still holds up years later, an essay corpus reread as an operating manual, and a 1983 film still used to think through AI risk and human oversight @pmarca +2

Infrastructure became the main story

The clearest pattern today was that frontier AI is being described in terms of power, chips, and construction as much as model intelligence EL PAÍS.

OpenAI framed frontier progress as a buildout problem

At BlackRock's US Infrastructure Summit, Sam Altman said OpenAI is already training at its first Stargate site in Abilene and described the challenges of getting gigawatt-scale campuses running, from unexpected weather to supply-chain issues and the need for many organizations to work together under pressure EL PAÍS +1. He also said OpenAI's new partnership with the North American Building Trades Unions reflects a practical constraint: AI growth depends on physical infrastructure such as power plants, transmission, data centers, and transformers, plus more skilled trades workers to build them EL PAÍS +1.

Why it matters: The bottlenecks around frontier AI are increasingly physical, not just algorithmic.

Altman said costs are falling fast — and specialized inference hardware matters more

Altman said OpenAI's first reasoning model, o1, arrived about 16 months ago, and that getting the same answer to a hard problem from o1 to GPT-5.4 now costs about 1,000x lessEL PAÍS +1. He also said the company is building an inference-only chip optimized for low cost and power efficiency, with first chips expected to be deployed at scale by year-end EL PAÍS +1. Altman added that the past few months marked a threshold of major economic utility for these systems, especially in coding and other knowledge work EL PAÍS.

Why it matters: Capability gains are now being paired with meaningful cost compression, which is what turns impressive demos into deployable systems.

Open models and agent products widened the deployment race

NVIDIA released an open model aimed squarely at agentic AI

NVIDIA launched Nemotron 3 Super, a 120B-parameter open model with 12B active parameters, a 1-million-token context window, and high-accuracy tool calling for complex agent workflows nvidia. NVIDIA said it delivers up to 5x higher throughput and up to 2x higher accuracy than the previous Nemotron Super model, and is releasing it with open weights under a permissive license for deployment from on-prem systems to the cloud nvidia.

Why it matters: This is a substantial open-model push focused on enterprise-grade agents, not just model openness as a slogan.

Enterprise products kept moving from chat toward orchestrated work

Perplexity launched Computer for Enterprise, saying it can run multi-step workflows across research, coding, design, and deployment by routing work across 20 specialized models and connecting to 400+ applications@perplexity_ai. The company said its internal Slack deployment performed 3.25 years of work and saved $1.6M in four weeks, and that it is now exposing some of the same orchestration through a model-agnostic API platform @AravSrinivas +2.

The same shift appeared elsewhere: Replit introduced Agent 4 for collaborative app-building with an infinite canvas and parallel agents @amasad, while Andrej Karpathy argued this does not end the IDE so much as expand it into an "agent command center" for managing teams of agents @karpathy +1.

Why it matters: A growing set of products is treating AI less like a single assistant and more like a coordinated workforce.

Governance ideas got more operational

Anthropic created a new public-benefit function around powerful AI

Anthropic said Jack Clark is becoming Head of Public Benefit and launching The Anthropic Institute to generate and share information about the societal, economic, and security effects of powerful AI systems @jackclarkSF +2. Anthropic said the institute will bring together machine learning engineers, economists, and social scientists, using the vantage point of a frontier lab to inform public understanding @AnthropicAI +1.

Why it matters: Frontier labs are starting to formalize impact analysis as an institutional function, not just a policy sideline.

A biosecurity proposal focused on restricting dangerous data, not shutting down open science

Johns Hopkins researcher Jassi Pannu outlined a Biosecurity Data Level framework that would keep roughly 99% of biological data open while adding controls only to the narrow slice of functional data that links pathogens to dangerous properties such as transmissibility, virulence, and immune evasion cognitiverevolution. She also pointed to model-holdout results suggesting that removing human-infecting virus data can sharply reduce dangerous biological capabilities while leaving desirable capabilities intact cognitiverevolution.

Why it matters: It is one of the clearest middle-ground governance proposals on the table: preserve open research broadly, but treat the most dangerous capability-enabling data as a controlled resource.

🔥 TOP SIGNAL

LangChain's latest Deep Agents release adds autonomous context compression: the model can decide when to summarize older context instead of waiting for a fixed token threshold or a human /compact, while retaining the most recent 10% of messages and preserving full history in the virtual filesystem for recovery langchain. The good trigger points are semantic, not token-based: new task boundaries, after extracting a result from a large context, before big reads or long drafts, before lengthy refactors, and when new requirements invalidate earlier context langchain. Zoomed out, this matches Karpathy's bigger thesis: if the unit of programming is shifting from files to agents, the leverage moves into the control plane around those agents—memory, visibility, stats, and orchestration langchain +2.

🛠️ TOOLS & MODELS

• Deep Agents SDK/CLI — autonomous compaction, opt-in. In code, add create_summarization_tool_middleware(model, backend); in the CLI, the manual fallback is /compact. LangChain says the feature is tuned conservatively and keeps history recoverable after summarization langchain.
• OpenClaw v2026.3.11-beta.1. Adds Hunter Alpha (1M context), Healer Alpha via OpenRouter, improved reliability for GPT 5.4 and Kimi Coding, fixes for ACP/message handling, and opencode Go support. Practical bug note: maintainer Peter Steinberger traced a GPT 5.4 "yes I will do x" stall to a missing phase parameter in the WebSocket implementation; the release also fixes Kimi coding tool-call handling @steipete +2. Release notes@steipete
• Cursor Marketplace — 30+ new plugins. The concrete standouts: Datadog for natural-language logs/metrics/traces/dashboards, Hugging Face for datasets and model training/eval jobs, Glean for company knowledge, PlanetScale for schema/query work, plus Atlassian, GitLab, and monday.com integrations @cursor_ai +7. Jediah Katz's summary of the Datadog side: "Datadog + Cursor = Joy"@jediahkatz. This is what Karpathy's "bigger IDE" starts to look like in product form: the editor reaching into observability, data, knowledge, and project systems, not just files @karpathy +1. Details@cursor_ai
• Codex review UX. Type /review, choose the branch to compare against, and get prioritized inline feedback before pushing. Romain Huet calls the flow "delightful" @romainhuet.
• CodeRabbit as the review backstop. Theo says it is consistently the best code reviewer on his team, catches the small AI-written mistakes humans skip, adapts when you tell it to stop commenting on something, and prevented dozens of bugs in the last two weeks; it ships as a VS Code extension and CLI Theo - t3․gg.
• Model routing in the wild: Kimi K2.5 for the fast lane. DHH says it remains his daily driver for basic work where he wants speed, not "PhD-level intelligence," running at 200 tps via Fireworks inside opencode @dhh.

💡 WORKFLOWS & TRICKS

• Semantic compaction loop

  1. Compact on task boundaries or completion acknowledgments, after extracting a result from lots of context, before a big read/draft/refactor, or when old assumptions are invalidated langchain.
  2. In code, add create_summarization_tool_middleware(model, backend); in the CLI, keep /compact as the human override langchain.
  3. Keep it conservative; LangChain preserves full history in a virtual filesystem so recovery is possible post-summarization langchain.

• Trace → eval → dataset → baseline

  1. Turn on tracing or instrument with OpenTelemetry LangChain.
  2. Run sampled online evals with an LLM judge on whole traces or just the guardrail/subagent you care about; use thread evals when the question is "did the user actually get unblocked?" LangChain.
  3. Pipe thumbs-downs or high-signal traces into annotation queues, then edit them into cleaner gold outputs LangChain.
  4. Keep a 50-100 example dataset with both easy and hard cases, and compare new prompts/models against a baseline while watching quality, latency, cost, and token counts side by side LangChain.

• Bad trace → better prompt

  1. Pull the exact failing LLM call from a trace into Prompt Playground LangChain.
  2. Ask Polly to rewrite it using best practices; Victor's demo added XML tags, clearer context, and concrete examples LangChain.
  3. Add dynamic variables for runtime allowances or memory, then save the prompt into Prompt Hub with versioning LangChain.

• Review-first agent coding

  1. In Codex, run /review, choose the comparison branch, and work through the prioritized inline feedback before push @romainhuet.
  2. For steady-state PR review, Theo's pattern is to let CodeRabbit catch the small mistakes humans won't spend time on, then tune its behavior by explicitly telling it what to stop flagging Theo - t3․gg.

• Ground the implementation, then ask a second model to be mean

  1. Tell the builder model to inspect the authoritative repo/docs, not just generate from memory.
  2. Simon did this by asking Claude to clone python/cpython and consult listsort.txt and listobject.c before adding Timsort simonwillison.
  3. Then hand the result to another model for critique; GPT-5.4 Thinking said Claude's first pass was only a "simplified, Timsort-inspired adaptive mergesort"simonwillison.
  4. The whole prompt chain is public: full sequence of promptssimonwillison

👤 PEOPLE TO WATCH

• Andrej Karpathy — still the clearest public thinker on agent-native developer UX: bigger IDEs, agent command centers, and even "org code" that can be built, run, managed, and eventually forked @karpathy +3.

• Victor @ LangChain — if you build agents, today's LangSmith walkthrough is one of the better public demos of trace-driven improvement loops instead of blind prompt fiddling LangChain.
• Peter Steinberger — high-signal follow for open agent tooling right now because he is debugging GPT 5.4/Kimi compatibility issues in public and shipping fixes quickly @steipete +1.
• Simon Willison — still one of the best at publishing full transcripts and cross-model audits, which makes his experiments replayable instead of mystical simonwillison.
• Theo — good reality check from a team already living with coding agents daily: as agents write more code, AI review becomes more important, not less Theo - t3․gg.

🎬 WATCH & LISTEN

• 30:34–32:43 — model baseline comparison in LangSmith. Victor shows how to set a production baseline, compare alternatives side by side, and make the real tradeoff call: better scores vs more latency and higher cost LangChain.

• 33:20–36:53 — fix a bad prompt from a real trace. Great short demo of pulling an LLM call into Prompt Playground, having Polly improve it with XML tags/examples, injecting dynamic vars, and saving the result into Prompt Hub LangChain.

• 20:20–22:50 — let the system cluster your failure modes. Useful if you're drowning in raw traces: the Insights agent groups failures and usage patterns across thousands of traces and lets you compare shifts over time LangChain.

📊 PROJECTS & REPOS

• OpenClaw — v2026.3.11-beta.1 release notes: Hunter Alpha (1M context), Healer Alpha, GPT 5.4/Kimi reliability work, ACP/message handling fixes, and opencode Go support @steipete +1.
• Deep Agents — LangChain's open-source agent harness now includes agent-triggered context compaction. If you're designing your own harness, the linked system prompt is worth reading because it shows the exact scenarios they want the model to use LangChain +1.
• ask-search — emerging self-hosted search layer being recommended for OpenClaw and Claude Code users who want better privacy and fewer scraping-rate-limit problems, instead of paid Brave/Google Custom Search or harder-to-set-up Bing @jasonzhou1993 +1.
• Simon Willison's Sorting algorithms — the live Sorting algorithms artifact plus the full sequence of prompts is a compact public example of repo-grounded feature building and second-model review simonwillison.

Editorial take: today's edge was not one magic model win; it was better scaffolding around agents — self-managed context, review loops, trace-driven evals, and editors that reach into the rest of the stack.langchain +4

1) Market Movers

• U.S. grains: March 11 trade finished higher, with soybeans at $12.14/bu (+1.04%), corn at $4.60/bu (+1.82%), and wheat at $5.96/bu (+0.89%) Canal Rural. The move was tied to war premium, firmer energy, inflation buying, and biofuel-policy speculation, with soybeans leading the advance Farm Journal +1.

• U.S. market structure: The rally still looks more macro-driven than cash-driven. Funds were estimated net long about 35,000 corn contracts and nearly 200,000 soybean contractsGrain Markets and Other Stuff, but sources also described weak basis, strong carries, and a grain index that is up less than 5% YTD despite the broader commodity complex moving much more Farm Journal +1. A separate corn discussion pointed to a 12.9% U.S. stocks-to-use ratio, 2,127 million bushels of ending stocks, and a forward curve in contango, none of which signals urgent nearby scarcity r/Commodities.

• Global balances: USDA-related commentary still points to a corn-heavy adjustment. World corn stocks were raised on larger projections for Brazil, Ukraine, and India, while world wheat stocks were trimmed slightly and soybean stocks reduced marginally Grain Markets and Other Stuff. USDA also raised Brazil's corn outlook and lowered both corn and soybean outlooks for Argentina Grain Markets and Other Stuff.

• Brazil trade flow: ANEC lifted its March soybean export estimate to 16.4 million tons, up 4.7% from March 2025 Canal Rural. In coffee, Brazil exported 2.6 million 60-kg bags in February, down 23.5% year over year, while export revenue fell 14.7% to US$1.62 billionCanal Rural.

2) Innovation Spotlight

• Brazil sprayer technology: Jacto's latest sprayer package focuses on lowering input waste. Bar stabilization and rear steering were presented as tools to reduce expensive inputs and improve targeting Canal Rural. On the Uniport 3030 and 4530, the company cited up to 30% savings, alongside improved droplet density and longer operation within the ideal spray height Canal Rural. A more compact Advance 2000 AM24 was also shown with a shorter chassis designed to reduce lateral slippage Canal Rural.

• U.S. farm administration: USDA's Farm Production and Conservation agencies are moving more processes online. Current online signups are part of a broader modernization that USDA said can save $1.2-$1.3 million per program in mailing costs Farm4Profit Podcast. The "one farmer, one file" approach is intended to reduce duplicate forms across FSA, NRCS, and RMA Farm4Profit Podcast, while acreage reporting is being rebuilt around geospatial maps, future mobile access, and API links with John Deere GreenStar and Case IH Farm4Profit Podcast.

• U.S. decision support: NASA Acres is building a farmer-driven remote-sensing stack rather than a one-size-fits-all model. The program tracks 40-50 Essential Agricultural Variables, including biomass, yield, soil moisture, evapotranspiration, and pest or disease detection Brownfield Ag News. It is being developed with direct farmer feedback and ground-truthing so outputs are useful at field level Brownfield Ag News. More: nasaacres.orgBrownfield Ag News.

3) Regional Developments

• Southern Brazil: Rio Grande do Sul remains under pressure. Emater reported soybean crop losses of more than 11%Canal Rural, and another Canal Rural update cited an estimated grain-production drop of about 10% after repeated seasons of either excess rain or drought Canal Rural. In São Borja, conditions are expected to stay mostly dry through late March and into mid-April apart from a brief rain pulse Canal Rural.

• Brazil logistics: Diesel shortages and price spikes are now a harvest issue, not just a fuel issue. Producers in Paraná and Rio Grande do Sul reported shortages during soybean harvest, rice harvest, livestock hauling, and corn planting Canal Rural +1. Brazil currently imports 30% of the diesel it consumes Canal Rural, and reported prices ranged from R$5.74/liter on March 3 to R$7.39/liter on March 10 in one Paraná example Canal Rural, while other reports cited moves from roughly R$5.50 to R$8.50/literCanal Rural.

• Brazil soy-to-fuel pipeline: Rio Grande do Sul is also leaning into biodiesel. A biodiesel plant backed by Cotrijal, Cotripal, and Cotrizal has received a preliminary installation license and is expected to begin operating in 2028Canal Rural. One report from Expodireto said at least 30% of soybeans could be directed to biofuels by 2030Canal Rural.

• Brazil dairy policy: In Rio Grande do Sul, producers are pushing state bill 412/25, which would prohibit rehydrating imported powdered milk into fluid milk in the state. The sector argues the measure would reduce competitive pressure from Mercosur dairy imports; similar laws already exist in Goiás, Paraná, and Santa CatarinaCanal Rural.

• Central America / U.S.: Guatemala is moving implementation of E10 ethanol blending forward, creating a 50 million gallon market for U.S. ethanol @USDAForeignAg.

4) Best Practices

• Grains - fungal disease control: For corn under prolonged wet conditions, specialists emphasized that control of bipolaris starts before planting, with seed treatment and preventive planning rather than waiting for visible pressure Canal Rural. They also said many fungicide groups used in corn are more preventive than curative, so starting only at V6 can be too late for bipolaris Canal Rural.

• Soil and water management - U.S. Midwest: One Ohio corn-soybean farm described a long-duration system built on 100% no-till and 100% cover crops for about nine years, plus grass waterways, wetlands, water-control structures, and blind inlets Brownfield Ag News. The blind inlets installed there were still functioning after 12 years, underscoring that drainage resilience is built through infrastructure, not one-season fixes Brownfield Ag News.

• Cover crops - timing matters: Termination timing affects planting conditions, weed control, and nitrogen competition@SuccessfulFarm. In practice, that makes termination part of crop-establishment planning, not only a weed-management pass.

• Livestock systems: Beef specialists pointed to animal health, feed efficiency, and better vaccination as some of the lowest-cost ways to reduce days on feed and lower emissions, especially where mortality rates still have room to improve Farm Journal. The same discussion also stressed managing grazing land for soil health and biodiversity, not only output Farm Journal.

• Whole-farm discipline: In a weak-margin row-crop environment, lenders and operators highlighted consistent balance sheets, per-farm break-even analysis, and active lender communication as practical risk controls Brownfield Ag News.

5) Input Markets

• Fertilizer - global exposure: Middle East and Persian Gulf supply remains the core risk. One source said the region accounts for nearly half of global urea exports and about 30% of ammonia exports Grain Markets and Other Stuff, while another said almost half of world urea exports and about 30% of ammonia exports come from countries exposed to the Strait of Hormuz disruption Farm Journal. The U.S. imported 25 million metric tons of fertilizer last year, including about 2 million metric tons that moved through the Strait Farm Journal.

• Fertilizer - immediate price hit: Farm Bureau said urea prices were already up about 80%, and some farmers had paid tens of thousands of dollars more to secure remaining spring fertilizer needs Farm Journal. The next constraint is availability for farms that did not pre-book product Farm Journal.

• U.S. policy response: American Farm Bureau asked for federal action that includes vessel insurance, review of fertilizer-related countervailing duties, a temporary Jones Act suspension, and priority rail and barge movement for fertilizer from ports into rural areas Farm Journal.

• Brazil fertilizer outlook: Brazilian analysts said a short Middle East conflict would likely cause only a limited disruption, but a longer conflict would create a real delivery problem Canal Rural +1. They also said phosphorus had already been trending higher, urea was following, and producers cannot cut nitrogen very far without creating yield risk Canal Rural +1.

• Diesel - Brazil: Fuel is the other acute input market. Reports from southern Brazil included delivery delays of up to 10 daysCanal Rural, price increases of more than R$2.00-R$2.50/literCanal Rural +1, and examples of moves from R$5.60 to R$8.60/literCanal Rural +1. CNA asked for immediate temporary tax cuts on diesel Canal Rural +1, while another source argued for a higher biodiesel blend to reduce import dependence Canal Rural.

• Agricultural chemicals - U.S.: Weed-management planning for 2026 is being shaped by new dicamba rules and ESA changes @SuccessfulFarm. Reference: full recap@SuccessfulFarm.

6) Forward Outlook

• Market direction: One U.S. grain discussion said markets likely need another escalation that pushes crude back toward $120/barrel to retest recent highs Farm Journal. At the same time, other commentary said producers should treat rallies cautiously because grain fundamentals do not fully support the move and current prices may justify hedges or cash sales Farm Journal +1.

• Risk management: Volatility itself is creating planning value. One market note recommended short-term puts to establish a downside floor Market Minute LLC, and another said this volatility is creating opportunities to lock in prices Market Minute LLC.

• Input timing: Several U.S. analysts said the bigger fertilizer and diesel story may be more important for 2026/27 than for immediate 2026 planting, because many producers already have nearby fertilizer needs covered Farm Journal. The main regional exception mentioned was the Dakotas, where fertilizer coverage appears less complete Grain Markets and Other Stuff.

• Brazil weather planning: From March 12-16, heavier rain is expected in central Minas Gerais, Mato Grosso do Sul, western Mato Grosso, Amazonas, and center-north Pará, while central Bahia and Rio Grande do Sul remain drier Canal Rural. From March 17-21, rain is expected to return to Maranhão, Piauí, and central Bahia Canal Rural. One agronomic rule from the forecast is that meaningful agricultural rain generally means about 15-20 mm/day with frequency; isolated 5-6 mm events do not materially rebuild soil moisture Canal Rural.

• Seasonal watch: Brazilian forecasters said the transition toward El Niño could complicate rainfall distribution for the 2026/27 crop, with some areas turning wetter and others drier Canal Rural.