Willy Wonka And The Consolidation Factory

Mike Teevee got shrunk because he tried to seize a network that was not his. This is the lesson at the center of a 1971 children's musical nobody has read as a documentary about distributed systems. They should. The film knew something the present moment is about to learn the hard way.

Willy Wonka and the Chocolate Factory was released fifty-five years ago. It is remembered as a tour through a candy factory with five children and four dark fates. Most people remember Mike Teevee's fate as comeuppance for a brat who watched too much television. That reading is correct as far as it goes. It misses the deeper structural lesson the scene teaches, which has nothing to do with television and everything to do with what happens when unwanted power tries to seize a system it did not create, does not understand, and cannot control.

How The Scene Actually Plays

The scene works like this. Wonka shows the touring families a machine called Wonkavision. The machine teleports a chocolate bar across the room. The bar disappears from the platform on one side. It reappears on a television screen on the other side, miniaturized. Wonka explains how it works. He warns the kids not to touch anything. Mike Teevee ignores him. The kid jumps onto the platform himself, gets transmitted, and arrives on the receiving television a few inches tall. His mother carries him out of the factory in her purse.

Wonkavision is a network. It is a careful piece of engineering Wonka built and understood the rules of. It was meant for transmitting chocolate bars. The input side and the output side were both designed for that purpose. The shrink ratio was calibrated for it. The signal carried what the architect intended it to carry. The network worked because everybody who used it respected what it was for.

Mike did not respect what it was for. He saw a powerful piece of infrastructure he did not build, did not understand, and had no right to use, and he decided it belonged to him. Watch the scene again with this lens. He does not just ignore an instruction. He says he will be the first person in the world to be sent by television. He frames himself as a pioneer. He claims the technology. He treats the system's purpose as flexible because his ambition matters more than its design. The shrinkage is not Wonkavision punishing him. The shrinkage is the network revealing how small his claim actually was.

The Same Scene Is Playing Out Now

The same scene is playing out right now in artificial intelligence infrastructure. Decentralized networks are being built in public. The architecture works. The research is published in peer-reviewed venues. The code lives in open repositories anyone can read. The Petals paper on distributed LLM inference is on arXiv and the code is on GitHub under the MIT license. The benchmarks have been validated by academic institutions on multiple continents. The corporations are watching all of this happen and starting to circle. They are calculating how to seize it. How to position themselves as the necessary partner. How to wrap the open thing inside a closed product they can charge for. How to remain at the center of an architecture designed to have no center.

They are Mike Teevee jumping onto the platform.

The thing they do not understand is what Mike did not understand. Decentralized networks do not just resist corporate capture. They shrink unwanted power by design. The whole point of the architecture is that no single party can seize it. When a corporation tries to use a decentralized network the way they use their own data centers, the network refuses. Routing goes around hostile actors. Validators reject outsized claims. Token economics, when designed correctly, dilute concentrated influence. The protocol does not need a security team. The protocol is the security team. Bitcoin has operated for over thirteen consecutive years without a single coordinated takedown attempt succeeding, across every regulatory crackdown and exchange collapse in that window. Their attempted control gets compressed into a position mathematically smaller than they expected. They get shrunk. Not as punishment. As physics.

Mike thought he was about to become the most famous kid in the world. He ended up in his mother's purse, an inch tall, taken to the Gum-Stretching Room as a problem the factory had to solve before the family could leave. The metaphor is precise. The corporations think they are about to capture the next layer of computing. They will end up running infrastructure-as-a-service on top of someone else's open protocol because that is the only role the architecture allows them. They will be carried out of the building by their own corporate parents, looking for somebody who can stretch their flattened position back into something useful for the next earnings call.

The structural insight most readers will miss the first time around: decentralized infrastructure is not just a different way to deliver the same product centralized providers already deliver. It is a different shape of system that produces different outcomes for the people who try to capture it. Centralized infrastructure rewards the corporations that control it. Decentralized infrastructure dilutes them. These are opposite functions. Unwanted power operating in a decentralized environment is not just inefficient. It is inverted. The harder they push, the smaller they get.

This is why the takeover narrative is going to fail in ways that surprise the people running it. They are used to a world where capital deployed at scale buys the position they want. Decentralized networks were specifically engineered to make that exchange impossible. The capital still gets deployed. The position does not get bought. The investor presentations continue. The acquisitions continue. The strategic partnerships continue. None of it will produce the corporate control the architecture was built to prevent. The platform stays open. The network stays distributed. The kid in the purse keeps shrinking.

Look at the corporate adoption examples already on the books. AT&T integrated with Helium for Wi-Fi offload in April 2025. Lockheed Martin Space deployed IPFS nodes in orbit through Filecoin. Microsoft signed a 20-year PPA with Constellation for a nuclear restart. Google signed a 25-year PPA with NextEra for another. The corporations bought services. The networks did not get bought. The structural rule held. The integrations work because the corporations accepted the role the architecture allowed them. Mike Teevee never did.

The honest tradeoff worth naming: decentralized systems do not capture margin the way centralized systems do. The value flows to participants rather than concentrating in shareholders. For the corporations being shrunk, this looks like loss. For the people running the nodes, it looks like the system finally working the way it was supposed to. Which view is correct depends on where the reader is standing. The point is that the architecture decides. It does not negotiate.

The Architecture Was Always The Lesson

Wonka is not an accidental analogy. Read the scene as a parable about the relationship between architects and users. Wonka built the system. Wonka understood the system. He warned the children, not because he was hostile, but because he respected what he had made. The kids who listened got chocolate. The kid who tried to claim the technology for himself ended up in luggage. The architecture decided. The authority figure was just there to explain.

The 1971 film was a children's musical that secretly became one of the most prescient documentaries about distributed systems ever made. Mike Teevee got shrunk because he did not respect what he did not build. The corporations are going to get shrunk by decentralized AI networks for the same reason, on a larger scale, in front of a much larger audience.

The architecture is the lesson. The shrinkage is the consequence.