What key people are thinking: founder interviews, researcher debates and investor calls.
Dave Lee criticized Meta for spending on AI like a cloud giant, with capex reaching up to $145 billion. The post says Meta lacks Amazon- or Google-style cloud sales growth from AI. The key issue is capex without matching visible revenue.
Why it matters: HKR-H/K/R all pass: a sharp Meta capex mismatch, a $145B figure, and infra-spend anxiety. It is commentary rather than a major release, so it sits at the 72 threshold.
A Reddit user tested small local and free-tier cloud models for weeks on multi-file coding tasks. Sub-7B structured output was unreliable; failures included markdown fences, wrong-file edits, and read/write misclassification, with post-processing and validation as fixes.
Why it matters: HKR-H/K/R pass: the post names real local coding-agent failure points, a sub-7B threshold, four failure classes, and mitigations. Reddit single-post scope keeps it below release-tier news, so 75.
Terence Tao says math is shifting from proof scarcity to proof abundance, with 20-plus AI solutions pending assessment on an Erdős problems GitHub page. The post says GPT-5.4 Pro generated an Erdős #1196 approach in 80 minutes, and Tao verified the core within 24 hours. The key issue is verification and digestion workflow, not raw proof count.
Why it matters: All HKR axes pass: Tao plus GitHub proof backlog gives HKR-H, while 20+ pending AI solutions and an 80-minute GPT-5.4 Pro claim give HKR-K. This is not a model release, so it stays below 85.
Google outpaced Big Tech rivals as AI spending plans rose to $725bn. The snippet says Meta fell on higher capex, while Alphabet cloud grew faster than Amazon and Microsoft. The post does not disclose the spending split or timeframe.
Why it matters: HKR-H/K/R all pass: the FT gives a $725bn AI capex race and Alphabet cloud lead. Missing company split, time frame, and model-level spend keep it in the lower 78–84 band.
Latent Space argues inference demand has hit an inflection point, citing its Apr 28-29, 2026 AINews roundup. Jensen Huang is quoted saying per-task compute rose about 10,000x in two years, with usage up about 100x. The key watchpoints are CPU sandboxes, agent harnesses, and split inference workloads.
Why it matters: HKR-H/K/R all pass, but this is a Latent Space AINews roundup and trend read, not a model launch or major product release. It fits the upper featured-threshold band for insightful commentary.
OpenAI posted about goblin outputs in GPT-5; only an RSS snippet is available. The snippet names timeline, root cause, and fixes, but does not disclose mechanisms or conditions. The key issue is how personality-driven quirks enter model behavior.
Why it matters: HKR-H and HKR-R pass: OpenAI is addressing odd GPT-5 behavior with clear talk value. HKR-K fails because the RSS text lacks reproduction conditions, timeline, and fix details, so it stays in the low featured band.
Dwarkesh interviewed Reiner Pope in a 1-session blackboard lecture on LLM training and serving. The post lists 7 timestamps on batch size, MoE rack layout, pipeline parallelism, KV cache, and API pricing. The key mechanism is cost: without batching, serving economics can be 1,000x worse.
Why it matters: HKR-H/K/R all pass: the 1000x batching cost hook, concrete serving mechanics, and inference-cost resonance are strong. This is a high-quality tutorial, not a same-day industry event, so it stays at 77.
The Verge discusses Claude Mythos and AI bug finding, citing DARPA AIxCC scans over 54 million code lines. Teams found most seeded flaws plus over a dozen unseeded bugs; the RSS snippet does not disclose Mythos benchmarks, pricing, or access terms.
Why it matters: HKR-H/K/R all pass: the hook is strong, DARPA AIxCC supplies concrete numbers, and the security angle resonates. No Claude Mythos benchmark, pricing, or access terms are disclosed, so it stays in the featured-threshold band.
WSJ says OpenAI missed its own new-user and sales goals. The RSS snippet cites internal concern over AI infrastructure spending. The post does not disclose targets, gaps, timing, or spend size.
Why it matters: HKR-H/R are strong because OpenAI growth missed its plan and infra spend is the nerve. HKR-K is thin: WSJ reports the miss, but target size, gap, period, and spend are undisclosed.
Applied Intuition’s founders reviewed a 10-year physical AI path, with the company valued at $15B. The post cites 30+ products, 18 of the top 20 non-Chinese automakers as customers, and L4 driverless trucks in Japan. The key constraint is onboard deployment: millisecond latency, low power, small models, and safety validation.
Why it matters: HKR-H/K/R all pass: the piece ties a major Physical AI company to real AV deployment with customer, valuation, and L4 details. No new model or major launch is disclosed, so it stays in the 78–84 band.
Denis Stetskov compares Western defense production gaps with AI coding, citing Stinger orders placed in 2022 for 2026 delivery. He says Europe’s 1M-shell target was 9 months late, and METR found senior developers 19% slower with AI. The key risk is the junior-engineer pipeline, not code generation speed.
Why it matters: HKR-H/K/R all pass: the analogy is clickable, the post gives concrete defense and METR numbers, and the junior-engineer pipeline resonates. X translation/commentary limits authority, so it sits just above the featured threshold.
Dwarkesh lists open AI questions, including that five hyperscalers own over 70% of global AI compute. He asks about coding agents, KV cache costs, merging training with inference, and online learning; the post gives questions, not experimental answers.
Why it matters: HKR-H/K/R all pass: Dwarkesh adds a concrete compute-concentration claim and practitioner-relevant questions. No experiment, release, or policy change, so it stays in the 72–77 commentary band.
Dmitri Lerko ran Gemma 4 31B and Qwen 4.6 36B locally during a 10-hour flight with no Wi‑Fi. The MacBook Pro M5 Max had 128GB unified memory and a 40-core GPU; sustained load used about 1% battery per minute, and performance degraded past 100k tokens. The sharp finding is instrumentation: an iPhone cable delivered 60W, while a MacBook cable delivered 94W under the same load.
Why it matters: HKR-H/K/R all pass: this is a named first-person local-inference test with concrete hardware, model, battery, and power numbers. Scope stays practical rather than industry-shaking, so it lands in the 72–77 band.
Axios says some firms now spend more on AI than salaries; Nvidia's Bryan Catanzaro says compute costs exceed employee costs. Gartner forecasts 2026 IT spending at $6.31T, up 13.5%, driven by AI infrastructure, software, and cloud. Watch token costs: Uber's CTO has already exhausted the 2026 AI budget.
Why it matters: HKR-H/K/R all pass: the piece turns AI cost anxiety into budget facts, including Nvidia compute costs and Uber’s token-budget issue. It stays in the 72–77 band because this is trend reporting, not a launch or hard news event.
Justin Smestad argues that firms stopping junior hiring in 2026 risk costly senior-heavy teams by 2030. The mechanism: a senior can demand a 40% raise; without a two-year bench, replacement may take six months. The key issue is pipeline leverage, not quarterly headcount savings.
Why it matters: HKR-H/K/R all pass, but this is an individual commentary, not a model, product, or research release. The 40% raise and 6-month replacement claims give it enough signal for low featured.
Denis Stetskov compares AI coding to 7 defense knowledge-loss cases: a 2022 Stinger order delivers in 2026. The post cites EU shell capacity at 230,000/year and a 1M-shell pledge met 9 months late; the risk is the junior engineer pipeline, not single-task coding speed.
Why it matters: HKR-H/K/R all pass: the hook is the manufacturing-to-code analogy, the essay supplies defense-production numbers, and the nerve is junior-engineer pipeline loss. It is strong commentary, not a model or product release, so it stays in the 72–77 band.
Feldera co-founder Gerd Zellweger argues agents should be embedded in existing software, not treated as chatty coworkers. He lists 3 patterns: CLI, declarative specs, and Kubernetes-style reconciliation loops, then adds CDC streams for inserts, updates, and deletes. The key split: agents adapt logic, while the engine runs it continuously and emits precise changes.
Why it matters: HKR-H/K/R all pass, but this is vendor engineering commentary, not a launch or first-person benchmark. Concrete architecture patterns justify featured, not the 78+ band.
The author argued on 2026-04-25 that LLMs break surface-quality proxies in knowledge work. Examples include market reports and code review, ending in skims, LGTM, and a 17th Claude Code session. The critique targets evaluation: corpus likelihood or RLHF preference, not truth.
Why it matters: A sharp personal essay: LLMs separate polished output from reliable work, using code review and consulting-style deliverables as examples. HKR-H and HKR-R pass; HKR-K is weak, so it lands at the featured threshold.
Matthew Brunelle used Claude Code with Opus 4.6 to rebuild a YouTube Music-to-OpenSubsonic connector, listing 6 setup steps. The stack used FastAPI, Pydantic, ytmusicapi, and yt-dlp, with Feishin logs used to fix .view suffix handling. The useful point: a clear spec plus human review beat one-shot generation.
Why it matters: HKR-H/K/R all pass, but the impact stays at a first-person coding workflow. Claude Code + Opus 4.6, a concrete connector stack, and Feishin-log debugging place it in the quality tutorial band, not a broader industry update.
Mark Nottingham critiques the “AI agent works for you” story and lists 8 trust-misalignment cases online. One example says Microsoft’s new Outlook sends third-party email passwords to its cloud and 700+ data partners. The key issue is delegation boundaries, not model capability alone.
Why it matters: HKR-H/K/R all pass, but this is sourced commentary rather than a model or product release. Mark Nottingham’s Web-protocol authority and HN traction put it at the featured threshold, not P1.