Bring the mental model from Scaled Dot-Product Attention & Transformer Layers; this page will reuse it instead of restarting from zero.
Scaling Laws & Emergent Abilities
Empirical power laws that predict how loss and capability improve with parameters, data, and compute, and how to choose compute-optimal training runs.
01
Intuition
Build the mental picture first so the rest of the page has something to attach to.
If you train a family of models the same way (same architecture class, data pipeline, optimizer recipe), then "bigger model" and "more data" usually give you predictably better loss.
Scaling laws turn that predictability into a planning tool. Instead of guessing, you can fit a curve from small runs, then forecast how far a larger run will go, and how to spend a fixed compute budget:
- Should we buy more parameters or more tokens?
- If we only get one big run, what is the compute-optimal choice?
- Why do some task behaviors look like they "appear suddenly"?
The key mindset is: scaling laws are not a proof about intelligence. They are an empirical control system for allocating compute.
Copy-only prompts — each action copies a page-grounded prompt to your clipboard. Nothing is sent by this site.
02
Math
Translate the story into symbols, assumptions, and a derivation you can inspect.
Power-law loss scaling
A common empirical form for test loss L is:
where:
- N is parameter count,
- D is number of training tokens (or examples),
- α,β>0 are exponents you fit from data,
- L∞ is the irreducible loss floor for the dataset/model class.
On a log-log plot, N−α and D−β look like straight lines. That's why power laws are useful: they extrapolate smoothly.
Compute-optimal allocation (Chinchilla-style rule of thumb)
Very roughly, training compute scales like:
Under this constraint, minimizing the loss above typically yields a near-linear rule:
Interpretation: for a fixed compute budget, don't overscale parameters without scaling data too, or you spend compute learning the same patterns repeatedly.
"Emergent abilities" as sharp transitions
When you measure a capability with a thresholded metric ("accuracy above 50%", "passes a benchmark"), smooth curves in loss can turn into sharp-looking transitions. The underlying performance can still be continuous.
Copy-only prompts — each action copies a page-grounded prompt to your clipboard. Nothing is sent by this site.
03
Code
Keep the implementation aligned with the notation so the algorithm is legible.
import numpy as np
# A toy scaling law: L(N,D) = L_inf + a N^-alpha + b D^-beta
L_inf, a, b = 1.5, 1.0, 1.0
alpha, beta = 0.07, 0.095
def loss(N, D):
return L_inf + a * N**(-alpha) + b * D**(-beta)
C = 1e12 # compute budget in arbitrary units ~ N*D
Ns = np.logspace(7, 10, 40) # 10M..10B params
best = None
for N in Ns:
D = C / N
L = loss(N, D)
if best is None or L < best[0]:
best = (L, N, D)
L, N, D = best
print("best loss:", round(float(L), 4))
print("N:", f"{N:.2e}", "D:", f"{D:.2e}", "D/N:", round(float(D / N), 2))
Copy-only prompts — each action copies a page-grounded prompt to your clipboard. Nothing is sent by this site.
04
Interactive Demo
Use direct manipulation to connect the explanation to a moving system.
Live Concept Demo
Explore Scaling Laws & Emergent Abilities
The stage is code-native and interactive. Use it to test the explanation against the mechanism.
Manipulate one control and predict the visible change.
Choose what to inspect in Scaling Laws & Emergent Abilities. This shared fallback is an observation guide, not evidence of learning.
Use the demo to explore how loss changes as you scale N and D, and why compute-optimal frontiers often prefer more data than you expect.
Copy-only prompts — each action copies a page-grounded prompt to your clipboard. Nothing is sent by this site.
Concept: Scaling Laws & Emergent Abilities
What is the smallest example that makes Scaling Laws & Emergent Abilities click without losing the math?
Object contextScaling
concept:scaling/scaling-lawsScaling Laws & Emergent Abilities
What is the smallest example that makes Scaling Laws & Emergent Abilities click without losing the math?
Start with the prediction checkpoint, then compare the reveal to the mental model.
Take this moveStudy modes
Keep the object fixed; change the lens.Route back through the notebook
Carry the same object through intuition, math, code, and demo.
Empirical power laws that predict how loss and capability improve with parameters, data, and compute, and how to choose compute-optimal training runs.
The next edge should feel earned: use the demo prediction here before following RLHF: Reward Modeling + KL-Regularized Policy Optimization.
After The First Pass
Turn the concept into an inspected object.
The lower panels are one second act: keep the object fixed, inspect it visually, check source boundaries, practice transfer, then attach the research question.Mechanism Storyboard
See the idea move before the page explains it
Empirical power laws that predict how loss and capability improve with parameters, data, and compute, and how to choose compute-optimal training runs.

