Your intelligence agent for what matters

Funding & Deals

• A six-person venture disclosed a $2M pre-seed. A CTO described a current six-person startup that raised a $2M VC-backed pre-seed. The CTO says he previously worked as an engineer and principal engineer at several startups, including one unicorn, and had founded two prior companies; the CEO is described as the more seasoned operator in this startup format. r/Entrepreneur

• FountainData is solving for GTM before launch. The technical founder says FountainData is pre-revenue and pre-MVP, with its core ML pipeline, UI/UX, and product spec already in place, and is offering a GTM co-founder 15–20% equity with a standard four-year vest and one-year cliff. The product reads App Store and Google Play reviews, semantically clusters complaints, ranks them by severity and trend velocity, generates evidence-backed tickets for Jira, Linear, or GitHub, and monitors whether complaints fall after fixes ship. The founder's wedge is closing the loop from complaint to ticket to verified fix, rather than stopping at dashboards. r/startups

Emerging Teams

• Repliva has the clearest operating traction in the batch. The founder comes from ecommerce and Shopify, and is building a native Shopify AI customer support app that ingests inbound emails, pulls order, tracking, returns, refunds, customer history, and policy context from Shopify, and drafts replies for human review. It is already running on the founder's own store doing about $80k/month in sales, with time savings cited as the main benefit. r/SaaS

• Tenet Industries is a defense team to watch. YC says Tenet is building low-cost, mass-producible defense systems, starting with strike drones, and frames the company as the F-150 for defense versus primes building Bugattis and Ferraris. The founders listed on the launch are @hpafrisk, @falkemil, and @0xfabian. @ycombinator +1

• Runik AI is testing AI-generated business systems for SMBs. The founder, who runs a small company in Chile, built the product after frustration with spreadsheets, expensive CRMs, and complex ERPs. The tool creates tables, kanban boards, calendars, dashboards, and reports from a plain-language description in about 2 minutes; after 8 months it has around 70 users, 25 industry templates, MCP connections to ChatGPT and Claude, and is still free while the founder collects feedback. r/SideProject

• AskBI is an early signal in SMB analytics copilots. The founder built a natural-language BI tool that connects to BigQuery, Snowflake, Salesforce, PostgreSQL, Google Sheets, Excel, and CSV, then returns charts plus AI-generated insights. Current product features include encrypted credential storage, in-memory processing, shareable links, and a report library. The more investable learning is around trust: schema cleaning improved NL-to-SQL results the most, wrong chart choice damaged user confidence even when the data was right, and non-technical users focused more on the AI narrative than the chart itself. r/SaaS

AI & Tech Breakthroughs

• LiteParse v2 is notable agent infrastructure. LlamaIndex says it rewrote LiteParse in Rust as native Python and Node packages, and claims it is the world's fastest PDF parser and more accurate than open-source model-free alternatives such as pymupdf and pypdf. The technical core is a grid projection algorithm that groups fragments into lines, identifies left, center, and right anchors, snaps text items to those anchors, handles flowing paragraphs separately, and renders structured text without LLMs. The parser supports 50+ document types and can be installed directly inside AI agents. @jerryjliu0 +1

• Wall-OSS-0.5 adds a useful data point in VLA training design. X-Square-Robot's report describes a 4B VLA with a 3B VLM backbone and a Mixture-of-Transformers layout trained with multimodal cross-entropy, action-token cross-entropy, and continuous flow matching from step zero. The key empirical claim is that, after the first few thousand steps, flow matching contributes only about 5% of the update signal reaching the backbone, while action-token cross-entropy drives most of the adaptation. The report also describes a residual vector-quantizer action tokenizer shaped by visual-action alignment and a distributed Muon variant, DMuon, to reduce overhead. r/deeplearning

• reverse-SynthID challenges assumptions about watermark robustness. A solo developer says he reverse-engineered Google's SynthID watermarking system using 200 sample images and built an open-source seven-stage attack pipeline. Reported results were about 16% evasion on v2 and roughly 91% removal of the watermark's spectral signature at near-zero quality loss; the GitHub repo had 4.1K stars at the time of the post. r/Futurology

