← Latest papers
🤖 machine learning

Two Speeds of Learning: A Representation-Readout Decomposition of Grokking and Double Descent

This paper introduces a task-agnostic "representation-readout" decomposition framework that explains complex generalization phenomena like grokking and double descent as the result of competing dynamics between gradual representation learning and readout calibration, offering new diagnostic tools to distinguish genuine learning from artifacts of non-standard training.

Original authors: Chi-Ning Chou, Oscar Uzdelewicz, Neng-Chun Chiu, Yao-Yuan Yang, SueYeon Chung

Published 2026-05-27
📖 5 min read🧠 Deep dive

Original authors: Chi-Ning Chou, Oscar Uzdelewicz, Neng-Chun Chiu, Yao-Yuan Yang, SueYeon Chung

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are teaching a student to solve a complex math problem. You have two things to track:

  1. The Student's Understanding: How well they actually grasp the logic and patterns of the math (the "Representation").
  2. The Student's Answer Sheet: How well they fill in the bubbles on the test to get the right grade (the "Readout").

Usually, as a student learns, both their understanding and their test scores improve together. But sometimes, in AI, something weird happens. The AI gets the training data perfect (100% on the homework) but fails the test for a long time, then suddenly "clicks" and gets perfect on the test too. This is called Grokking. Other times, the AI's test score goes up and down like a rollercoaster while it keeps getting better at homework. This is called Double Descent.

This paper argues that these confusing behaviors happen because the "Understanding" and the "Answer Sheet" are learning at two different speeds, and they sometimes get out of sync.

Here is the breakdown of their findings using simple analogies:

1. The Two-Speed Race

The authors split the AI brain into two parts:

  • The Encoder (The Understanding): This part looks at the input and tries to organize it into a clear, logical map. It's like the student trying to understand why the math works.
  • The Readout (The Answer Sheet): This part takes that map and tries to guess the answer. It's like the student filling in the bubbles.

The Discovery:
In "Grokking," the Readout is a cheater. It memorizes the homework answers very quickly. It gets a 100% on the training set, but it's just guessing based on patterns specific to the homework, not the actual math. Meanwhile, the Encoder is working slowly and steadily, actually building a true understanding of the math.

For a long time, the Readout is "train-biased"—it's so focused on the homework that it ignores the test. But eventually, the Encoder finishes building a good enough map. Once the map is clear, the Readout can finally stop cheating and start using the real logic. Suddenly, the test score jumps up. That's the "Grokking" moment.

2. Debunking the "Sleeping Giant" Theory

Before this paper, many scientists thought the Encoder was basically "asleep" or "lazy" during the early stages. They thought the AI was just memorizing, and then suddenly woke up and started learning.

The Paper's Correction:
The authors show the Encoder was never asleep. It was working the whole time, just much slower than the Readout. It's like a student who is slowly reading the textbook while their friend frantically memorizes the answer key. The student is making progress the whole time; they just haven't caught up to the answer key yet.

3. The "Fake" Grokking (Spurious Learning)

The paper also looked at a famous example where an AI seemed to "Grok" on a simple image task (MNIST digits), but it was actually a trick.

The Analogy:
Imagine a student who is given a broken textbook (bad training setup).

  • The Problem: The student's "Understanding" (Encoder) actually gets worse over time because the textbook is confusing.
  • The Result: The "Answer Sheet" (Readout) gets confused too. It tries to force the broken understanding to fit the homework answers.
  • The Illusion: The test score looks like it's delayed, but it's not because the student is finally learning; it's because the teacher (the training setup) was messing with the student.

The authors created a set of "diagnostic tools" (like a mechanic's checklist) to tell the difference between Real Learning and Fake Learning:

  • Real Grokking: The understanding gets better slowly, and the answer sheet eventually catches up.
  • Fake Grokking: The understanding gets worse or stays broken, and the answer sheet is just struggling to fit a square peg in a round hole.

4. Why This Matters

The paper provides a new way to look at AI training. Instead of just watching the "Loss" (how many mistakes the AI makes), which can be confusing and misleading, we can look at the geometry of the AI's mind.

  • Critical Dimension: Think of this as measuring how "tangled" the AI's thoughts are. If the thoughts are a messy knot, it's hard to solve the problem. If they are untangled, the solution is easy. The paper shows that in real Grokking, the knot slowly untangles over time, even if the test score doesn't show it yet.
  • Alignment: This measures if the AI's "Answer Sheet" is looking in the right direction. In fake learning, the Answer Sheet is looking at the wrong things (like noise or random patterns).

Summary

The paper says: Don't panic when the AI's test score lags behind its homework score. It's likely just that the AI is slowly building a real understanding (the Encoder) while its answer sheet (the Readout) is temporarily over-focusing on the homework.

However, if the "understanding" part is actually getting worse or broken, then the AI isn't learning at all—it's just hallucinating a solution. The authors' new tools help us tell the difference between a slow learner and a broken one.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →