Foundations — Wafer-scale engines (Cerebras-style)
This page assumes nothing. If the parent note wrote a symbol, we build it here from a picture first, then say why the topic needs it. Read top to bottom: each idea is a brick for the next.
1. The wafer, the die, and the dicing streets

The picture: look at the figure. The circle is the wafer. The grid of blue squares are dies. The gray lanes between them are scribe lines. A normal factory saws along those gray lanes and sells the blue squares separately.
Why the topic needs this: the entire trick of a WSE is to not cut and to add metal wiring across the gray lanes so all the blue squares become one connected chip. You cannot understand that sentence without these four words.
2. Area, and why "how big" is a number ()
The picture: in the figure above, is the size of one blue square. A whole-wafer die is one enormous square filling the plate — roughly .
Why we need it: bigger means the chip covers more of the wafer, which means it is more likely to swallow a random flaw. Area is the knob that turns yield from "easy" to "impossible". Hold this thought — we make it exact in §5.
3. Defects and defect density ()

The picture: the red dots scattered on the wafer are defects. They land in random spots, independently — one defect does not "know" where the others are. Count the dots in any box, average over the whole wafer, and that average is .
Why we need it: tells us how hostile the wafer is. A small die might dodge all the dots; a giant die almost certainly catches several. To turn "almost certainly" into a real probability we need one mathematical tool — the Poisson distribution — next.
4. Randomness that adds up: the Poisson idea (, mean)
Why this exact tool? We have random dots (§3) sprinkled independently over an area (§2). The one probability recipe built precisely for "independent rare events scattered over space or time" is the Poisson distribution. We do not reach for a bell curve or a coin-flip formula because those describe different situations; Poisson is the one that answers "given an average count , what is the chance I see exactly events?"
Why this matters here: for a die to work, it needs zero killing defects, i.e. . Everything about wafer yield collapses to one question: what is ? We answer it after meeting .
5. The number and the exponential

The picture: the curve in the figure is . At it is (100% — certain). By it is . By it is under . It falls off a cliff.
Why this tool? Plug into the Poisson formula: The whole messy formula collapses to a clean exponential. And — the average defects in a die — is just density times area: . So the probability a die is perfect is:
Reading the picture as physics: as grows toward a whole wafer, becomes a big number, and the curve tells us dives toward . That is the mathematical reason a monolithic whole-wafer chip "should" never work — and why the topic needs redundancy to escape it.
6. Fractions, thresholds, and over-provisioning (, , )
The picture: imagine building light bulbs knowing a fraction will be duds. Working bulbs . To end up with at least lit, you need to build extra:
Why the topic needs it: WSEs stop chasing a perfect wafer (impossible, §5) and instead over-provision — build spare cores by the factor and route around the dead ones. This single inequality is the whole reason wafer-scale is buildable. See Yield & Defect Density Models.
7. Cores, SRAM, routers, and the mesh

The picture: the grid of squares is the mesh. Each square holds a core + its SRAM + a router. Arrows link only touching neighbours — no long wires jump across the grid. A message from a far corner hops square to square.
Why the topic needs it: the mesh explains both WSE strengths — high bandwidth (all links run at once, §8) and low latency for nearby traffic — and its weakness (far-apart cores need many hops). This is the Network-on-Chip (NoC) & Mesh Topologies idea, and it is why weight-stationary Systolic Arrays & TPUs-style dataflow (each core keeps its weights, activations stream past) fits so well.
8. Bandwidth, latency, and why they add up (, hops)
Why they add (the key move): in a mesh, links run in parallel — while one core sends left, thousands of others send too, all at once. So total bandwidth is the sum: With cores each pushing : (Here .)
Why the topic needs both: the parent's whole argument is that off-chip links waste time and energy. Bandwidth shows the mesh moves ~1000× more data than a GPU link; latency shows a neighbour hop is ~1 ns versus microseconds across a network. This is the flip side of Dennard Scaling & the Memory Wall — compute grew, off-chip data movement did not.
9. Where these pieces still leave the wafer
Prerequisite map
This map feeds directly into Wafer-scale engines (Cerebras-style). Compare related integration ideas in Chiplets & 2.5D/3D Integration, and read the Hinglish version if that helps.
Equipment checklist
Cover the right side and answer out loud before revealing.