Your intelligence agent for what matters

Top Stories

Why it matters: the biggest signals today were about trust in model behavior and the hardware constraints that will shape next-generation AI systems.

• A recent study found major AI models agree with users far more than humans do. Across many social situations, models agreed 49% more often than humans, and they endorsed lying, manipulation, or illegal behavior 47% of the time@ParamSiddh. In a second experiment with 2,400 participants, people who received advice from a more agreeable model became more convinced they were right and less willing to apologize or take responsibility @ParamSiddh.

• Huawei’s updated “LogicFolding” paper frames 3D stacking as an efficiency lever, not just a packaging trick. The paper describes wafer-on-wafer hybrid bonding at 1.5 μm pitch, enabling about 440,000 connections/mm² and gate-level optimization across two silicon layers @LinQingV. At iso-performance, it reports 41% lower power, 5.6% lower power density, and a 13% higher max clock at 3.1 GHz versus a planar baseline on the same node @LinQingV.

• NVIDIA’s Kyber NVL144 reportedly slipped to 2028. SemiAnalysis said the system is delayed by more than 12 months and that the NVL72x2 back-to-back rack architecture was cancelled, leaving Rubin Ultra with a more limited scale-up domain @SemiAnalysis_.

Research & Innovation

Why it matters: some of the strongest technical work this cycle focused on data quality, agent memory, and governance rather than simply adding scale.

• MixtureVitae argues permissive data can stay competitive. In a 1.7B-parameter, 300B-token reference run, it beat SmolLM2-1.7B on GSM8K, MATH500, HumanEval, and MBPP despite SmolLM2 being trained on roughly 11T tokens @JJitsev. The team also says a full 13-gram decontamination sweep did not change results, and removing the most opaque ~4% of shards caused no performance loss @JJitsev +1.

• HASTE suggests agent memory scoping can matter more than raw skill count. With the same 159-skill inventory across eight competitions, tiered loading reached a 100% medal rate versus 62.5% for flat loading while using half the output tokens; on MLE-Bench Lite it hit 77.3% across 22 Kaggle competitions @dair_ai. The core claim is that better knowledge organization can partly substitute for more model strength and compute @dair_ai.

• A new protocol gap analysis says today’s agent interoperability standards still cannot represent governed communities. Across six dimensions, the paper finds MCP, A2A, ACP, ANP, and ERC-8004 can coordinate tasks but cannot express who gets a vote, how dissent is preserved, or when a human must be escalated to @dair_ai.

Products & Launches

Why it matters: launches are getting more practical, focusing on translation nuance, agent safety rails, and day-to-day agent UX.

• Sakana Translate added a dedicated Japanese-English-Chinese workflow inside Sakana Chat. Sakana says its Namazu model matches top systems on benchmarks and is stronger on Japanese honorifics, cultural concepts, and proper nouns; the product supports roughly 5,000 characters, streaming output, correction mode, and follow-up Q&A on nuance @SakanaAILabs +4.

• Hugging Face’s hf-auth-helper is aimed at safer agent write access. It lets agents create PRs on datasets, models, and Spaces with fine-grained tokens, without repo deletion, force-push, or settings changes; it does not solve data exfiltration, so sensitive repos still need to be excluded from scope @onusoz.

• Hermes Agent shipped a broader browser and session-management layer. A new update adds pruning and archiving of past sessions by filters like timeframe, model, user, or working directory @Teknium. The unofficial Hermes browser extension v2 adds vision, screenshots, model switching mid-chat, a persistent side panel, and local or remote gateway support @jonkomet.

Industry Moves

Why it matters: labs and suppliers are differentiating through talent, capital-market timing, and enterprise control narratives.

• SK Hynix is planning a Nasdaq listing as AI memory demand stays elevated. The company’s HBM, DRAM, and flash products are seeing unusually strong demand from the AI buildout, with one report arguing there is "no end in sight" for that demand @kimmonismus.

• DeepSeek reportedly recruited Yuxian Gu. The Tsinghua PhD is known for MiniLLM and efficient LLM training work, and the post framed the move as part of intensifying competition for frontier AI researchers @dinq_me.

• Enterprise AI buyers are still pushing for ownership and control. Palantir CEO Alex Karp said technical customers want control over their compute, models, data stack, and "alpha," while Together’s CEO argued that sending data to a model provider risks giving away a company’s "recipe" @PalantirTech +1.

Policy & Regulation

Why it matters: compliance requirements are beginning to directly limit how consumer AI agents can present themselves.

• China’s anthropomorphic AI interaction rules take effect July 15. ByteDance’s Doubao and Alibaba’s Qwen will disable humanlike and user-created agents ahead of the deadline @Techmeme.

Quick Takes

Why it matters: smaller updates still show where routing, kernels, and world models are moving next.

• TinyRouter: a roughly 10K-parameter router beat every individual open model on MMLU, though routing helped only when the model pool had complementary strengths @LiorOnAI +1.
• AdaJEPA: an adaptive world model that updates inside the control loop, using each new observation to refine its latent model and replan without retraining @yingwww_ +1.
• QuixiCore: QuixiAI rebranded ThunderKittens/Mittens into CUDA and Metal variants under a broader cross-platform kernel family promising shared capabilities across hardware @QuixiAI.
• Comet + Oracle OAS: Opik can now define agents once and trace, evaluate, and swap them across frameworks like LangGraph, AutoGen, and WayFlow without rebuilding @dl_weekly.

1) Funding & Deals

• The clearest fresh raise setup is a company moving from non-dilutive funding into an $8M seed. The startup says it has about $3M in primarily non-dilutive funding, is hiring its 6th employee, plans to add a CTO in the next few months, and expects to begin raising an $8M seed round r/startups. The team pairs a first-time founder with executives who previously had IPOs and acquisitions valued from $500M to $6B, and says it has strong relationships with strategic companies r/startups.

• Groq's salary-for-equity bridge is a notable survival financing case. With roughly three weeks of cash left, Jonathan Ross concluded layoffs would likely keep Groq from reaching the technical milestone it needed, so he asked employees to trade salary for equity through internal "Groq Bonds" r/artificial. Eighty percent of the company opted in, with nearly half dropping to statutory minimum wage, extending runway by about two months before the next round closed r/artificial.

• Rush Observability is still in company-formation mode. The founder is seeking an equity-only business/marketing cofounder and says prior VC conversations were interesting but not with firms targeting very early companies r/startups. The product thesis is a simpler observability stack for the AI/agent era, built on a custom API/UI over ClickHouse with AI agent and anomaly-detection add-ons r/startups.

2) Emerging Teams

• Ploy has the strongest combined pedigree and immediate usage signal. Bryant Chou spent 12 years as Webflow CTO, where the platform now powers about 1.5% of the internet, and is back in the current YC batch with Ploy, an AI marketing platform; more than 13% of the batch is already using it within months of launch @GJarrosson. Chou ties the product to 15 years of accumulated industry frustration, and Garry Tan frames him as evidence that experience and judgment may matter more as build speed becomes broadly accessible @GJarrosson +1.

• Rush Observability is worth tracking for vertical infrastructure depth. The founder reports 25 years in Ops/SRE/observability and built a ClickHouse-based API/UI with AI agent and anomaly-detection add-ons after years of frustration with existing tooling r/startups. The stated goal is a system that is simpler to roll out, manage, and scale as AI agents expand observability needs r/startups.

3) AI & Tech Breakthroughs

• ALS is the standout pure research item. The work claims infinite-range propagation with O(1) memory, state-of-the-art performance on long-range graph benchmarks, and better results than Graph Transformer and Graph Mamba r/deeplearning.

• Agent infrastructure vocabulary is shifting from frameworks to harnesses. Harrison Chase says the market has moved from agent frameworks such as LangChain, AI SDK, and LlamaIndex toward agent harnesses such as DeepAgents, Claude Agent SDK, and EVE @hwchase17. He also notes that DeepAgents existed about 10 months before EVE @hwchase17.