Market Signals

• Open models are being framed as closing faster on closed systems. Bindu Reddy argues open-source AI will catch up rapidly because open models are getting more usage and training data, frontier improvements are becoming incremental, and models like Kimi 2.6 are already very close to SOTA. She adds that Kimi 2.6 already outperforms Flash 3.5. @bindureddy

• AI is broadening who can build software inside companies. Reddy argues software creation is moving from 10 million builders to 8 billion, and says her own sales and marketing teams have already built and use their own SaaS apps, removing the need for expensive CRM, sales, or marketing tools. @bindureddy

• The company pattern in this batch is workflow-native AI, not generic chat. The products here cluster around business system generation, Shopify-specific support drafting, SMB BI, and app-review-to-ticket automation rather than horizontal assistants. r/SideProject +3

• Trust and human control are still adoption gates. Repliva keeps humans on final customer replies, AskBI says chart choice and explanatory narrative heavily shape trust and is still working through user concerns around data uploads and SMB pricing, and Runik remains free while its founder learns what users actually need. r/SaaS +2

Worth Your Time

• Tenet YC launch — YC's launch page for the company building low-cost, mass-producible defense systems and listing its founders. @ycombinator +1

• LiteParse v2 thread — Jerry Liu's explanation of the grid projection algorithm behind LiteParse v2. @jerryjliu0

• reverse-SynthID GitHub — the repository for the seven-stage watermark attack pipeline; the post says it had more than 4.1K stars. r/Futurology

• Wall-OSS-0.5 report — the report on X-Square-Robot's 4B VLA / 3B VLM setup. Companion resources: GitHub and Hugging Face. r/deeplearning

🔥 TOP SIGNAL

• The best signal today is critique-first prompting plus explicit review loops. Lea Verou's Claude prompts start by accusing the code of being overengineered or architecturally incoherent, and steipete says the same trick works on Codex: when it says a review is "all good," tell it there is a bug and it keeps searching @LeaVerou +1. steipete also says GPT 5.5 + /goal + autoreview + crabbox moved his prompts from ~30-60 minute tasks to often 4-10 hour tasks, with much higher confidence in the result @steipete.

⚡ TRY THIS

• Force a second pass with specific critique language. Lea Verou's copyable openers: "You overengineered this, there is a simpler way", "There is a smaller delta that buys us most of the benefits", "There is a more elegant way", and "This is not architecturally coherent" @LeaVerou. steipete's Codex version is even simpler: ask for bug review, and if it says things look fine, reply "there is a bug" and make it loop again @steipete.

• Push longer jobs with /goal + autoreview + crabbox. steipete says that exact GPT 5.5 stack turned ~30-60 minute prompts into 4-10 hour tasks and raised his confidence that the work was ready @steipete. Start by inspecting the two components he shared: Autoreview skill and crabbox@steipete.

• Keep Codex running when one model taps out. Jason Zhou says the official config lets Codex use third-party models like DeepSeek, Kimi, and GLM, and that open-source models can run through the codex harness @aibuilderclub_ +1. If you hit usage limits or just prefer another model, switch the backend instead of abandoning the workflow; his setup thread is the place to copy from @aibuilderclub_.

📡 WHAT SHIPPED

• DeepSWE + Opus 4.8: now live. On default high thinking effort, it scores 6% higher than Opus 4.7 xhigh while lowering average cost per task; Theo says that matches his experience @datacurve +1.
• Claude Code field report: Theo says he's seeing frequent random tool-call errors and write failures, and suspects Opus 4.8 may be better than Claude Code makes it look @theo +1.
• Codex model switching surfaced: the official config supports DeepSeek, Kimi, and GLM, while codex harness supports open-source models @aibuilderclub_ +1. Useful if you want one interface across multiple backends.
• Emerging project worth studying: Simon Willison says Claude Opus 4.8 produced a working approach for running Python ASGI apps in Pyodide with Service Workers, with a research PR, a basic demo, and a Datasette 1.0a31 demosimonwillison.

