"A force is a spring vibration passing on to the next lattice site while fading" — that one line drops the whole thing onto a single sheet
A reader summed up everything through last time in a single line — "A force is just a spring vibration that keeps passing on to the next lattice site while fading, right? That's why it can be computed." This is not a metaphor; it is the literal identity of field theory. This episode adds no new material. It shows how that one line binds the whole series together, with a single correspondence table and a moving spring network — this is the linking episode.
First, the word "field." It's the collective name for something that has a value assigned to every nook of space — electric field, magnetic field, gravitational field, and so on. Drop that into a mechanical image: a network of countless weights arranged on a lattice, with each connected to its neighbors by springs. In physics language this is called coupled harmonic oscillators (weights that swing back and forth on springs, tied to one another), and this is the first-principles definition of a field.
In a familiar picture: the taut surface of a trampoline, a water surface, or the springs of a mattress. Poke it anywhere and the dip passes on to the next neighbor and the next, spreading and weakening. This "poke it and a wave travels" is exactly what it means for a force to act. And:
Written as an equation, the motion of the spring network is exactly the single wave equation \(\partial_t^2 u=c^2\nabla^2 u-m^2u\) (in physics this is called the "Klein–Gordon equation." \(u\) is the size of the sway at each point, the left side is the acceleration of the sway, the first term on the right is "being pulled by the neighbors," and the second term \(m^2u\) is the "on-site spring" that shows up later). In Episode 1 we said "\(F=1/(Cn)^D\) is not a force equation but a ruler." So what was the "force" that the ruler measured actually made of — the answer was this single spring network, and that is this episode.
The phenomena we saw separately across the series all drop onto parts of this spring network. The colors are each episode's — this table is the map of how it "binds the other episodes together."
| Phenomenon seen so far | Its identity in the spring network | Ep. |
|---|---|---|
| The field itself | weights + nearest-neighbor springs arranged on a lattice (coupled oscillators) | all |
| Mediator particle | a ripple traveling through the network (a vibrational mode) | 10 |
| Finite propagation speed = \(c\), light cone | local coupling that travels only to the neighbor in one step | 2, 4 |
| Fading \(1/r^{D}\) | the ripple disperses over the wavefront \(r^{d-1}\) | 1, 10, 11 |
| Massless → \(D=2\) (gravity, electromagnetism) | nearest-neighbor springs only → honest inverse square | 10, 11 |
| Weak force \(D\to\infty\) | an "on-site spring" = mass term pinning each site to its rest position → exponential decay | 10 |
| Strong force \(D\to0\) | nonlinear spring (a flux tube that stays twisted and taut) | 10 |
| \(D=2\) is the blade (stable binding) | geometry in which the spring network vibrates stably = can store a state | 11 |
| Complex dimension, log-periodicity | a hierarchy of discrete scales in the spring network (a self-similar tick) | 8 |
| Formula of information → differential equation | the continuum limit as the lattice spacing \(\to0\) (difference → derivative) | 9 |
"That's why it can be computed" is the deepest line on this sheet. Why can we say so? The spring network is local (each weight is tied only to its neighbors) and finite-speed (one step travels only one lattice's worth). If so, a given weight's "sway at the next instant" is decided by nothing but its own and its neighbors' "sway right now" — this "procedure that computes the next from the now" is called an update rule. Which means:
Local springs (neighbors only) + finite speed + an update rule = exactly the form a computer can advance one step at a time. There is no need to solve the whole thing at once; you just update each point a little from its neighbors' values — this is exactly the computer's specialty. And this is not just an idea but a practice: lattice QCD (carving spacetime into a fine lattice, arranging spring variables on it, and actually running it on a supercomputer to numerically compute the strong force — a vast decades-old field of computational physics) is a concrete example. Episode 2 (what kind of computer to view the universe as) → Episode 4 (the map of how things travel = the causal graph) → Episode 5 (when there is no shortcut and you can only run it) are linked into one by this single line.
If the spring is linear (it tries to return in exact proportion to how far you stretch it = an honest spring), then you can decompose the sway into a clean superposition of sine waves and write down the answer in one shot. But that is a world where the waves merely pass through each other and never collide = a "free field" where forces don't act on one another = a world so easy that nothing interesting happens. Real forces (the confinement of the strong force, for instance) are nonlinear springs (when the sway is large the return twists = the waves affect one another), which can't be cleanly decomposed, and you can only actually run the computer from start to finish. We called this "no-shortcut" property computational irreducibility in Episode 5. So the correct statement is "because updates are local, it can be put on a computer," not "so it solves easily" — being writable as a procedure and there being a shortcut are different things.
"Passing on to the next lattice site" is the finest computational image, but there is a pitfall. Lay down a grid like a go board naively, and preferred directions along the rows/columns and a preferred rest frame are secretly created. Yet the core of relativity is "the laws of physics are the same seen by anyone moving at any speed" (Lorentz invariance), and the lattice breaks this (= a preferred reference frame appears. This is why the simple lattice model was disqualified in Episode 2). Moreover, the operation of making the lattice ever finer to return to smooth space (the continuum limit) works out only in special situations (critical points) (Episode 9). So is the lattice merely a temporarily laid scaffold for computation, or the true foundation of spacetime — no one has settled this yet. This is the "one hole" running through the whole series. The spring network is real as an image, but whether it is the substrate of the world is a bet. We don't fill this in — never say "solved," that is the rule of the whole series.
A force is a vibration that travels to the next neighbor while fading across the lattice's spring network. Mediator particle = the ripple, finite speed = \(c\) = the light cone, fading = \(1/r^D\), mass term = the on-site spring (the weak force's short range), nonlinear spring = the strong force's confinement, stable vibration = the blade of \(D=2\), discrete scales = complex dimension, lattice spacing→0 = the continuum limit where the formula of information becomes a derivative. Episodes 1–11 all drop onto this one sheet.
And because it is local + finite speed + an update rule, it runs on a computer as is — this is the backbone of the series. But runs ≠ solves easily (nonlinear must be run, Episode 5), and whether the lattice is scaffold or foundation is undecided (Lorentz, the continuum limit, Episodes 2, 9). The spring network is real as a picture, but a bet as the substrate — the map was drawn, but no flag was planted.
Print / save as PDF: Ctrl+P (⌘+P on Mac). On screen, "Send a pulse" flicks the spring network, and the mass-term slider shows the distance the wave reaches shrinking. Click "Show the answer" to open each solution.