Start with the picture, metaphor, or geometric mechanism.
Before reading further, choose the kind of change Scaling Laws & Emergent Abilities should make visible.
Visual Inquiry
Make the image answer a mathematical question
Empirical power laws that predict how loss and capability improve with parameters, data, and compute, and how to choose compute-optimal training runs.
Which visible object should carry the first intuition?
Pick the cue that should make Scaling Laws & Emergent Abilities easier to reason about before the page gives the answer.
Source Grounding
Canonical references for the mechanism on this page.
What is the smallest example that makes Scaling Laws & Emergent Abilities click without losing the math?
concept:scaling/scaling-lawssources: kaplan-2020-scaling-laws, hoffmann-2022-chinchilla
Open the closest source note before trusting the local explanation.
2 selected-object sources shown first; 2 references total.
Audit the claim boundary, then ask from the same selected object.
Grounds empirical power-law fits between model size, data, compute, and language-model loss.
Kaplan et al. study language-model cross-entropy loss and report power-law scaling with model size, dataset size, and training compute. Hoffmann et al. train over 400 models and find that...
This checks empirical pretraining scaling and training-compute allocation, not a proof of intelligence, universal exponents across architectures/datasets, inference-time compute, data-qua...
Grounds compute-optimal scaling as a balance between parameter count and training tokens.
Kaplan et al. study language-model cross-entropy loss and report power-law scaling with model size, dataset size, and training compute. Hoffmann et al. train over 400 models and find that...
This checks empirical pretraining scaling and training-compute allocation, not a proof of intelligence, universal exponents across architectures/datasets, inference-time compute, data-qua...
Claim Review
Empirical power laws that predict how loss and capability improve with parameters, data, and compute, and how to choose compute-optimal training runs.
What is the smallest example that makes Scaling Laws & Emergent Abilities click without losing the math?
concept:scaling/scaling-lawssources: kaplan-2020-scaling-laws, hoffmann-2022-chinchilla
Treat every claim as provisional until source support and a local witness agree.
1 structured claim check on this concept.
Run the prediction or practice transfer before asking for a grounded review.
Publisher-side editorial review is not independent replication. Claims without it still need exact source-support review. 2 references and 3 local witnesses are available for inspection.
Kaplan et al. study language-model cross-entropy loss and report power-law scaling with model size, dataset size, and training compute. Hoffmann et al. train over 400 models and find that compute-optimal tra...
This checks empirical pretraining scaling and training-compute allocation, not a proof of intelligence, universal exponents across architectures/datasets, inference-time compute, data-quality effects, downst...
Checked arXiv abstracts: Kaplan et al. support cross-entropy loss power laws over model size, dataset size, and training compute; Hoffmann et al. support equal scaling of model size and token count for compute-optimal fixed-budget training. Local math/code/demo instantiate only this scoped pretraining loss and N-D budget view.
Reviewer: codex; reviewed 2026-05-20Practice notebook
Use the idea, then test it somewhere new
Empirical power laws that predict how loss and capability improve with parameters, data, and compute, and how to choose compute-optimal training runs.
What is the smallest example that makes Scaling Laws & Emergent Abilities click without losing the math?
concept:scaling/scaling-lawssources: kaplan-2020-scaling-laws, hoffmann-2022-chinchilla
Use one state from Scaling Laws & Emergent Abilities to explain what changes, why it changes, and which assumption the explanation needs.
No learner move yet; no learning state is inferred.
Write first, use only the help you need, then try a new case without it.
Use one state from Scaling Laws & Emergent Abilities to explain what changes, why it changes, and which assumption the explanation needs.
Reveal when your model needs a nudge.
Reveal when your model needs a nudge.
Reveal when your model needs a nudge.
Write an attempt before asking the companion.
0 of 3 progressive hints opened.
This draft and any AI response do not establish mastery; a later unassisted case can.
- ObjectConceptScaling Laws & Emergent Abilities
- PredictBefore revealScaling Laws & Emergent Abilities prediction
- WitnessCompare codeScaling Laws & Emergent Abilities code witness 1
- RoomAsk groundedChecking local snapshot
Research Room
Attach the question to an exact object
Pick the concept, equation, source, code witness, claim, misconception, or demo state before asking for help. The handoff stays grounded to that object.Open the draft below to save one note and next action in this browser.
Scaling Laws & Emergent Abilities
What is the smallest example that makes Scaling Laws & Emergent Abilities click without losing the math?
These are fixed, deterministic perspectives derived from the selected object. They do not represent people, community contributions, or independent review.
Source ids kaplan-2020-scaling-laws, hoffmann-2022-chinchilla must support the exact object, not just the surrounding topic.
Treat this as a mechanism object: connect the definition to one equation, code witness, or demo before broadening the discussion.
Ask the learner to perturb one representation, then check whether the same invariant survives in math, code, and demo.
The learner can state the mechanism in their own words
Local action draftNo local draft saved yetExpand only when ready to capture one local next action
This draft stays locally in this browser for concept:scaling/scaling-laws.
- Source ids to inspect: kaplan-2020-scaling-laws, hoffmann-2022-chinchilla
- Definition, prerequisite, and contrast concept links
- The equation or code witness that makes the concept operational
- One demo state that shows the invariant instead of a slogan
- The learner can state the mechanism in their own words
- The learner can name the prerequisite that would repair confusion
- The learner can predict how the mechanism changes under one perturbation
I am working in Continuous Function's research reading room. Object: concept - Scaling Laws & Emergent Abilities Object key: concept:scaling/scaling-laws Context: Scaling Anchor id: concept/concept-notebook/scaling/scaling-laws Open question: What is the smallest example that makes Scaling Laws & Emergent Abilities click without losing the math? Evidence to inspect: - Source ids to inspect: kaplan-2020-scaling-laws, hoffmann-2022-chinchilla - Definition, prerequisite, and contrast concept links - The equation or code witness that makes the concept operational - One demo state that shows the invariant instead of a slogan Deterministic role lenses for this object: - Boundary: fixed perspectives, not people, community contributions, or independent review - Source-checking summary: Treat this as a mechanism object: connect the definition to one equation, code witness, or demo before broadening the discussion. - Proposed experiment: Ask the learner to perturb one representation, then check whether the same invariant survives in math, code, and demo. - Teach/transfer move: Turn the mechanism into one sentence that predicts a neighboring concept. - Assumptions: - Source ids kaplan-2020-scaling-laws, hoffmann-2022-chinchilla must support the exact object, not just the surrounding topic. - The stable content-object key lets local drafts, prompts, and route memory attach without changing the source page. - The concept explanation is local atlas prose until checked against its math, code, and source support. - Prerequisite gaps should become a repair route, not a reason to leave the object vague. - Role-lens requests: - Learner: ask for "Ask what would make "Scaling Laws & Emergent Abilities" feel predictable rather than familiar." | assumption: Source ids kaplan-2020-scaling-laws, hoffmann-2022-chinchilla must support the exact object, not just the surrounding topic. | next action: The learner can state the mechanism in their own words - Researcher: ask for "Source ids to inspect: kaplan-2020-scaling-laws, hoffmann-2022-chinchilla" | assumption: The stable content-object key lets local drafts, prompts, and route memory attach without changing the source page. | next action: The learner can name the prerequisite that would repair confusion - Experimenter: ask for "Choose one variable or condition to perturb before asking for an explanation." | assumption: The concept explanation is local atlas prose until checked against its math, code, and source support. | next action: The learner can predict how the mechanism changes under one perturbation - Professor: ask for "Find the smallest transferable rule a learner could reuse without the AI." | assumption: Prerequisite gaps should become a repair route, not a reason to leave the object vague. | next action: Teach or transfer: Turn the mechanism into one sentence that predicts a neighboring concept. What would resolve this: - The learner can state the mechanism in their own words - The learner can name the prerequisite that would repair confusion - The learner can predict how the mechanism changes under one perturbation Answer as a careful research tutor: stay source-grounded, separate verified evidence from assumptions, name the relevant math objects, and end with one next action. Current deterministic role lens for this object: - Role lens: Learner - Evidence request: Ask what would make "Scaling Laws & Emergent Abilities" feel predictable rather than familiar. - Assumption to keep visible: Source ids kaplan-2020-scaling-laws, hoffmann-2022-chinchilla must support the exact object, not just the surrounding topic. - Proposed experiment: Ask the learner to perturb one representation, then check whether the same invariant survives in math, code, and demo. - Next action: The learner can state the mechanism in their own words
concept/concept-notebook/scaling/scaling-laws
concept:scaling/scaling-laws