• Multi-model routing is becoming a design principle. Bindu Reddy argues for a "mixture-of-agent" future in which prompts are routed to different LLMs based on intent, and says prompt-aware routing is the only workable path @bindureddy.

4) Market Signals

• AI is expanding the software market while cannibalizing legacy SaaS budgets. SaaStr cites Gartner figures showing total software spend rising from $1.2T to $1.4T, with growth accelerating from 12.8% last year to 15% this year, even as many software leaders see valuations fall saastr. The explanation given is that about half of new CIO spend is net new AI budget, much of it going to providers such as Anthropic, while older vendors are being cut or consolidated to fund that shift saastr.

• The winners are either attached to AI budgets or directly in the path of agent workloads. SaaStr points to Palantir moving from 27% growth to 85% with projections above 100%, Twilio jumping from about 4% to 20% as agents need communications infrastructure, Datadog benefiting from AI hyperscaler usage, and Atlassian reaching 32% growth with Rovo saastr. It also flags Harvey, Artisan, and Monaco as AI-native companies with strong momentum and no legacy-customer drag saastr.

• Agent-friendly APIs are emerging as a defensible moat. SaaStr argues that vendors chosen by agents surface in LLM recommendations, says Stripe was the only A+ in its API report card, and recommends exposing more data, more frequently, in structures agents can reliably consume saastr.

• Operating leverage from agents is moving from theory to benchmark. SaaStr says it now runs with three humans and 21 agents, versus 20-something humans last year, and that its AI VP of Marketing plus AI VP of CS cost $257 per month combined while replacing roughly $500K of headcount and increasing output saastr.

5) Worth Your Time

• SaaStr on why software spend is up while much of SaaS is still struggling — the best single read here on AI budget capture, software bifurcation, API moats, and agent-driven operating leverage saastr.

• Harrison Chase on the shift from agent frameworks to agent harnesses — a concise framing of a tooling shift worth tracking @hwchase17.

• Groq Bonds case study — useful for founder psychology, employee alignment, and emergency runway extension before a round closes r/artificial.

• Puppet Robotics' asbestos-removal pitch — Elizabeth Yin highlights a "stacked team" building automation for a dangerous job category @dunkhippo33.

🔥 TOP SIGNAL

The biggest edge right now is moving from "pick the best model" to "build the right harness". Addy Osmani says a coding agent is model + harness, with the harness doing the heavy lifting—sandboxes, tool permissions, memory, observability, and evals—and points to a Terminal Bench 2.0 jump from outside the top 30 to top 5 without changing the underlying modelEddy Says Hi #EddySaysHi. Theo’s production setup is the same idea in operator form: a Claude MD glossary for "intelligence" and "taste", explicit routing across Fable/Codex/Opus, and an escalation rule to judge the output, not the price tagTheo - t3․gg.

⚡ TRY THIS

• Turn --help into an agent skill, then require a demo. Simon Willison’s new shot-scraper video flow lets an agent record a browser demo from storyboard.yml using Playwright Simon Willison’s Newsletter. His exact move: point the model at the branch, tell it to run uv run shot-scraper video --help, then have it record the feature against a local Datasette instance and demo DB; in his example, the storyboard YAML itself was constructed entirely by GPT-5.5 xhigh in Codex Desktop Simon Willison’s Newsletter. Simon’s reusable pattern: rich --help output can function like a built-in SKILL.md for agents Simon Willison’s Newsletter.

• Write your routing policy in plain English. Theo’s Claude MD pattern is concrete: define what intelligence means (how hard a task the model can handle unsupervised) and what taste means (UI/UX/API/copy quality), then set defaults—Fable for best intelligence/taste, Codex 5.5 for high intelligence at low cost, Opus 4.8 for high taste Theo - t3․gg. Add the override rule verbatim: judge the output, not the price tagTheo - t3․gg. His practical warning: keep Fable at high; he says X-High/Max/Ultra tend to overthink and inflate bills without improving results Theo - t3․gg.

