Act 01 · Text becomes numbers 2:30 Unknown words and secret IDs

What happens to a word it's never seen.

Byte-fallback guarantees any string can be tokenized — nothing is unrepresentable, some things are just expensive.

Video rendering soonThe cinematic render for this episode is being generated. The article, transcript and key ideas are all here now.

Key ideas

  • The one idea — Byte-fallback guarantees any string can be tokenized — nothing is unrepresentable, some things are just expensive.
  • How it is shown — Keyboard mash falling down the cascade: menu word → pieces → characters → raw bytes.
  • The trap to avoid — "It tokenized my word" ≠ "it knows my word" — arrival as shards is arrival, not understanding.
  • What it sets up — Whether shards add up to meaning depends on training.

Old language systems had a panic button: any word not on the list became 'unknown,' and the information vanished. Modern AI dug a floor under the menu — bytes.

The one idea

Byte-fallback guarantees any string can be tokenized — nothing is unrepresentable, some things are just expensive.

Mash your keyboard. It still tokenizes. Nothing you can type is outside this system — and the reason is a safety net at the bottom of the menu. Old language systems had a word list and a panic button. Any word not on the list became UNK — unknown — a featureless shrug. One typo, one rare name, and the information simply vanished. Modern tokenizers dug a floor under the menu: bytes. All text is bytes — and there are only two hundred fifty-six possible bytes. Put all two hundred fifty-six in the menu, and no string in any language, alive or invented, can ever be unrepresentable. So the chopper works down a cascade. Whole word on the menu?

How it works — the demo

Keyboard mash falling down the cascade: menu word → pieces → characters → raw bytes.

One token. No? Familiar pieces. Still no? Characters. Still no? Raw bytes. "Flurbonium" — a word I invented — comes out as flur, bon, ium. Keyboard mash comes out as bytes. Everything tokenizes. The net isn't free.

The trap to avoid

"It tokenized my word" ≠ "it knows my word" — arrival as shards is arrival, not understanding.

Why it matters — and what’s next

Whether shards add up to meaning depends on training.

Falling to the floor is expensive: a rare name can cost ten tokens where "the" costs one. And you already know who pays that bill — underrepresented languages live near the floor. It also means the model can eat things that aren't language at all: emoji, corrupted files, binary dumps. The chopper will chop anything. Whether the model can do anything useful with the shards is an entirely different question. The trap: "it tokenized my word" does not mean "it knows my word." Arriving as five shards is arrival, not understanding. Whether those shards add up to meaning depends on what training did with them — which is exactly where this act is headed. So: nothing is unrepresentable — some things are just expensive. One piece of bookkeeping remains, and then the chopper's story is complete: every chunk on the menu has a secret number. Next episode, you read your first prompt the way the model does.

Your rare name doesn't break the AI. It's just expensive — it can cost ten tokens where 'the' costs one. And arriving as shards isn't the same as being understood.

This is one short episode in AI: Zero → Frontier, a step-by-step climb through how AI actually works. Each episode builds only on the ones before it.

Full transcript 2:30 of narration

Mash your keyboard. It still tokenizes. Nothing you can type is outside this system — and the reason is a safety net at the bottom of the menu.

Old language systems had a word list and a panic button. Any word not on the list became UNK — unknown — a featureless shrug. One typo, one rare name, and the information simply vanished.

Modern tokenizers dug a floor under the menu: bytes. All text is bytes — and there are only two hundred fifty-six possible bytes. Put all two hundred fifty-six in the menu, and no string in any language, alive or invented, can ever be unrepresentable.

So the chopper works down a cascade. Whole word on the menu? One token. No? Familiar pieces. Still no? Characters. Still no? Raw bytes. "Flurbonium" — a word I invented — comes out as flur, bon, ium. Keyboard mash comes out as bytes. Everything tokenizes.

The net isn't free. Falling to the floor is expensive: a rare name can cost ten tokens where "the" costs one. And you already know who pays that bill — underrepresented languages live near the floor.

It also means the model can eat things that aren't language at all: emoji, corrupted files, binary dumps. The chopper will chop anything. Whether the model can do anything useful with the shards is an entirely different question.

The trap: "it tokenized my word" does not mean "it knows my word." Arriving as five shards is arrival, not understanding. Whether those shards add up to meaning depends on what training did with them — which is exactly where this act is headed.

So: nothing is unrepresentable — some things are just expensive. One piece of bookkeeping remains, and then the chopper's story is complete: every chunk on the menu has a secret number. Next episode, you read your first prompt the way the model does.

TokenizationByte FallbackOut-of-VocabularyCost