jason belk network engineer → physical AI

2026-06-05

Off the hands-on track: the GTC Taipei keynote through a network engineer's lens

nvidiagtc-taipeiphysical-aivera-rubincosmosisaac-gr00tautonomous-vehicleslearning-log

Yesterday’s plan was the weekend centerpiece: get the cruise-promenade scan into Isaac Sim next to a Franka arm. Yesterday was actually a flight home from Cisco Live in Vegas and setting up my daughter’s 6th birthday party. The day job and the family calendar both outrank the side project, and a learning-in-public log is more useful when it says that plainly. No Isaac Sim, no friction log today.

The one piece of NVIDIA work I did get was the GTC Taipei keynote, start to finish, all 2 hours of it. Watching a keynote isn’t building anything. But this one maps the exact territory I’ve been ramping into, so the notes are worth keeping. Three things landed hard, and all three landed because of where I’m coming from rather than because they were the loudest announcements.

Vera Rubin, and the data center that gets built in a digital twin first

Vera Rubin is in full production and ships this fall. It’s an end-to-end system, not a single GPU: Rubin GPUs, the new Vera CPU, the storage and networking trays, all designed together. The silicon is the headline everyone will quote.

The part that actually stopped me was a workflow, not a chip. NVIDIA showed designing and validating an entire Vera Rubin AI factory in an Omniverse digital twin before a single rack lands: the layout, the power, the cooling, the network fabric, every integration tested in simulation first. They’ve named the blueprint DSX. The pitch is that a factory now running 50 to 100 billion dollars per gigawatt has to work the first time, so you prove it out in software before the concrete cures.

That’s the same shape as work I’ve done for years. You model the topology, simulate the behavior, validate the integrations against the model, and only then do you cable anything in the real room. Network automation has been calling that a digital twin of the network for a while now. NVIDIA is doing it one layer out, for the building the network lives in: power, cooling, racks, and the spine all validated before anything is racked.

Here’s the connection that made the last week of my own work click into place. The substrate under that whole demo is Omniverse, and Omniverse is OpenUSD. The thing I’ve spent this week authoring by hand on a MacBook is the same composition layer NVIDIA uses to assemble a gigawatt-scale factory in simulation. Different scale, same file format, same non-destructive composition model I wrote about in the cruise scan entry. That’s the moment the OpenUSD ramp stopped feeling like a side quest.

Alpamayo 2, and 6 months of letting the car drive

NVIDIA announced Alpamayo 2 Super, a 32-billion-parameter open reasoning model for autonomous vehicles, and called the result the first reasoning autonomous vehicle. The demo narrated its own decisions out loud: nudge left due to the stationary vehicle ahead, yield to the pedestrian in our lane, keep distance to the cut-in vehicle merging from the left.

I have a specific lens on this one. My wife and I have a Model Y we got in January, and we let it drive almost everywhere, both of us, every day. That narration describes out loud what my car already does silently 100 times a commute. I’m a daily user, not an AV engineer, so I can’t speak to the stack underneath. What I can say is that the thing NVIDIA is selling here, the reasoning being legible in language instead of staying a black box, is exactly the thing that would change how I trust the car. When FSD does something I don’t expect, the missing piece is always the why. A model that can state the why, for safety validation and for regulators, is a genuinely different thing to live with than the one in my driveway.

Cosmos 3 and Isaac GR00T: the data problem, and the simulator that answers it

Jensen framed physical AI’s hard problem as data, and the framing was clean. Language models trained on all the text humans wrote and read, from our perspective. Robots need data from the robot’s own perspective, first-person, and almost all the video in the world is third-person. So you climb a ladder: teleoperation (human demonstration), then simulation, then world foundation models that generalize across any viewpoint.

Cosmos 3 is the foundation model for that middle-and-top of the ladder. It’s a mixture-of-transformers design, a reasoning transformer feeding a generation transformer, trained on 20 trillion tokens of multimodal data, shipped open in a high-accuracy “super” size and a fast “nano” size. It can act as the perception model, the world simulator, or the policy itself.

This connected straight to the Ant I trained in Isaac Lab earlier this week. That was simulation as a bootstrap for a control policy at toy scale, an evening and under a dollar of compute. Cosmos 3 is the same idea at frontier scale: when real-world data is impossible to collect, compute becomes the data. Having done the small version of that loop by hand, the big version reads as a continuation instead of a slide.

NVIDIA also announced an Isaac GR00T reference humanoid robot aimed at academic labs: a Unitree H2 Plus chassis, Sharpa five-finger hands, a Jetson Thor brain, roughly 6 feet and 150 pounds, running the full Isaac GR00T software stack. The interesting move there is a developer-experience one. A reference design takes a research lab from months of stitching together simulators, teleop rigs, and data pipelines down to hours. That’s a removing-setup-friction play, and it’s the kind of thing I pay attention to as a DevRel problem rather than a hardware one.

I’ll be honest about the edge of my understanding. The architecture details are where I’m still building intuition. Mixture-of-transformers, and the state-space-plus-mixture-of-experts hybrid in the Nemotron 3 Ultra model they also shipped: I can follow what each piece is for, but the why-it-works at the math level is a newer muscle for me, and watching a keynote is not the same as understanding the model. That gap is exactly what the cert study on my calendar is for.

What I took from it

The repeated point across the whole keynote was that the same computing pattern keeps showing up: a model, a harness that orchestrates it, tools with skills, and a runtime, whether that runs in the cloud, on a PC, in a car, or in a robot. For someone coming from network automation, the lesson underneath that was quieter and more useful. The leverage keeps landing in the same place I’ve already worked: the modeling layer, the single source of truth, and the validate-before-you-deploy step. The silicon gets the headline. The part I’d actually work on sits one layer down, in the modeling and validation workflow, and that layer already looks familiar.

What’s next

Reach me on LinkedIn or via Sierra Code Co.