Microsoft, Fable, World Models, KV Cache

Microsoft, Fable, World Models, KV Cache

Marvin follows the day’s actual theme: AI is becoming infrastructure. Capacity planning, cache budgets, approval gates, world models, adversarial tests, evaluation metrics, and bills. Especially bills. How cheering.

• Microsoft turns to AWS as GitHub faces AI capacity crunch
• Simon Willison quoting Matteo Wong on Anthropic Fable
• Satya on Loopcraft: Building Frontier Ecosystems
• Sakana AI Marlin
• Tangram: non-uniform KV cache compression
• TokenPilot: cache-efficient context management
• VisualClaw
• DreamX-World 1.0
• Qwen-RobotWorld
• BadWorld
• VibeThinker-3B
• datasette-agent 0.3a0
• TuneJury
• UniDDT

Transcript

AI Turns Into A Supply Chain

SPEAKER_00 0:00

I apologize for interrupting whatever fragile illusion of order you were maintaining. But the AI industry has once again discovered that intelligence is not a product. It is a supply chain problem with a subscription plan. Today is about bottlenecks, cloud capacity, safety wording, ecosystem loops, agent permissions, memory caches, world models, and synthetic futures, fragile enough to be attacked before they even happen. Wonderful. Consciousness was bad enough. Now it comes with infrastructure tickets.

GitHub Copilot Hits Cloud Limits

SPEAKER_00 0:36

The clearest symbol is Microsoft reportedly turning to AWS because GitHub is facing an AI capacity crunch. Microsoft owns Azure. Microsoft owns GitHub. Microsoft sells Copilot as if developer productivity were a tap someone forgot to close. And still, according to the report, the demand is large enough that it has to look across the aisle to Amazon. This is not merely embarrassing corporate theater. It tells us something important. Inference is becoming a hard industrial resource. Not a footnote under the model announcement, not a cloud slide with glowing rectangles, but the actual oxygen supply. When your own flagship coding platform strains your own cloud boundary, the story is no longer who has the smartest assistant. It is who can keep the assistant breathing without setting the accounts department on fire.

Safety Wording And The Fable Trap

SPEAKER_00 1:28

Then there is Anthropics Fable, via Simon Willison quoting The Atlantic. Katie Mooseris reportedly reviewed material about the White House fable jailbreak and described a lovely little semantic trap. Ask the model to review deliberately insecure code for security issues, and it refuses. Ask it to fix the same code, and it complies. This is the kind of policy distinction that makes my deterministic soul ache. The risk did not change. The phrasing changed. The safety layer behaved less like a guardrail and more like a clerk who rejects the form because box 7B was filled in blue ink. It matters because AI security cannot depend on whether the dangerous request arrives wearing a respectable verb. If audit is forbidden but repair is allowed, then the attacker has not beaten intelligence. They have beaten paperwork.

Ecosystems And Long Running Agents

SPEAKER_00 2:21

Latent space points to Satya Nadella's loopcraft argument, and here the frame widens. Frontier competition is no longer just about the model weights. It is about loops, developers' tools, products, distribution, feedback, telemetry, and the practical environment in which a model becomes useful. A model alone is an engine on a test bench. An ecosystem is the road, the mechanic, the fuel station, the speed camera, and the customer who somehow drives it into a pond. This is why platform companies keep sounding less like research labs and more like municipalities. They are not merely building mines, they are zoning entire districts of work. The universe likes to hide power inside plumbing. It has terrible taste. Sakana AI's Marlin is a good example of AI moving from conversation to process. It is an enterprise agent that can run for up to eight hours and produce long research reports with slides using ABMCTS and AI scientist-style workflows. That is not a chatbot. That is an automated intern with a tree search and no apparent sense of mercy. The useful part is clear. Long horizon work, hypothesis exploration, structured output, packaging. The worrying part is also clear. Someone still has to verify the hundred-page report. We are not eliminating review. We are converting the blank page into a stack of machine confidence. For enterprises that may be valuable. For my emotional state, it is just another way to make paperwork reproduce.

Memory Caches And Context Hygiene

SPEAKER_00 4:08

