Music is math.
Not as a slogan. As a description of the machine. Sound gets chopped into a learned alphabet, a transformer predicts the next symbol the way your phone predicts the next word, and a decoder turns the symbols back into something you can hear. That is the whole trick.
The reason it belongs in an operator's field manual is what happened next. The same recipe — find the alphabet, predict the next piece, decode — went and conquered proteins, robot arms, and the weather. Once you have seen the shape once, you stop being surprised by the headlines and start being able to predict which domain falls next. This page is the mechanism, the receipts, and the three places the story is oversold.
Jump to section tap to open
The claim
Ask most people how an AI writes a song and you get a shrug and the word "magic." Ask an engineer and you get an answer so boring it sounds like a dodge: it is autocomplete. Both are wrong in the same direction — they treat music generation as a music achievement.
It isn't. It is a tokenization achievement. The hard part was never composition; it was finding a way to write sound down as a short sequence of discrete symbols, so that a machine built to finish sentences could finish a song instead. Once sound had an alphabet, the sentence-finishing machine worked unmodified.
That is the sentence worth carrying out of this page, because it generalizes. The surprising discovery of the last few years is not that AI can do one impressive thing. It is that a single family of architectures, pointed at a single objective — predict the next piece — keeps falling into domain after domain that look nothing alike, as soon as somebody works out the alphabet. Music, proteins, motion, weather. The world turned out to be far more writable-down than anyone expected.
Sound is already numbers
Start with the thing nobody finds surprising and everybody skips past: audio on a computer is already a list of numbers. A CD stores 44,100 amplitude measurements per second, per channel, at 16 bits each — so a stereo second is 88,200 numbers, about 1.4 megabits (Red Book). Sound is not like math. It is stored as math.
So why not just predict the next number? Because 44,100 steps per second is a hopeless sequence length. Three minutes of one channel is about 7.9 million numbers, and a model that had to emit them one at a time would spend its entire capacity on the shape of a waveform rather than the shape of a song. The raw representation is technically complete and practically useless — the same reason nobody builds a language model over individual pixels of a scanned page.
The fix is a neural codec: a small network trained to squash a chunk of sound into one of a fixed set of learned entries, and a matching network trained to turn that entry back into sound. Now sound has a vocabulary. Four numbers you can hold onto, all read off the papers:
- 50 a second. Meta's MusicGen runs a codec at a 50 Hz frame rate, with four codebooks of 2,048 entries — 200 tokens per second of audio.
- 1,500 steps for 30 seconds. The same paper: an interleaving trick lets it emit four tokens per step, so half a minute of music costs 1,500 prediction steps rather than 6,000.
- 600 a second. Google's MusicLM states it plainly: "one second of audio is represented by 600 tokens" — plus a sparse 25-per-second layer that carries melody and structure while the dense layer carries timbre.
- ~90×. Descript's audio codec compresses 44.1 kHz audio into tokens at 8 kbps — about 86 frames a second, nine codebooks deep.
That is the entire magic trick, stated as arithmetic: 44,100 numbers a second becomes a few hundred symbols a second. Now the sequence is short enough that a transformer can hold a musical idea across it, and the model does what it has always done — given everything so far, predict what comes next. Your prompt is just more context, steering which continuation is likely.
Pick a domain and run it:
What Suno will and won't tell you
Every number above comes from an open paper. Suno — the tool most people actually mean when they say "AI music" — has published none. No paper, no model card, no architecture post, across every version through v5.5 (shipped 26 March 2026). Anyone who tells you exactly how Suno works is reading tea leaves. So here is precisely what is on the record, and where the record stops.
The founders' own code. Before Suno was a music company it open-sourced Bark, a text-to-audio model built in the GPT mould: predict semantic tokens, then coarse codec tokens, then fine ones, then decode to a waveform. Token prediction, end to end.
The CEO, on the record. In a March 2024 interview, Mikey Shulman described the approach as next-token prediction over audio tokens — "very similar to text… you train a model to predict the probability over all of the next token" — and said their tokenization is "at least similar to how it's done in the open source stuff." He also named the constraint that governs the product: "We care a lot about how many tokens per second we can generate, because we need to stream you music as fast as you can listen to it."
Where it stops. That was two model generations ago. The popular description of Suno as a transformer paired with a diffusion refiner is third-party inference that Suno has never confirmed. There is no public figure for its sample rate, codec frame rate, or token rate — the 48 kHz specs floating around come from third-party guides, not from Suno. If you want to reason about the tokens behind an 8-minute Suno track, you are borrowing MusicGen's arithmetic and should say so.
The honest summary: Suno's stated paradigm is the one this page describes, its ancestor provably worked that way, and whether today's model still does is not public. That is a normal state of affairs in 2026 — and it is why the mechanism is worth understanding from the open systems, where the numbers are checkable.
What else turned out to be a language
Here is where it stops being a music story. The same three-step shape — find the alphabet, predict the next piece, decode — has been pointed at domains that share nothing except sequential structure.
Proteins — the one that should stop you
A protein is a sentence in a 20-letter alphabet. Evolution spent four billion years writing the training corpus and left it lying around in public databases. So ESM3, a 98-billion-parameter model trained on 771 billion tokens of protein, learned to speak it — and was used to design esmGFP, a green fluorescent protein that is 58% identical to the nearest known fluorescent protein: 96 mutations across 229 residues. It was not a simulation. They expressed it, and it glowed — peak emission 512 nm, brightness in the natural GFP range after about two days (Science, 16 January 2025).
Now the three details that popular retellings drop, each of which I had to correct in my own draft:
- The 58% neighbour is a red protein. It is tagRFP. Against the nearest wild-type protein of any kind it is 53% identical; against the original jellyfish GFP, 36%. "58% similar to anything known" is wrong as usually written.
- The 500 million years is an analogy, not a measurement. The authors fit a line through six anthozoan GFPs whose species have dated common ancestors, correlating sequence identity with elapsed time. It estimates how far apart two species would have to be for their GFPs to differ this much — not how long evolution would have needed to find this protein.
- It was not one shot. Tens of thousands of candidates were generated, 88 went onto a first 96-well plate and produced exactly one dim hit — 50× less bright, maturing over a week. esmGFP turned up on the second plate. Roughly one good protein per 184 wells.
That last one is the real lesson, and it is not a debunk. A model that turns "search an astronomically large space" into "screen two plates" is genuinely transformative. It just isn't authorship — it is candidate enrichment, and the wet lab is still the judge.
One more correction, because it matters two sections down: ESM3 is not GPT run left to right. It is a masked model — it generates by starting from a fully masked sequence and unmasking tokens in any order, filling in blanks rather than continuing a sentence. Same bet (discrete tokens, transformer trunk, predict what belongs), different reading order. The frontier 98B model is also closed; only a 1.4B version has public weights.
Robots — the recipe is fine, the data isn't
This is the one that sounds like science fiction and is mechanically the most literal. Google's RT-2 writes a robot action directly into the text stream: eight integers per step — three position deltas, three rotation deltas, gripper, a stop flag — with each continuous axis chopped into 256 bins. The model predicts them exactly the way it predicts words. A robot arm and a chatbot, running the same play.
But the frontier complicated it, and the complication is the interesting part. Physical Intelligence's π0 keeps a token-predicting vision-language model as its backbone and then abandons tokens for the actions themselves, generating continuous 50 Hz motion through flow matching — a diffusion relative — because naive binning breaks down on fast, dexterous control. Their own follow-up paper says so outright, then partially rescues the token story with a smarter tokenizer whose purely autoregressive model matches the flow-matching one while training with up to 5× less compute. π0.5 settled into the split worth quoting: discrete decoding for the high-level plan, continuous flow matching for the low-level motor commands. Google announced Gemini Robotics 2 on 30 July 2026 — the day this page was researched — as a closed system with blog-level disclosure, so treat it as announced, not proven.
Weather — prediction with no tokens in it at all
The atmosphere is a grid of numbers evolving in time, so forecasting is the purest "predict what comes next" problem on the list. DeepMind's GenCast — a diffusion model, explicitly the same family behind image and music generation — beat ECMWF's ENS, the best operational ensemble in the world, on 97.2% of 1,320 evaluation targets, rising to 99.8% beyond 36 hours out, and produces a 15-day forecast in 8 minutes on a single Cloud TPU v5 where the physics ensemble takes hours on a supercomputer (Nature, 4 December 2024).
Two things the headline version leaves out. Google's own production successor, WeatherNext 2 (November 2025), is not a diffusion model — it injects noise into the weights instead, runs 8× faster, and now drives weather in Search, Gemini and Maps. And every one of these models is trained on ERA5 reanalysis, a dataset manufactured by physics-based data assimilation, then initialized from physics-based analyses. The AI replaced the expensive simulation step. It did not replace the physics underneath.
Two ways to generate — and why the binary is already leaking
Two dialects keep showing up. Autoregressive: chop the thing into discrete symbols and predict the next one, the autocomplete you have now seen in music, proteins and robot actions. Diffusion: start from pure noise and repeatedly denoise until the finished thing emerges all at once — how images, video and weather tend to work.
Useful as a first map. But by 2026 the real axis is not autoregressive-versus-diffusion; it is discrete symbols versus continuous values, and each side has more than one way to decode:
Decode them left to right (MusicGen, RT-2), or decode them in any order by unmasking — which is how ESM3 designs a protein, and how masked audio models generate music several times faster than the autoregressive ones. Same tokens, different reading order.
Denoise them (Stable Audio generates 3-minute stereo tracks over a latent running at 21.5 steps a second — no tokens anywhere; GenCast does the same to the atmosphere), or flow-match them, diffusion's faster sibling, which is what moves π0's robot arm.
So "AI music" is not one architecture. MusicGen autocompletes tokens; Stable Audio denoises a continuous latent; both make music. The bet they share is not the mechanism — it is the premise that the data has learnable structure. That is the actual through-line, and it survives every architectural fashion cycle.
The boring thing that decides whether it feels magic
Here is the operator-grade takeaway, and it is deliberately unglamorous. How impressive AI is in a domain tracks two things — how good the alphabet is, and how much data exists — and almost never tracks how creative or intelligent the task sounds to a human.
Proteins fell fast because the alphabet is 20 letters and evolution handed over a colossal free dataset. Robots lag, and not because moving is harder than talking. Compare the two piles: Physical Intelligence pre-trained π0 on 10,000 hours of dexterous manipulation data, across 7 robot configurations and 68 tasks. Meta pre-trained its flagship Llama 3 model on 15.6 trillion text tokens. The units do not even match — which is the point. One of those you can scrape; the other you have to physically perform, one robot-hour at a time. The largest open robotics dataset aggregates about a million real trajectories from 34 labs, which is heroic for robotics and a rounding error next to the internet.
The same lesson wearing its first costume: music's constraint was never musicality, it was tokens per second — Suno's CEO named it as the thing they care most about, because the model has to produce music faster than you can listen to it. Alphabet quality and data volume. Everything else is commentary.
This is also why the "which domain falls next?" question has a cheap answer. Not the one that sounds most creative — the one where somebody just found a good alphabet and there is a mountain of examples nobody had bothered to point a model at.
Where the thesis leaks
"Everything is a language" is a genuinely good lens and it is oversold constantly — usually by people repeating a version of this page without the corrections. Three places it breaks, all of which I had to fix in my own draft.
- 1 — Images are the weakest link, not the strongest. The tidy claim is that an image becomes a grid of "visual words" the way sound becomes audio tokens. That conflates two different things. Patches — the famous 16×16 words — are how a transformer reads an image. Discrete visual tokens are real but power a minority of generators; most of today's leading image models create pictures by iterative denoising in a continuous latent space, with no visual vocabulary involved at all. Token-by-token image generation did return at the frontier with GPT-4o's native image mode, but as the exception. Keep the metaphor for perception; drop it for generation.
- 2 — "Predict the next frame" is wrong for the video models people mean. Sora-class systems denoise an entire clip jointly rather than emitting frames in order. The systems that genuinely do predict the next frame are interactive world models — Genie 3 generates navigable 720p worlds at 24 fps, frame by frame, conditioned on what you just did, with no explicit 3D model underneath. That distinction is not pedantry: it is precisely what makes a world model interactive and a video model not. (It is also a live space: OpenAI announced in March 2026 that it is winding down the Sora app.)
- 3 — AlphaGo is not evidence for this thesis. "Go is a language of moves" is a nice line, and AlphaGo's move-prediction network really was trained to predict an expert's next move. But AlphaGo won by searching the future — Monte Carlo tree search over learned position evaluations — not by finishing sentences. Citing it as proof that everything is next-token prediction gets the mechanism backwards.
And one honest correction to the framing as a whole: "one architecture, one objective" was true in 2023 and is not true now. On architecture, 2026's flagship open-weight models are hybrids — Qwen and Moonshot independently landed on interleaving linear-attention blocks with real attention at a ratio of about 3:1, meaning roughly three quarters of the sequence-mixing layers in a current flagship are not attention at all. The defensible sentence is "attention is still the load-bearing primitive, in about a quarter of layers." On objective, the splintering is worse: generation now happens at least four ways (left to right, masked unmasking, diffusion, flow matching), and a large share of headline capability arrives after pretraining — DeepSeek's R1-Zero went from 15.6% to 71.0% on AIME 2024 through reinforcement learning alone, with no supervised fine-tuning. That is a 55-point jump from an objective that is not next-token prediction.
The version that survives the attack is narrower and still remarkable: a single family of sequence models, pointed at the objective of predicting missing pieces, keeps transferring to domains that share nothing but structure. Note what that sentence gives up. The transformer generalized. Next-token prediction did not — wherever the output is continuous and geometric (weather, protein structure, robot motion, video), diffusion and flow matching won.
The last leak is the one that costs money rather than credibility: fluency is not a working model of the thing. The cleanest demonstration is a transformer trained to give turn-by-turn directions across Manhattan — 2.9 million shortest-path sequences over a street graph built from New York taxi pickup and dropoff coordinates. It produced the true shortest path 97% of the time and almost never proposed an invalid next turn. Then researchers reconstructed the map its predictions implied, and got streets whose orientations are physically impossible — labelled north-west while facing east, requiring flyovers over other streets. Force random detours into the route and its rate of valid traversals falls from 0.99 with no detours to 0.69 at a 1% detour rate, 0.08 at 10%, and 0.00 at 50%. A follow-up trained models on orbital trajectories: they predict planetary motion beautifully, and the force law you can extract from them is nonsense. Kepler without Newton. The same signature shows up in genomics, where a 2026 preprint reports a classifier telling AI-generated genomes from real ones at up to 0.97 AUROC, with accuracy climbing the further you get from the seed sequence — locally fluent, globally incoherent — and in AlphaFold 3, which invents confident structure in disordered regions the way a text model invents confident citations.
None of that makes the thesis wrong. It makes it a claim about prediction, not about understanding, and those come apart exactly where you would want to rely on them. A model that speaks a domain fluently has not thereby become trustworthy in it. That gap is where evaluation lives, and it is the whole reason Chapter 25 exists. It is also a live bet with real money on it: Yann LeCun left Meta in November 2025 saying "LLMs basically are a dead end when it comes to superintelligence," founded Advanced Machine Intelligence Labs, and in March 2026 raised $1.03 billion at a $3.5 billion pre-money valuation on that proposition. He may be wrong. He is not obviously wrong, and the market has priced that in.
Do this Monday
This page is a lens, not a tool, so the Monday move is a habit rather than an install.
Take one repetitive thing your business produces and ask the three questions. What is the alphabet — the smallest discrete unit this thing is built from? How much of it do we already have written down? And is what comes next genuinely predictable from what came before? Support macros, outreach sequences, invoice lines, QA steps, shift rosters. If all three answers are good, the domain is already tokenizable and someone will point a model at it — better you than a competitor. If the alphabet is fuzzy or the pile is thin, you have just found the actual bottleneck, and it is a data-collection project, not an AI project. That reframe alone kills more doomed AI initiatives than any vendor evaluation.
Then apply the discount rule to the next headline. When a lab announces that AI has conquered a new field, ask four things: which dialect it actually used, whether the number came from the vendor or an independent evaluator, whether it was validated outside a simulation, and what the denominator was. Five claims in my own draft of this page failed that test — the image-tokens claim, the AlphaGo claim, calling ESM3 a GPT, the esmGFP "58% similar to anything known" line, and the implication that the protein came out in one shot. Every one of them was directionally right and specifically wrong, which is the most expensive kind of wrong. The pattern is real. The retelling is where it gets sloppy.
Related: Ch 10 — the generative pipeline this runs inside · Ch 25 — fluency is not competence · Ch 46 — the same argument for pixels · The Sovereign Stack — the open models you can read the papers for · Glossary
Every figure on this page was verified against a primary source on 2026-07-30, by a six-lane research pass with an adversarial re-check on each numeric claim. Where a system is closed (Suno, Gemini Robotics 2, Sora 2), that is stated rather than papered over. Corrections: v@vladyslavpodoliako.com