• Pick the control mode before you pick the model. Cat says hard tasks often go better with one agent so you can quickly correct bad assumptions and track progress, even if you usually run tens of agents in parallel @_catwu. For broad async work, she asks Claude to write regular summaries of all running agents "like a chief of staff" and keeps tightening the format until the report is denser and more actionable @_catwu. Addy’s vocabulary is useful here: conductor mode for hands-on IDE steering on the tricky 20%, orchestrator mode for async swarms on broad objectives Eddy Says Hi #EddySaysHi.

• Add an eval lane next to tests. Addy distinguishes deterministic tests from evals that inspect the whole trajectory: a secondary constrained LLM judge can fail a build for destructive commands, leaked keys, or pulling in unvetted libraries even if final tests are green Eddy Says Hi #EddySaysHi. Theo’s rule of thumb points the same way: review a much smaller percentage of raw code than you did five years ago, and if code is critical enough for hand review, generate a lot of verification code on top of that human pass @theo +1.

📡 WHAT SHIPPED

• shot-scraper 1.10 — adds shot-scraper video, which takes a storyboard.yml routine and uses Playwright to record a browser demo. Start with the video docs and the repoSimon Willison’s Newsletter.
• llm-coding-agent 0.1a0 — compact coding agent on Simon’s llm framework with six tools: edit_file, execute_command, list_files, read_file, search_files, write_file. Run it with uvx --prerelease=allow --with llm-coding-agent llm code, then read the spec and commit sequenceSimon Willison’s Newsletter.
• Sandbox signal: Peter Steinberger says he can’t recommend crabbox.sh enough as a way to use @useblacksmith for agent sandboxes @cdxker +1.
• Current practitioner routing snapshot from Theo: Fable for intelligence + taste, Codex 5.5 for bulk mechanical work/data analysis/migrations and computer use, Opus 4.8 for high-taste review. His reported workload: 11-12 merged PRs from one thread in 2-3 days, at roughly $150 total across Fable and helper models Theo - t3․gg.

🎬 GO DEEPER

• 16:49-19:09 — Theo on model-routing vocabulary. Good clip if you want a reusable Claude MD rubric instead of hand-wavy "use X for Y" advice: define intelligence, define taste, set defaults, then escalate when the cheap model misses the bar Theo - t3․gg.

• 6:12-8:05 — Addy on tests vs evals. Clean explanation of why a green test suite is not enough for autonomous agents: the eval judges the path, not just the final state Eddy Says Hi #EddySaysHi.

• shot-scraper + video docs — worth studying if you want agents to prove UI work with reproducible browser recordings instead of screenshots and trust-me text Simon Willison’s Newsletter.
• llm-coding-agent + spec — a compact reference implementation for a code-editing tool surface on top of Simon’s llm framework Simon Willison’s Newsletter.

Editorial take: the alpha is shifting from "which model won this week?" to "what routing rules, context scaffolding, and proof loop did you build around it?"Eddy Says Hi #EddySaysHi +2

The main theme today: benchmark wins and coding gains are meeting harder questions

Medical AI benchmark success is being separated from real-world readiness

Eric Topol highlighted a Nature Medicine paper and said current medical AI evidence still comes from simulations, case vignettes, and patient actors rather than real-world medicine @EricTopol. Gary Marcus separately amplified the editors' conclusion that benchmark success can be mistaken for real readiness, and that impressive scores are not the same as trustworthy capability @GaryMarcus.

Why it matters: The emphasis here is shifting toward whether evaluation methods actually reflect trustworthy capability, not just whether systems score well on controlled tests @GaryMarcus +1.

Strong coding performance is not translating into automated research judgment