🎬 GO DEEPER

• Short demo clip — DeepSWE's Opus 4.8 result.Watch the post. It's the quickest way to see the exact claim in context: default high thinking effort beats Opus 4.7 xhigh by 6% while lowering average cost per task @datacurve.
• Repo/spec to study — Autoreview.Autoreview skill is one of the exact pieces steipete credits in his longer-running GPT 5.5 setup. If today's theme is review before trust, start here @steipete +1.
• Project to study — Pyodide ASGI in the browser. Simon Willison's research PR and the two live demos are worth reading end-to-end because they show an agent producing a working system, not just isolated code snippets simonwillison.
• Tool worth inspecting — crabbox.crabbox is the other named component in steipete's stack for pushing tasks beyond the usual short-agent horizon @steipete +1.

Editorial take: today's edge is coming from better self-critique and model-switching workflows, not blind faith that the default agent pass is good enough.@LeaVerou +3

Most compelling recommendation

Kevin Simler’s Melting Asphalt posts

• Content type: Blog posts
• Author/creator: Kevin Simler @patrick_oshag
• Link/URL:
  • Mr. Jaynes' Wild Ride — first entry in a four-part Julian Jaynes series @patrick_oshag
  • Social Status: Down the Rabbit Hole@patrick_oshag
  • Honesty and the Human Body@patrick_oshag
• Who recommended it: Patrick O'Shaughnessy @patrick_oshag
• Key takeaway: O'Shaughnessy described Simler's work as an all-time favorite and named these three starting points @patrick_oshag
• Why it matters: This was the strongest endorsement in the set because it paired a clear personal favorite with specific places to begin @patrick_oshag

Two Bill Gurley reads on China AI commercialization

Who Has the Hardest Fist in China's LLM Ring?

• Content type: Article (Substack) @bgurley
• Author/creator: not specified in the extracted note
• Link/URL:https://crossingriver.substack.com/p/who-has-the-hardest-fist-in-chinas@bgurley
• Who recommended it: Bill Gurley @bgurley
• Key takeaway: Gurley said it is a quick summary of what is happening with LLM model companies in China: there is more VC funding available for open-weights than many think, and these companies are generating real revenue @bgurley
• Why it matters: It highlights two concrete business signals—funding and revenue generation—rather than treating the space only as a model race @bgurley

The Commercialization Moment for...

• Content type: Article @bgurley
• Author/creator: not specified in the extracted note
• Link/URL:https://crossingriver.substack.com/p/the-commercialization-moment-for@bgurley
• Who recommended it: Bill Gurley @bgurley
• Key takeaway: Gurley described it as an article summary about Chinese AI companies monetizing outside China with enterprises, and noted that it covers an AWS event in Shanghai @bgurley
• Why it matters: It extends the commercialization theme from domestic funding and revenue to enterprise adoption outside China @bgurley

One theory piece Marc Andreessen thought was worth engaging with

AI Dark Output: The Visible Cost of

• Content type: Newsletter article
• Author/creator: SemiAnalysis @pmarca
• Link/URL:https://newsletter.semianalysis.com/p/ai-dark-output-the-visible-cost-of@pmarca
• Who recommended it: Marc Andreessen @pmarca
• Key takeaway: Andreessen called it an interesting theory, while warning that inefficient and broken sectors of the economy may absorb any dark economic surplus, as he says happened during the computer revolution @pmarca
• Why it matters: The recommendation is useful because it comes with the main reservation attached, giving readers both the thesis and the pressure test @pmarca

Pattern from today

The clearest signal was Patrick O'Shaughnessy's high-conviction endorsement of Kevin Simler's writing. The rest of the day's strongest links clustered around AI economics and commercialization: Bill Gurley shared two reads on Chinese AI revenue and enterprise adoption, while Marc Andreessen highlighted a theory piece on where AI's economic gains may go @patrick_oshag +3

Top Stories

Why it matters: frontier competition is increasingly being shaped by agent performance, outside scrutiny, and the economics of data.