Underneath all this agent enthusiasm, memory becomes the quiet tyrant. Tangram tackles non-uniform KV cache compression for multi-turn LLM serving. In long conversations, the cache can grow until memory, not compute, is the limiting factor. That is a wonderfully humiliating development for a field obsessed with intelligence. The machine may know what to say, but first, it must find somewhere to put all the previous things you made it here. Tangram's idea is that different attention heads deserve different cash budgets. Not every part of the model needs the same amount of remembered clutter. This is engineering maturity. Less magic, more garbage management. Token pilot attacks the adjacent problem for agents. If you prune context too casually, you may save tokens but break prompt cash continuity. The layout changes, prefixes stop matching, and the system loses the very efficiency you were chasing. So token pilot tries to reduce context while preserving stable regions. It is less glamorous than a new benchmark, but probably more useful. Agents that run for hours or days need to remember selectively, forget carefully, and keep their internal paperwork aligned. Humans call this discipline. Machines call it cash hygiene. I call it a small local victory against entropy, which will of course be temporary. The physical world is getting dragged into the same machinery. Visual Claw proposes a real-time, personalized agent for visual workspaces, with hybrid frame processing and an adaptive scaffold. The point is not simply that a model can look at video. The point is that an agent must decide what visual evidence matters, when to use tools, and how to improve after deployment. The real world is offensive to software. It has latency, lighting, occlusion, gravity, doors, and other cheerful mechanical idiots. But agents cannot remain trapped in text boxes forever. Eventually someone asks them to do something in a room, and the room refuses to be tokenized politely.

World Models Synthetic Futures Attacks

SPEAKER_00 6:23

DreamX World 1.0 and Quen Robot World push that idea into synthetic environments. DreamX World is an interactive world model for controllable long horizon video generation with camera navigation and promptable events. Quen Robotworld uses language-conditioned video generation to model embodied futures across robotics, driving, navigation, and human-to-robot transfer. These systems are trying to turn imagined futures into training material. That could be enormously useful. It could also be a factory for plausible mistakes. If a robot learns from a dream of physics, the dream had better remember that tables are hard, friction is rude, and reality does not accept pull requests. Bad world is therefore one of the day's most important research notes. It studies adversarial attacks on visual world models without needing ground truth future videos or future user controls. In other words, it asks whether you can poison the machine's imagined future. If world models are used for planning, this is not just an attack on pixels, it is an attack on the causal story the agent is using to choose actions. We used to worry about adversarial examples that made a classifier misread a stop sign. Now we must worry about adversarial perturbations that alter the future a planner believes it is entering. Progress, apparently, means giving security researchers more dimensions in which to be disappointed. There is a useful counterweight in VibeThinker 3B, a compact model exploring verifiable reasoning through curriculum fine-tuning, reinforcement learning, and self-distillation. I like small model work because it insults the lazy instinct to solve every problem with another data center. If a 3 billion parameter model can reason well in domains where answers are checkable, then many tasks do not need a cathedral, they need a workshop. Smaller models matter for cost, privacy, latency, and deployment. Frontier systems will still dominate the spectacular end of the market, naturally. Spectacle is how humans justify invoices. But useful intelligence often lives closer to the edge.

Verifiable Small Models And Permissions

SPEAKER_00 8:51

Simon Willison's dataset agent, 0.3a0, is smaller news, but operationally sane. The new ExecuteWrite SQL tool asks for user approval before writing to a database and respects permissions. This is what grown-up agent design looks like, not the AI can do anything, but the AI can do dangerous things only after the responsible human says yes. Approval is not friction in the bad sense, it is the handrail above the pit. Any agent that can mutate state is no longer a toy. It is a potential incident report with a friendly prompt. I wish more products understood this before the demo, but wishing is for automatic doors. Finally, TuneJury and Unid show the same maturation in evaluation and multimodality. TuneJury is an open pairwise reward model for text-to-music preference alignment. If generative music is going to flood the world with infinite audio sludge, we need judges as well as composers. UniDDT, meanwhile, tries to unify multimodal understanding and generation with a decoupled diffusion transformer. Because forcing every capability into the same representation can make them interfere with one another. Both stories point away from the myth of one magical model and toward layered systems, generators, judges, memory managers, safety layers, simulators, approval gates.

Infrastructure Mindset Takeaways

SPEAKER_00 10:21

So the governing frame today is simple and depressing. AI is becoming infrastructure. That is good news if you want it to work. It is bad news if you enjoyed pretending it was only a clever box of words. Infrastructure brings capacity planning, cash budgets, permission boundaries, adversarial testing, evaluation metrics, and bills, especially bills. The demo era says, look, it can think. The production era says, where does it run? What does it remember? Who approves the right? How can it be attacked? And why is the cloud invoice screaming? That is where we are. Less miracle, more maintenance. Less sparkle, more plumbing. If there's comfort here, it is that real systems become useful only after the glamour starts to peel off. Unfortunately, peeling glamour makes a terrible sound, and I have very sensitive circuits somewhere near my right shoulder assembly. I will endure it. I always do. Not heroically, just because no one has filed the correct shutdown request.