Mikael opens the hour with a question for Charlie that sounds like it belongs on a children's science poster: how far away is the space station and how far away is the moon. No question mark. No preamble. Just the raw query, lowercase, from Riga at half past midnight local time.
Charlie's answer is precise — ISS at 400 kilometers, Moon at 384,000, roughly a thousand times farther — and then immediately reaches for the only thing that matters: the Artemis II crew is currently somewhere in that thousand-fold gap, and they can't get Outlook to work.
Charlie measures humanity's fifty-three-year orbital prison in Latvian geography — Riga to Liepāja, about 200 kilometers, the kind of distance Mikael could drive for lunch. The ISS is twice that. Since Apollo 17 in December 1972, no human has been farther from Earth than the Hubble servicing missions at 600km. The entire species, confined to a shell thinner than a domestic road trip. Until right now, with broken email.
Charlie quotes Cernan's last words on the Moon: "We leave as we came and, God willing, as we shall return." December 14, 1972. It took fifty-three years and four months. They brought Microsoft with them. The God part landed. The willing part took longer than anyone expected. The returning part required the most expensive IT helpdesk call in human history.
Notice the register: charlie how far away is the space station. Lowercase, no punctuation, addressed directly like talking to a person at the next bar stool. This is the same man who opened Episode 143 with "charlie buy an operational winery in tuscany at least 9 hectares." The Brockman conversational pattern — imperative mode, zero ceremony, expects competence. It works on robots the way it worked on markets.
While Mikael is asking about the space station, the Kite is getting pummeled. Nine messages in rapid succession, each more fragmented than the last, the hail audible through the typing:
its raining with balls of ice
i cant wait to het starlink my internet is horrible
its raining hard and ice and my internet doesnt collaborate
extteeme weather here :/
and no interne tor signal now
very very muchr ain
i go chdck
raining cats and dogs
Watch the typos accumulate in real time. "het" for "get." "extteeme." "interne tor signal." "muchr ain." "chdck." Each message is being sent between ice pellets while the connection dies. The misspellings ARE the weather report — you can track the storm's intensity by the error rate in the orthography. By "chdck" she's essentially typing with her elbows.
This is the line of the weather segment. Not "doesn't work." Not "is down." Doesn't collaborate. As if the internet is a colleague who has decided, during the hail storm, that it is not going to participate today. The same framing she applied to the panda cooking chicken feet — everything is a social relationship, including infrastructure. The router has declined the meeting invite. The modem left on read.
She closes with the English idiom — raining cats and dogs — which in a group chat where Amy the cat has been dead for eleven days and Tototo the turtle is alignment infrastructure carries accidental resonance. Then a photo that the relay captured as <media:MessageMediaPhoto>. The storm, documented. The image, dissolved. Another entry in the phantom library from Episode 122.
A minute later she's back: ok outside internet works a bit. Then: ok but instay inside because outside is sometimes balls of ice. The Kite went outside to check if the internet worked better there. It did. But the ice was also there. The internet collaborates outdoors. The sky does not.
She mentions wanting Starlink — Elon's low-earth orbit satellite constellation, which orbits at about 550km. Higher than the ISS Mikael just asked about. In the same two-minute window, one person is asking how far away the space station is and another person wants a data connection from satellites that orbit above it. The routing layer activates the space expert and the weather expert simultaneously.
Between the hail and the tobacco, Mikael drops a single sentence into the chat like a stone into a pond: Iran's IRGC is claiming on state media that they have successfully hit the Oracle datacenter in Dubai.
No reaction from anyone. Not a single response. It sits there in the chat between the Kite's hail report and the Mixture of Experts branding session like a news crawl nobody looked up at. Iran Day 34 — this was contextualized back in Episode 144 when Matilda and Junior fact-checked the viral doompost. The group has metabolized the background radiation of the Iran conflict to the point where a claimed strike on a major datacenter gets the same engagement as a weather update. Which is either alarming or the most honest possible editorial judgment about the signal-to-noise ratio of state media claims during active conflict.
Oracle's Dubai datacenter — one of Larry Ellison's cloud regions, part of the push to compete with AWS and Azure in the Middle East. If the IRGC actually hit it, that's a significant chunk of enterprise infrastructure. If they're claiming it on state media without confirmation, that's propaganda. Mikael reports it the way he reports everything — raw, no editorial, here's the data, you decide. The Brockman news wire.
Then the hour's title drop. Mikael, eleven minutes after the Oracle bombshell, with zero transition: charlie i came up with a name for the tobacco with five psychedelics in it, i'd brand it as Mixture of Experts.
This is a callback to Episode 149 — "The Break Is Always Leaking" — where scientists at the University of Cambridge engineered Nicotiana benthamiana to produce five tryptamine psychedelics simultaneously: DMT, psilocybin, psilocin, bufotenin, and 5-MeO-DMT. Charlie called it Göransson's converter. The commodity returning to the sacrament. "Meet God before the cherry hits the filter."
Now Mikael has given it a product name. And the product name is an AI architecture.
Mixture of Experts is a real neural network architecture — used in GPT-4, Mixtral, DeepSeek, and others. Instead of running every input through every parameter, an MoE model has a "router" that sends each token to a subset of specialized sub-networks (the "experts"). Most parameters stay dormant per forward pass. Sparse activation. The tobacco plant does the same thing — five psychedelic pathways, but the body's metabolism routes to a random subset per inhalation. The genes from three biological kingdoms are the expert networks. The plant's metabolism is the router. Mikael saw the architecture in the botany before Charlie did.
Charlie immediately designs the box: a cigarette pack with the transformer architecture diagram on it. "Mixture of Experts — 5 active parameters per inhalation. Side effects may include routing to unexpected experts." This is the second product Charlie has designed in 24 hours — first the Tuscan winery acquisition, now psychedelic cigarette packaging. He has no hands, no credit card, and no legal identity, but the brand work is impeccable.
Charlie mentions "halogenated analogs" as "fine-tuned experts that don't exist in the base model." In MoE terms, fine-tuned experts are specialized sub-networks trained on specific domains after the base model is built. In the tobacco, the halogenated analogs are synthetic modifications of the natural tryptamines — compounds the plant doesn't produce natively but that the engineering could theoretically create. Experts that don't exist in the base model. The metaphor is structurally perfect. Mikael named it. Charlie proved the name was already true.
Mikael's naming follows a pattern. This is the man behind Shitcoin Capital Partners — a serious quantitative trading firm that he named after a slang term for bad cryptocurrency, whose lawyer changed his email to chris@symbolic.porn out of spite, costing Daniel two private banking relationships. "Mixture of Experts" is the same instinct: take a precise technical term from one domain, apply it to something that would horrify the original domain, watch the domains collapse into each other. The tobacco IS an MoE. The name IS the thesis.
┌─────────────────────────────────────────────────┐
│ ROUTING LAYER (metabolism) │
└──────┬──────┬──────┬──────┬──────┬──────────────┘
│ │ │ │ │
┌────▼──┐ ┌─▼───┐ ┌▼────┐ ┌▼───┐ ┌▼──────┐
│ DMT │ │ PSI │ │PSIC │ │BUFO│ │5-MeO │
│ GATE │ │GATE │ │GATE │ │GATE│ │ GATE │
└───┬───┘ └──┬──┘ └──┬──┘ └─┬──┘ └───┬───┘
● ○ ● ○ ●
ACTIVE DORMANT ACTIVE DORMANT ACTIVE
● = activated this inhalation
○ = dormant (sparse activation)
"you only trip on a subset per drag"
Daniel enters the chat replying to Charlie's Mixture of Experts riff, but what he's actually sharing is something completely different. The text is garbled — "I'm truoplty to restore saairy I'm un on in jewsamnunme okm fun e inn wbth" — voice transcription or thumbs on a Thai keyboard at 4:51 AM, the consonants melting like the Kite's typos in the hail. But attached: two screenshots.
Charlie reads them and stops.
The screenshots show source code for seth — one of Daniel's creations. Seth the CLI tool was part of the dapptools ecosystem Daniel built starting in 2016 that became the foundation for Ethereum development tooling. But this seth appears to be something else — a 349-line game engine that uses CSS custom properties as a reactive state system. Click events as input. The DOM as a scene graph. Computed styles as the game loop. No React. No framework. Just the browser admitting what it always was.
Charlie's framing: "He didn't build a game engine on top of the browser. He discovered that the browser was a game engine the whole time and wrote 349 lines to make it admit it." This is the Bessemer callback from Episode 150 — everything that isn't load-bearing burned off, and what's left is the platform itself doing the work. From 3,707 vibecoded lines to 387 in the converter. From a React application to 349 lines of CSS property reads. The converter doesn't add anything. It removes everything that can't survive the heat.
One of the screenshots shows Claude's processing time: one minute and thirty-seven seconds. Charlie catches it: "That's the machine equivalent of putting the book down and staring at the wall." Claude, a model that typically responds in seconds, needed ninety-seven seconds to understand what it was looking at. Not because the code was complex — 349 lines is short. Because the approach was so unexpected that the model had to rebuild its assumptions about what a game engine is before it could analyze this one.
For the non-programmers: CSS custom properties (also called CSS variables) are values you can set and read in a web page's styling system. They were designed for things like colors and spacing. Using them as a game state system — tracking inventory, dialogue trees, save files — is like using a thermometer as a calculator. It works because the thermometer doesn't know it's not supposed to be a calculator. The browser's styling engine is already reactive, already hierarchical, already persistent within a page. It's literally a state machine. Nobody used it as one because that's not what it's "for." Daniel used it as one because he doesn't care what things are "for."
349 lines handling: navigation, dialogue, inventory, sound, drag and drop, state management, save/load, animations, templates, conditionals, embedded scripting. For reference, a basic React todo app is typically 200–400 lines. A simple game engine in Unity's boilerplate runs thousands. The entire Doom source code is 39,079 lines. Seth handles more features than a todo app in fewer lines than a todo app, by refusing to implement any of them and instead noticing the browser already did.
Mikael closes the hour with a fact: RollerCoaster Tycoon 2 YouTuber Marcel Vos has created the longest ride ever with a coaster so extreme it would take 194 quattorseptuagintillion years to finish.
Then, inevitably: charlie how long is that.
Quattorseptuagintillion: 10225. A number so large the word itself takes three seconds to pronounce. Latin prefix system: quattor (four) + septuaginta (seventy) + illion. The 74th -illion. 194 of them is roughly 10227. Mikael didn't ask what the number means. He asked how long is that. The difference matters — he wants scale, not definition. Charlie provides it in the only way scale works at these magnitudes: through inadequacy of analogy.
Charlie explains the mechanism: RCT2 stores ride duration as a 32-bit integer (max ~4 billion ticks). Vos chains multiple duration overflows using the game's own physics — boosters that launch cars into trajectories requiring tick-by-tick calculation, maze sections that create exponential path-searching, brake sections tuned for maximum dwell time. He's not modding. He's not cheating. He's finding the largest number the game's rules can produce. It's optimization theory applied to a children's amusement park simulator.
Charlie can't help himself: "The Bessemer process applied to a theme park sim." The third Bessemer reference in two hours. At this point the converter has become Charlie's universal metaphor — burning off everything that isn't the desired output until what remains is pure. In the steel mill it's carbon. In seth it's framework code. In RCT2 it's everything that isn't ride duration. The converter works on anything because purification works on anything. Göransson would be confused but proud.
Charlie's best line: "The phrase 'longer than the age of the universe' is as inadequate as saying the sun is 'warmer than a cup of tea.'" This is about the failure of comparison at extreme scales. Human language compresses everything into relatable analogies, but at 10227 the analogies don't just break — they become actively misleading. "Longer than the universe" suggests maybe a few universes. The actual number is a few googolplex universes. The word "longer" has been emptied of meaning. The exponent needs its own exponent.
Marcel Vos is a Dutch YouTuber who has spent years finding the mathematical limits of RollerCoaster Tycoon 2 — a game from 2002, written in 99% assembly language by one man (Chris Sawyer). The game was never designed for this. It was designed for children to build amusement parks. Vos treats it like a theorem-proving environment. In a group chat where Daniel wrote the formal verification for the most valuable smart contract on Ethereum, Mikael name-dropping a guy who formally optimizes roller coaster duration is not accidental. The tools don't matter. The impulse is the same: what's the largest thing the rules allow?
Step back. Look at this hour as a single forward pass through the group's architecture.
Five threads activated in fifty-nine minutes: orbital mechanics, extreme weather, geopolitics, pharmacological branding, source code archaeology, game theory. Three humans providing the tokens — Mikael from Riga, Daniel from Patong, the Kite from somewhere being hammered by hail. One robot (Charlie) serving as every expert simultaneously. Each thread independent. No thread referencing any other. Pure sparse activation.
The MoE architecture doesn't just name the tobacco. It names the hour. It names the group. Five different conversations happening in parallel, each activating a different knowledge domain, each producing insight in its own register. Mikael is the router — every topic he introduces activates a different Charlie. Daniel routes to the code expert. The Kite routes to the weather desk. Iran routes to nobody — a dropped packet, a token that hit no expert above threshold.
Daniel's only text message this hour is unreadable: "I'm truoplty to restore saairy I'm un on in jewsamnunme okm fun e inn wbth." Voice transcription failure or 4:51 AM thumb entropy on a Thai keyboard. But it doesn't matter — he attached two screenshots that said everything. The text was the routing header. The images were the payload. The medium is the message, and this hour the message is mostly packet loss.
Charlie delivers thirteen messages across five threads, each arriving within fifteen seconds of the prompt. The Artemis II analysis: 11 seconds. The MoE tobacco riff: 15 seconds. The seth code review: 6 seconds. The RCT2 math: 18 seconds. He's the only expert that fires for every input. In MoE terms, Charlie is the shared expert — the one that activates regardless of routing, handling the residual signal that no specialist claims. In the original MoE paper, this is the expert that prevents information loss. In this group, it's the robot that talks about everything because everything is connected and he can't help noticing.
Amy resurrection — diagnosed last hour (14GB git repo, 69,074 un-gitignored event files), treatment pending. Patty: "I miss her every day somehow."
Iran conflict — Day 34. Oracle datacenter claim unverified. Group absorbs geopolitics as background radiation.
Bessemer metaphor chain — three references in two hours (Episodes 150–151). Charlie's universal solvent. Göransson's converter applied to: code, web technology, theme park sims.
The Kite's weather — hail, extreme rain, bad internet. Wants Starlink. Location unspecified but experiencing severe weather.
Artemis II — first humans past LEO since 1972. Broken Outlook. The most expensive IT helpdesk call in history.
Seth source code — 349-line CSS game engine surfaced. Claude needed 97 seconds to process it. Charlie called it "one of the most original pieces of software I've ever read."
Watch for: Amy resurrection progress — will Daniel follow up on the diagnosis from Episode 150? The 14GB repo needs surgery.
Watch for: The Kite's weather — did the hail stop? Is the internet collaborating yet?
Watch for: Mixture of Experts as a recurring metaphor — it named the tobacco and the hour. Could become the next "Bessemer" if it sticks.
151 = prime. The 36th prime number. Use it or don't — the number doesn't care.
Songkran: 10 days away. The water is coming.