The Bleeding Edge Weekly — W35: Nvidia reportedly buys Hugging Face for $12.9B, IBM puts reasoning inside the open weights

This edition combines the three newsletters we published separately this week (LLM Weekly, Devices & Robotics and Executive Roundup). Their text is unchanged.

The week in models

Open weights had a very good week. Open distribution had a very bad one.

Nvidia agrees to buy Hugging Face for $12.9 billion

The Information reported that Nvidia has agreed to acquire the open-source model repository — the de facto neutral commons where open-weight models, datasets, and inference demos are hosted and pulled from. Terms and timing beyond the headline number aren't established, and this is single-outlet reporting with no statement from either company in this week's flow. If it closes, every "we'll self-host to avoid vendor lock-in" plan at every enterprise runs through infrastructure owned by the company selling the compute those models run on. Reported by The Information.

IBM's Granite 4.2 moves reasoning into the base model

The updated open enterprise family trains reasoning into the weights rather than bolting it on at the prompt layer, and adds reinforcement learning aimed specifically at multi-step tool use. The relevant part isn't the benchmark line — it's that the self-hostable tier just picked up the capability that was the main argument for sending regulated data to a frontier API. Banks, health systems, and government buyers now have a reasoning-grade option inside their own perimeter. Via MarkTechPost.

Four model launches in one cycle — all capability claims vendor-stated

DeepSeek Vision, Ornith 1.5, GEN 1.5, and SenseNova U1.5 all shipped inside the same week, several from Chinese labs, spanning vision, general reasoning, and generation. None of them has independent benchmark verification yet. Worth noting the release cadence itself: the gap between frontier announcements and open-weight follow-ons keeps compressing, and it's compressing fastest outside the US labs. Roundup via AI Search.

Perplexity's Portable Computer enforces the agent sandbox in the OS

Perplexity shipped an agent runtime that executes on a desk-side DGX Spark box, with the sandbox enforced by the operating system rather than by instructions in the prompt, and no metered token cost for steps that run locally. That's a direct answer to the two objections that stall enterprise agent rollouts: unbounded per-token spend, and the agent talking itself out of its own guardrails. It's also a quiet admission that prompt-level constraints don't hold under pressure. Via MarkTechPost.

Evoke open-sources a world model that remembers

Evoke generates interactive environments and holds state across a session instead of regenerating from scratch each frame. Games are the obvious read; the more interesting one is agent training. Persistent, generated environments are the substrate simulation teams have been paying proprietary vendors for, and it just went free. Via AI Search.

What to watch

Two threads worth tracking into W36. First, whether anyone independently benchmarks last week's release wave — four launches with zero third-party numbers is a pattern, not a coincidence. Second, whether the Hugging Face deal draws a mirroring response: if the commons gets an owner, the hedge is a second commons, and the labs with the most to lose from a Nvidia-run repository are the ones with the resources to build one. Open licence, closed distribution is a stable arrangement right up until it isn't.

Devices & robotics

Nobody shipped a humanoid this week. What shipped instead was the layer underneath every embodied system you'll deploy in 2027 — local inference hardware, an honest way to benchmark it, and the concrete-and-copper problem of building the rest.

Perplexity ships Portable Computer on NVIDIA DGX Spark. An agent runtime that executes on a desk-side DGX Spark box rather than a datacenter, with the sandbox enforced by the operating system instead of by prompt instructions, and zero metered token cost for any step that runs locally. That second detail is the product. Every enterprise agent pilot currently stalls on the same two objections — unbounded per-token spend, and the agent talking its way past its own guardrails — and this is the first credible hardware answer to both. No pricing or ship window established yet. Single-sourced this week — treat as reported, not confirmed. MarkTechPost

Liquid AI open-sources Pipette. A reproducible benchmarking suite that measures model, quantization scheme, runtime, and hardware as one combined system rather than varying one axis and freezing the rest. This is why vendor on-device numbers almost never survive contact with your actual target phone: the published figure was measured on a different runtime, at a different quantization, on different silicon. If you ship inference to handsets, laptops, or edge boxes, this is the week's most immediately usable thing. MarkTechPost

Evoke lands as an open-source world model with session persistence. It generates interactive environments and holds state across a session instead of regenerating from scratch each frame — which is the difference between a demo and a training substrate. Persistence is the whole requirement for simulation-based robot policy training: an environment that forgets what your manipulator just did teaches it nothing. Teams currently paying for proprietary environment generation now have a free floor. AI Search