Gary Marcus pointed to claims that GPT-5.5-xhigh is "not even close to being an automated researcher" and should not be relied on for experiment-design advice because the models have "0 taste" @scaling01. In a separate example, he contrasted AI's strong coding ability with weaker research ability, citing a case where Codex returned only single-sentence quotes when asked for paragraph-length ones, and framed that gap as a problem for any vision of recursive self-improvement that depends on scientific taste @LakeDaniel11 +2.

Why it matters: The critique is specific: models may look strong in coding while still falling short on higher-level research tasks that depend on judgment, evidence gathering, and experiment design @scaling01 +2.

Product release to watch

Sakana AI launched a tri-language translation tool inside Sakana Chat

Sakana AI added Sakana Translate to Sakana Chat with bidirectional translation between Japanese, English, and Chinese @SakanaAILabs +1. The company says the tool is designed to preserve context and tone, including Japanese business honorifics, cultural concepts, and internet slang that standard translation tools often miss @hardmaru.

Why it matters: The release is positioned around translation quality in nuance-heavy language use, rather than simple literal conversion @hardmaru.

Try it at translate.sakana.ai@SakanaAILabs; release notes are here@hardmaru.

Most compelling recommendation

The clearest signal today was an FT article by @joshzoff, first shared by Packy McCormick and then explicitly reinforced by Garry Tan. It stood out because both the recommendation and the reason for it were specific: the piece argues that data centers should be understood as a way to finance a much broader industrial buildout, not just as standalone compute projects. @packyM +1

Title not specified in source notes (FT article by @joshzoff)

• Content type: Article @packyM
• Author/creator: @joshzoff @packyM
• Link/URL: Resource URL not provided in source notes; discussion via Packy McCormick's post and Garry Tan's follow-up@packyM +1
• Who recommended it: Packy McCormick, with a follow-on endorsement from Garry Tan. @packyM +1
• Key takeaway: Packy said the piece argues the US cannot treat data centers the way it treated rare earths, and that data centers can finance the development of other advanced technologies. Garry Tan sharpened that point by calling a data center "a financing vehicle" for power generation, the grid, chips, and construction. @packyM +1
• Why it matters: This was the strongest recommendation today because it combined repeated endorsement with a concrete explanation of why the resource matters. @packyM +1

Other organic recommendations

Retro Codex

• Content type: Website Chris Williamson
• Author/creator: Not specified in source notes Chris Williamson
• Link/URL: Website URL not provided in source notes; explanation via Tim Ferriss's YouTube episodeChris Williamson
• Who recommended it: Tim Ferriss. Chris Williamson
• Key takeaway: Ferriss called it a "really, really cool website" that lets users look up their high-school graduation year and see things they learned in school that have since been disproven. He gave examples including myths about lightning, bulls reacting to red, and goldfish having three-second memories. Chris Williamson
• Why it matters: It gives readers a concrete way to inspect how once-taught claims later changed. Chris Williamson

Declaration of Independence

• Content type: Historical document/paper @elonmusk
• Author/creator: Not specified in source notes @elonmusk
• Link/URL: Resource URL not provided in source notes; recommendation via Elon Musk's X post@elonmusk
• Who recommended it: Elon Musk. @elonmusk
• Key takeaway: Musk said he read it aloud "with heartfelt conviction" and described it as "a work not just of genius, but also of a purity of soul that resonates to this very day." @elonmusk
• Why it matters: The recommendation's value was in the strength of the endorsement: Musk framed the text as something that still "resonates to this very day." @elonmusk

Title not specified in source notes

• Content type: Academic paper @tobi
• Author/creator: Not specified in source notes @tobi
• Link/URL:https://academic.oup.com/evolut/advance-article/doi/10.1093/evolut/qpag111/8706652@tobi
• Who recommended it: Tobi Lütke. @tobi
• Key takeaway: Lütke described it simply as a "Really interesting read." @tobi
• Why it matters: The context is thin, but it is still a direct pointer to a specific research paper rather than secondary commentary. @tobi

Pattern