• GPT-5.5 widened its coding lead. It ranked #1 on DeepSWE at 70% pass@1 versus 58% for Claude Opus 4.8, while posts tracking the runs also cited roughly 2x faster execution, about half the cost, and around one-third the output tokens at $6.61 per task vs. $12.58. Multiple observers framed that token efficiency as increasingly important for longer-running agentic workflows, where wasted tokens become latency and cost. @reach_vb +2

• METR published a rare cross-lab safety review. Anthropic, Google, Meta, and OpenAI allowed METR_Evals to test their best internal models with chain-of-thought access and review non-public capabilities, alignment, and control information for its first Frontier Risk Report. The notable development is the degree of external access major labs granted for frontier-risk assessment. @METR_Evals

• Data is looking more like a strategic bottleneck. One industry discussion put frontier-lab spending on training data at $10B-$15B per lab, with strong long-horizon tasks costing up to $20,000 each and a full browser-use SAP version rumored at $500,000. At the same time, public coding benchmarks cited in the discussion remain small, including DeepSWE at 113 tasks and TerminalBench-2.0 at 89, reinforcing calls for better public evals. @MTSlive +1

Research & Innovation

Why it matters: the most useful research this cycle focused on world models, attention efficiency, and the reliability of evaluation itself.

• LeJEPA got a clearer theory for when it can learn a world model. A new paper summarized by The Turing Post says LeJEPA can linearly recover true latent variables from nonlinear observations when the latent variables are Gaussian and evolve through stationary additive-noise transitions, effectively undoing the nonlinear scramble up to a rotation. @TheTuringPost +1

• A new attention variant targets memory pressure in deep layers. The proposal replaces context-dependent value vectors with a learned table of sparse, context-free values for deep layers, reportedly beating standard attention on validation loss and benchmark scores while removing the need for a V cache in those layers and enabling table offloading with token-ID prefetching. @HeMuyu0327

• Benchmark quality is becoming a research topic of its own. Researchers auditing 168 LLM and agent benchmarks found ambiguous prompts, misaligned tests, and other flaws that can change leaderboard rankings; separately, another review argued evals should evolve through harder tasks, quality fixes, and broader coverage rather than remain static. @james_y_zou +1

Products & Launches

Why it matters: new releases are converging on video generation, easier evaluation, and more autonomous developer tooling.

• Grok-Imagine-Video-1.5-Preview moved to the top of the image-to-video leaderboard. The 720p model ranked #1 in the Image-to-Video Arena and was described as a +52 point improvement over the prior Grok-Imagine-Video release, ahead of Seedance-2.0 and HappyHorse. @arena

• PrimeIntellect launched Hosted Evaluations. The platform is designed to absorb the infrastructure overhead of evals, including harnesses, sandboxes, compute hours, and parallel runs, and it includes a rollouts viewer for creating and analyzing evaluation data. @PrimeIntellect +1

• Developer copilots are becoming more orchestration-heavy. VS Code now surfaces Anthropic, OpenAI, and Gemini models with BYOK and multiple harness choices, while the GitHub Copilot app can open its own sessions, run multiple agents in parallel after code review, and report progress back to the user. @pierceboggan +2

Industry Moves

Why it matters: large buyers and platform companies are moving from generic copilots toward custom stacks, tighter distribution, and larger infrastructure bets.

• Kirkland & Ellis is earmarking $500M for its own AI platform rather than relying on tools available to rivals, a strong signal that some large enterprises want proprietary systems instead of shared vendor layers. @Techmeme

• Microsoft is reportedly building a Copilot “super app.” The backdrop is weak paid penetration: under 4.5% of 450 million Microsoft 365 seats reportedly pay for Copilot, or roughly 20 million users, while GitHub Copilot has 4.7 million paid users and faces pressure from Cursor and Claude Code. @kimmonismus +1

• OpenAI’s infrastructure ambitions keep expanding. One discussion this week described plans to scale from roughly 2GW to 30GW of compute capacity by 2030 using a heterogeneous compute strategy while working through bottlenecks. @apoorv03

Quick Takes

Why it matters: a few smaller updates still sharpened the picture on deployment speed, inference efficiency, and open safety work.