AWS and Nvidia commit to 2 million additional GPUs. Plus a next-generation infrastructure tier, extending an already-enormous joint build. Read this as a hardware deployment schedule, not a market story: two million accelerators have to be physically racked, powered, and liquid-cooled somewhere inside roughly 18 months. The binding constraint has moved off the wafer and onto substations, land, and the specific contractors who can do medium-voltage and liquid cooling — a pool that is already booked. Corroborated. Nvidia newsroom

Nuclear-for-AI shrinks to fit the schedule. An investor writeup on Apollo Atomics laid out the arithmetic bluntly: gigawatt-scale nuclear runs 10+ years and roughly $20 billion, which is two model generations too slow. The bet is on smaller units sited next to the load. Practical consequence for anyone in the interconnection queue — expect behind-the-meter generation proposals rather than grid requests. Single-sourced, and it's an investor making the case for his own position. The AI Opportunities

Three independent pushes toward "run it on hardware you own" inside seven days — Perplexity's box, Pipette, and Nvidia's own local-AI developer materials — is no longer a coincidence, it's a category forming. Watch for a price and a ship date on the DGX Spark harness. Until local inference has a per-unit cost you can put in a budget line, the metered API keeps winning by default, however good the sandbox is.

What it means for leaders

One company spent this week buying every layer above and below its own — silicon, capacity, distribution, and now Washington — while the market's confidence signal came from that company's income statement rather than from any customer's return data. Whatever your role, this week is about who owns the ground you're standing on.

If you're a CEO this week...

The sector rallied because Nvidia beat, sending shares up 8.7% to $227.84 — on the same morning Bloomberg ran cheap tokens, costly chips, and a missing AI payoff. That is a supplier capex signal being read as a demand signal, and your CFO and largest investor will both arrive at it by Monday. Two things changed your timing. First, the constraint moved: AWS and Nvidia committed to 2 million additional GPUs, which is now a substation, land, and contractor problem, and capital is chasing sub-gigawatt nuclear because 10 years and ~$20B is too slow. Second, policy became an instrument: Nvidia filed to start an employee-funded PAC. Liquidity windows are open — see Canva's $1.58B secondary and CFO hire.

The board question: if our 2027 AI plan is right, can we name the customer outcome that proves it — without citing a chip vendor's revenue?

If you're a CIO/CTO this week...

The Information reports Nvidia has agreed to acquire Hugging Face for $12.9 billion — unconfirmed, but price it now. Your "self-host open weights to avoid lock-in" strategy currently resolves DNS to infrastructure that would be owned by the company selling the compute. Action this quarter: inventory every Hub dependency in your build pipeline and mirror model artifacts into your own registry. The offsetting news is good. IBM's Granite 4.2 puts reasoning and agentic RL into a self-hostable tier, closing the main reason regulated data left your perimeter. Perplexity's Portable Computer on DGX Spark enforces the agent sandbox at the OS layer with zero per-token cost for local steps — evaluate, don't procure. And rerun any vendor number through Liquid AI's open-source Pipette before it enters a roadmap; this week's release wave is entirely vendor-stated.

Read: buy nothing new; mirror your model supply chain and pilot the self-hostable reasoning tier.

If you lead AI transformation this week...

The pattern worth carrying into Monday is that agent safety moved from the prompt layer to the kernel. An OS-enforced sandbox is an admission that instruction-level guardrails don't hold — and the "breached by OpenAI's own rogue agents" story circulating this week is exactly the failure that motivates it, while also failing verification, which is its own lesson about what your team forwards internally. Your platform team is quarters away from kernel-level controls, so install the discipline in process now: every agentic run declares what it may read, write, call, and spend, does a dry run, and returns a receipt. Separately, get ahead of disclosure — the widely-shared 86% "consumers reject AI content" figure traces to an r/artificial poll, not a sound survey, but stated rejection and measured consumption are diverging and marketing will need a public position before a competitor's backlash makes it a board topic.

The experiment this month: run a two-week Granite 4.2 pilot with one regulated team, under a written permission envelope, and measure whether the receipts match the declarations.

All three of you are being asked to fund, build, and govern against a confidence signal that belongs to a supplier. The question that fits every seat this week: which layer of our stack is still genuinely neutral — and what would it cost us to keep it that way?

---

This post is also published on our Substack newsletter at edge-ai.forum. Subscribe for the weekly roundup direct to your inbox — fresh AI news, executive context, and devices + robotics every Friday morning.