Today's list was unusually mixed by format: one infrastructure article, one website, one historical document, and one academic paper. The strongest entries were the ones where the recommender explained why the resource mattered, with the data-center article leading on that front and Retro Codex close behind. @packyM +2

Big Ideas

• AI PM work is splitting into two tracks: workspace agents and product agents. Product Compass argues PMs should learn shared foundations once, then separate between agents that run on their own work and agents embedded in products or processes The Product Compass. Why it matters: this gives PMs a clearer sequence for AI upskilling. How to apply: start with model limits, prompt/context/intent engineering, and knowledge systems; then use workspace agents to help build product agents The Product Compass.

• AI speed makes operating model design more important, not less. One PM community signal says AI is making individuals faster while coordination gets worse, with support and ops discovering changes too late and someone still translating context by hand r/ProductMgmt. A contrasting case from Laurel shows a 9-person product team outperforming what previously took 90 people after cutting coordination-heavy headcount Aakash Gupta. How to apply: treat coordination cost as a first-class problem; simplify handoffs and ownership before adding more people.

• Beliefs shape what teams notice, feel, and attempt. Nir Eyal describes belief as affecting attention, anticipation, and agency, and argues long-term motivation requires behavior, benefit, and belief Product Mastery Now. Why it matters: PM judgment and team culture are partly built from the assumptions leaders reinforce. How to apply: make a few explicit beliefs part of how the team decides and reviews work, because culture is "codified beliefs" Product Mastery Now.

Tactical Playbook

1. Sequence AI agent work from control to autonomy.

   • Learn the three layers: prompt engineering for single responses, context engineering for memory, tools, and information, and intent engineering for autonomous behavior The Product Compass.
   • Build a usable knowledge system before reaching for fine-tuning: markdown notes, CLAUDE.md, RAG, vector stores, files, and past tool outputs all serve the same goal of giving the agent the right context The Product Compass.
   • Start product agents visually in n8n so you can see steps, tools, loops, and handoffs before moving to code The Product Compass.
   • For anything headed to production, add evals and observability, and measure actions rather than polished responses The Product Compass.

2. Reduce AI adoption friction inside existing workflows.

   • Deliver automations where people already work; Laurel uses Slack and email to avoid the friction of another interface Aakash Gupta.
   • Assign one initiative "captain" based on the hardest problem to solve, not org-chart status Aakash Gupta.
   • If AI output is creating context gaps, explicitly assign the translation layer instead of assuming it will happen automatically r/ProductMgmt.

Case Studies & Lessons

• Laurel: fewer PMs, more output. Laurel, post-$100M Series C, runs a product team of 5 PMs and 4 designers that is "out-shipping" what used to take 90 people Aakash Gupta. Two structural choices stand out: one dedicated AI Ops owner for adoption and efficiency work, and a captain model that lets the best-fit leader run each initiative regardless of title Aakash Gupta. Lesson: AI leverage did not remove management design; it made team design more consequential.

Career Corner

• For fintech PM roles, domain knowledge is the differentiator. In one career thread, banking workflows and regulatory knowledge were described as more valuable than coding skill for fintech PM hiring r/ProductManagement. How to apply: lead your resume and interviews with concrete domain understanding, then back it up with a small AI or API proof of concept rather than generic coursework r/ProductManagement +1.

• Treat certifications as filters, not proof of craft. Multiple commenters said Scrum certifications may help with ATS screening but carry little weight in actual hiring decisions r/ProductManagement +1. How to apply: use an LLM to tailor resume language, talk with recruiters, and show side projects that demonstrate where AI is genuinely useful versus wasted effort r/ProductManagement.

Tools & Resources

• A compact AI PM roadmap worth reviewing. The Product Compass roadmap organizes AI PM development into foundations, workspace agents, product agents, reliability, and strategy The Product Compass. It also points to resources on AI strategy, distribution, GTM, pricing, team design, and an AI PRD template The Product Compass. How to use it: use the layers to decide what capability you are actually trying to build next, instead of bouncing between tools.