• Salesforce said Claude Code helped finish a migration estimated at 230 days in 13 days, while passing 100% of test cases. @stablequan
• vLLM v0.22.0 shipped with 459 commits from 230 contributors and a reported 28.9% end-to-end latency improvement on its batch-invariant Cutlass FP8 path. @vllm_project +1
• The AI Safety Institute is releasing evals, datasets, and models openly on Hugging Face for external scrutiny and reuse. @ClementDelangue
• Qwen 3.6 27B was shown at 87 tokens/s on a consumer AMD GPU using UnslothAI Dynamic Quants. @danielhanchen +1

What stood out

Today’s clearest pattern sat around the stack around models rather than inside a single flagship model launch: more openness around safety work, more concrete security tooling for agents, and a sharper debate over whether durable advantage comes from frontier scale or from the systems built around models @ClementDelangue +3.

AI Safety Institute is reportedly putting eval assets in the open

According to Hugging Face CEO Clement Delangue, the AI Safety Institute is releasing its evals, datasets, and models openly on Hugging Face, so researchers can scrutinize, reproduce, and build on them @ClementDelangue.

Why it matters: For professionals trying to separate safety claims from marketing, openly accessible artifacts make outside inspection and reuse much easier @ClementDelangue.

NVIDIA launched a security scanner for AI agent skills

NVIDIA launched SkillSpector, a security scanner for AI agent skills @bibryam. The tool is described as “Semgrep + antivirus” for agent skills and includes 64 checks across 16 categories, covering prompt injection, credential theft, supply-chain vulnerabilities, AST and taint-flow analysis, MCP security checks, optional LLM evaluation, and SARIF output for CI/CD @bibryam.

Why it matters: This is a useful signal that agent deployment is increasingly being treated like an application security and software supply-chain problem, not just a model-quality problem @bibryam.

xAI is pushing Grok Build beyond an early CLI

A rollout summary amplified by Elon Musk described Grok Build v0.2.11 as moving quickly from an early CLI into a more serious agentic coding environment @XFreeze +1. The update list includes integrated X and web search, export and agent commands, a read-file viewer, Always-approve mode, broader platform support, shared subagent backend services, improved context compaction, 30fps terminal video, multi-image support, and faster model switching @XFreeze.

Why it matters: The release list suggests xAI is investing in persistent, tool-using developer workflows rather than a simple terminal chatbot @XFreeze.

The frontier-vs-open debate is getting more economic

Martin Casado argued that frontier labs are focusing on “autocatalytic” processes in which models help improve models—for example through GPU kernel creation and data cleaning—and that this should improve economies of scale @martin_casado. He also argued there is pricing power at the frontier, while open models face three structural challenges: pre-training is not saturated, current-generation training runs cost $2-4B, and distillation is getting harder as access to the strongest models tightens @martin_casado +1.

Nathan Lambert framed the same split more simply: closed models may remain slightly smarter, while open models may remain cheaper @natolambert. Casado added that lagging by a few months may not matter if most value accrues to whoever stays on the frontier, and he estimated the largest frontier training runs at roughly 100,000 GPUs for six months @martin_casado +1.

Why it matters: The argument here is moving away from ideology about “open vs. closed” and toward a harder commercial question: how much value buyers place on marginal intelligence gains versus lower cost @natolambert +1.

Harnesses are becoming part of the model story

Lambert said harnesses can make models “far more independent and thorough,” pointing to a gap between weak search behavior in the Claude app and stronger task execution in Claude Code, such as pulling exact figures from papers into slide decks @natolambert. In a separate interview, Gary Marcus argued that neuro-symbolic systems are “winning in practice,” because symbolic tools and deterministic code wrapped around LLMs—such as regex, loops, and Python—are doing work that pure scaling alone did not solve SparX by Mukesh Bansal.

Why it matters: Different camps in the AI debate are emphasizing the same operational lesson: orchestration, tools, and surrounding code can materially change what a model can do in practice @natolambert +1.

Big Ideas

