Intelligence Is Predictive Compression · Part II of VII
A Thousand Dots and One Line
Database versus geometry, and the exact moment compression becomes intelligence
A database stores observations. A geometry stores the relationship that generated them. The database is a thousand times larger and cannot answer the one question that matters.
This part narrows to a single example and stays there: what happens at the edge of the record, why fitting the past is not evidence of structure, and why you cannot determine what an entity holds by examining its performance on things it has already seen.
Contents
Give an entity one thousand observations.
They arrive as ordered pairs — a thousand historical events, each recorded as a position in the plane. The entity accepts all of them. Storage is not a problem. Fidelity is not a problem. Every point is held exactly as it was given.
Now interrogate it.
What was the 400th observation? It answers instantly and correctly.
What was the 973rd? Correct again.
Were there any observations between the 12th and the 15th? Correct.
What is the mean of the y-values? Correct.
By every test so far, the entity is flawless. It has never once been wrong. If your definition of intelligence involves accuracy, recall, speed, or completeness, this entity is scoring perfectly and you would be entitled to be impressed.
Then ask it one more question.
What is point 3,000?
And the entity — the one that has been perfect for the entire examination — has nothing. There is no 3,000th record. The question is not hard for it. The question is unanswerable by it, in the same way that a photograph cannot be asked what happened the following Tuesday. Its competence terminated at observation one thousand and it did not terminate gradually. It fell off a cliff.
This is the boundary. Everything in this series happens on one side of it or the other.
Two ways of keeping the past
There are exactly two things you can preserve when you look at a thousand observations, and they are not variations on each other. They are different in kind.
You can preserve the observations. Each one, individually, as an item. The record grows linearly with what you have seen. Retrieval is exact. Nothing is inferred, so nothing can be inferred wrong. Call this a database.
You can preserve the relationship that generated the observations. Not the items — the rule connecting them. The representation does not grow with the number of observations, because it was never storing observations. Call this a geometry.
If the thousand points happened to lie along
y = 2x + 5
then the database holds a thousand facts and the geometry holds one. The database is larger by a factor of about a thousand. And yet only one of them can answer the question about point 3,000, and it is not the one holding a thousand times more information.
That sentence should be uncomfortable. It says that having more of the past can make you worse at the future. It says the entity that discarded 99.9% of what it was given is the one that can still speak when the records run out.
The database is not defective. It is doing exactly what it was built for, perfectly. It is simply built for a different question than the one that matters.
Where the discomfort actually lives
Most people, reading the above, quietly assume the geometry is doing something like clever interpolation — filling gaps between known points. It is not, and the difference is the whole argument.
Interpolation stays inside the territory. If you know points at x = 1 and x = 3, guessing at x = 2 is a modest act. You are surrounded on both sides by evidence.
Point 3,000 is not surrounded by anything. It is two thousand units past the last thing anyone ever saw. There is no neighboring evidence to lean on. The only thing standing between the entity and total ignorance is the claim that a relationship observed inside the data continues to hold outside it.
That claim is not free. It is not derivable from the data. David Hume noticed this in 1739 and nobody has closed the gap since: no finite record of the past logically entails anything about the future. The geometry does not prove point 3,000. The geometry bets on point 3,000.
And this is precisely why the extrapolation is where intelligence becomes visible. Anyone can be right about what they have already seen. Being right about what you have never seen requires having extracted something real — a structure that was genuinely in the world rather than an artifact of the sample. The bet is what exposes whether the compression found the generator or merely traced the output.
There is a technical name for what happens when a model traces output instead of finding the generator. It is called overfitting, and its signature is exactly this: excellent performance on the record, collapse beyond it. A model with enough parameters can pass through every one of a thousand points and still be worthless at 1,001. Neural networks can be trained to fit randomly assigned labels perfectly — labels with no structure in them at all — which shows that fitting the past is not by itself evidence that any structure was found.1
Fitting is not learning. Fitting is memorizing with extra steps.
Prediction is where memorization can no longer hide.
Vector, not raster
There is a useful picture from graphics, and it is worth taking exactly as far as it goes and no further.
A raster image is a grid of pixels. Every pixel is a stored fact. Enlarge it and you do not get more detail — you get bigger pixels, because there was never anything there but the pixels. The image knows what it was told and nothing else.
A vector image stores relationships: this curve, these control points, that stroke width. Enlarge it a thousandfold and the edges stay clean, because the representation was never a record of appearance. It was a description of construction. You are not zooming into stored detail; you are re-deriving detail from a rule.
That is the difference between a database and a geometry, and it is a good picture because it makes vivid the thing that surprises people — the smaller file is the one that survives magnification.
Where the analogy ends: vector graphics are exact and closed-form. The learned geometries we care about — in brains, in models — are neither. They are approximate, high-dimensional, and messy. Do not walk away thinking that a language model contains a tidy curve. It does not. What it contains is the thing the analogy is pointing at: structure preserved without the examples being preserved.
What “geometry” is doing in this argument
I am using the word deliberately and I want to be careful about how far the claim reaches.
In machine learning, the standard framing is the manifold hypothesis: real-world high-dimensional data does not fill its space but concentrates near a lower-dimensional surface embedded in it.2 Images of faces occupy a vanishingly thin sliver of the space of all possible pixel arrangements. Grammatical English occupies a vanishingly thin sliver of the space of all possible token sequences. Learning, on this view, is the discovery of that sliver — finding the low-dimensional shape that the data actually lives on.
There is real evidence that learned systems build such structure rather than lookup tables. A transformer trained only to predict legal moves in Othello — never told the rules, never shown a board — develops an internal representation of the board state that can be probed and, more tellingly, intervened on: change the internal representation and the model’s subsequent predictions change accordingly, as though you had moved a piece.3 Language models trained on text develop identifiable linear representations of spatial and temporal position, with individual neurons tracking latitude, longitude, and date.4 Nobody put a map in there. The map was the cheapest way to predict the next token.
And there is real evidence on the other side, which belongs in the same paragraph. A transformer trained on New York taxi routes scores well on standard world-model diagnostics while holding an internally incoherent map — reconstruct its implicit street network and you find impossible configurations, streets flying over each other. Introduce a detour at one percent of steps, replacing the model’s chosen turn with a different legal turn, and the fraction of its routes that remain valid falls from 0.99 to about 0.69.5 The geometry was real enough to predict the training distribution and not real enough to survive a small perturbation.
The same study contains the sharpest version of the warning. A sibling model trained on random walks rather than shortest paths does not degrade under the same detours at all. Two models, indistinguishable on the training distribution, holding structures of completely different quality — and nothing about their performance on the record revealed which was which.
Both findings are the same finding. A learned geometry is a bet about structure, and bets can be well-placed or badly-placed. The Othello model’s bet was good. The shortest-path taxi model’s bet was locally good and globally wrong. The only way to tell them apart was to ask about something that was not in the record.
Which is the point. Not “models have world models.” The point is: you cannot determine what kind of structure an entity holds by examining its performance on the past.
The moment of transition
Return to the thousand points and watch the transition happen in slow motion.
Before the future question, the compression from a thousand points to one equation is an engineering result. It saves storage. It is faster to transmit. It is easier to write down. Nothing about it demands the word intelligence — it is a tidier way of holding what you already had, and you could reasonably describe it as filing.
After the future question, the same object is doing something categorically different. It is producing a claim about a region of reality that has left no trace in the record. It is not retrieving. It is generating a commitment that the world can falsify.
Nothing about the equation changed. What changed is what we asked of it.
Before the future question, compression is efficient storage. After the future question, we begin calling it intelligence.
This means intelligence is not a property you can find by inspecting a representation. It is a property that only shows up in a particular kind of encounter — the encounter between a compressed structure and something it has not seen. You can hold the equation in your hand and not know whether it is intelligent. You find out when x = 3,000.
Memory is evaluated against the past. Intelligence is evaluated against the future.
Why this reframes the entire question of “how much does it know”
Once the boundary is drawn this way, a whole category of common arguments dissolves.
How many facts does it store? — a question about the database. Interesting for a search engine; nearly irrelevant here.
How large is it? — a question about capacity to remember, which as we saw is the thing that delays compression rather than causing it. Capacity is a budget for not-yet-generalizing.
Did it get the 400th observation right? — a question inside the record. It tests fidelity, not structure.
Can it be caught reproducing training data verbatim? — a real and important question about copyright, privacy, and safety. It is not a question about intelligence, because it is a question about the database portion.
Every one of these can be answered impressively by an entity with no predictive structure whatsoever. And every one of them can be answered poorly by an entity with excellent predictive structure — a physicist who cannot remember the date of a conference is not thereby less able to predict a scattering cross-section.
The only question that separates the two is the one aimed past the edge of the record.
The picture to keep
A thousand dots on a plane.
Someone draws a line through them, and the dots become unnecessary. Not compressed — unnecessary. The line does not contain the dots; it contains the reason the dots were where they were.
Then the line is extended past the last dot, into the region where nothing has ever been observed, and it makes a claim.
The claim is checkable. That is the whole thing. The line has committed to a value at x = 3,000, and the world will eventually supply one, and the two numbers will either agree or they will not.
The database ends where its records end. The geometry does not.
The crossing of that boundary is where intelligence becomes visible. Not where it is generated — where it becomes visible. Those are different places, and confusing them is the most common error in this entire subject.
Because the natural next question is: where do we look to see it?
Almost everyone looks in the wrong place.
Sources
1. Chiyuan Zhang, Samy Bengio, Moritz Hardt, Benjamin Recht, and Oriol Vinyals, “Understanding Deep Learning Requires Rethinking Generalization,” ICLR 2017, arXiv:1611.03530. Networks reached 100% training accuracy on randomly labeled CIFAR-10.
2. Yoshua Bengio, Aaron Courville, and Pascal Vincent, “Representation Learning: A Review and New Perspectives,” IEEE Transactions on Pattern Analysis and Machine Intelligence 35, no. 8 (2013): 1798–1828, arXiv:1206.5538. See also Charles Fefferman, Sanjoy Mitter, and Hariharan Narayanan, “Testing the Manifold Hypothesis,” Journal of the American Mathematical Society 29, no. 4 (2016): 983–1049 — which supplies a statistical test with sample-complexity guarantees, not a proof that any particular dataset lies on a manifold.
3. Kenneth Li et al., “Emergent World Representations: Exploring a Sequence Model Trained on a Synthetic Task,” ICLR 2023 (oral), arXiv:2210.13382.
4. Wes Gurnee and Max Tegmark, “Language Models Represent Space and Time,” ICLR 2024, arXiv:2310.02207.
5. Keyon Vafa et al., “Evaluating the World Model Implicit in a Generative Model,” NeurIPS 2024, arXiv:2406.03689.
2 thoughts on “A Thousand Dots and One Line”