• The PM role is splitting into daily shippers and quarterly planners. Aakash Gupta argues the split exists because AI can cut prototyping from six weeks to 45 minutes, collapsing the old PM → design → engineering relay race Aakash Gupta. In teams using agent-assisted triage, the bottleneck is no longer surfacing issues; it is deciding which issues matter enough to ship Aakash Gupta.

Why it matters: cadence is now more a function of workflow design than of raw build capacity. How to apply: redesign PM time around rapid judgment, not just document production Aakash Gupta.

• Reusable guardrails are becoming the scaling mechanism for AI-assisted product work. One team reported shipping a million-line app with zero human-typed code by requiring every AI mistake to be solved with a guardrail and rerun, rather than a manual fix Aakash Gupta. Why it matters: one-off heroics solve today's task; guardrails improve tomorrow's tasks too. How to apply: treat repeat AI mistakes as missing rules, tests, or constraints—not as cleanup work Aakash Gupta.

Tactical Playbook

1. Set up a self-improving triage loop.

   • Have an agent pull discussions, issues, and releases, then score each item by priority Aakash Gupta.
   • Make it grade its own accuracy and absorb corrections overnight Aakash Gupta.
   • Keep the PM focused on scoring drift and on refining what "good" looks like when priorities are off Aakash Gupta.

   Why it matters: this is how teams get from issue intake to same-day shipping Aakash Gupta. How to apply: start with one feedback source and one rubric; correct mis-ranked items explicitly so the eval improves over time Aakash Gupta.

2. Fix AI mistakes at the system level.

   • When the agent fails, add a guardrail for that class of error Aakash Gupta.
   • Rerun the agent instead of patching the output by hand Aakash Gupta.

   Why it matters: it feels slower initially, but the improvement compounds across future tasks Aakash Gupta. How to apply: keep a running list of repeated failures and turn each into a reusable check or rule Aakash Gupta.

Case Studies & Lessons

• Arize: a working PM agent in under 45 minutes. In a live build, Arize's CPO started from an empty directory and used four plain-English terminal commands to create a functioning PM agent Aakash Gupta. Its first blind spot was clear: it over-weighted feature requests relative to production bugs Aakash Gupta. After human correction, the eval improved and so did later outputs Aakash Gupta. Lesson: the compounding value is in refining judgment criteria, not just generating backlog summaries.

• Guardrails widened who could ship. In Ryan Lopopolo's workflow, banning manual typing forced the team to encode reusable safeguards instead of making local fixes Aakash Gupta. Reported outcomes included a PM with no engineering background shipping a merged pull request in a week and designers prototyping full UI features Aakash Gupta. Lesson: AI-assisted teams can broaden execution beyond engineers if they standardize the rules.

Career Corner

• Interview prep is broader than frameworks. Across PM communities, the recurring prep areas were personal narrative, achievement and failure stories, motivation for the company and role, favorite-product critique, product cases and guesstimates, AI use cases, industry trends, and app reviews r/prodmgmt. One poster's warning: candidates often over-prepare frameworks and under-prepare stories, market knowledge, and company-specific context r/prodmgmt. How to apply: build a short bank of crisp stories and product opinions before your next interview loop.

• To get AI-product ready, build something. In a thread from a traditional PM moving into AI, the strongest advice was to build a personal AI project, with commenters saying recent interviews were directly asking for personal AI experience r/ProductManagement +1. Use foundational material such as Andrew Ng's ML course or Hugging Face docs to understand what is possible before you start r/ProductManagement. How to apply: let one shipped side project become your proof of learning; use courses as support, not as the main signal.

Tools & Resources

• FountainData is worth watching as a feedback-to-action workflow. Its pitch: read every App Store and Google Play review, cluster the complaints that matter, rank them by severity and trend velocity, detect churn signals, send evidence-backed tickets to Jira, Linear, or GitHub, and monitor whether complaints actually fall after a fix ships r/startups.

• For AI foundations, pair building with reading. The most concrete resource suggestions in this set were Andrew Ng's ML course and Hugging Face documentation, used alongside hands-on experimentation r/ProductManagement.