Before you can read the parent note, you need to own every symbol it throws at you. We build each one from a picture, in the order that lets the next one make sense.
The picture: think of a hilly terrain. Your horizontal position needs two numbers (east–west, north–south) → that is R2. The height of the ground at that position is one number → that is R. So a terrain is exactly f:R2→R.
R = "all real numbers" — every point on an infinite number line.
Rn = "a list of n real numbers" — a position needing n coordinates.
Why the topic needs it. In machine learning f is the loss — a number saying how wrong the model is. The n inputs are the model's tunable parameters. We want the position of lowest height (least wrong). See Loss Landscape Visualization.
The picture: on the terrain, x is where you are standing (a pin on the map — exactly the orange dot from §1's figure). Its two numbers are how far east and how far north. x∗ is a marked pin — the pass or valley we are investigating.
Why the topic needs it. We cannot write "the flat point" a million different ways for a million-parameter network, so we bundle all coordinates into one bold letter and star the interesting one.
Why the limit? We want the slope at a single instant, not averaged over a chunk. The gap h is the chunk width; sending h→0 (the symbol lim means "the value this creeps toward") collapses the chunk to a point. That is the only tool that gives an instantaneous rate — see Taylor Series.
Sign story (all cases):
f′(x)>0 → ground rises to the right (uphill).
f′(x)<0 → ground falls to the right (downhill).
f′(x)=0 → flat — the ground momentarily neither rises nor falls. This is the flatness the whole topic hunts for.
Back to the full world: f:Rn→R with a bold input x. With n inputs there is no single slope: the ground can rise going east yet fall going north. We measure one direction at a time.
The picture: slice the terrain with a vertical wall running exactly east–west through your feet. On that wall's edge you see an ordinary 1-D curve. Its slope is ∂x1∂f.
Why an arrow? Each partial is one component of a total slope. Combined, they form the single direction of fastest increase — exactly what you'd need to climb fastest, or (with a minus sign) descend fastest.
Before we measure curvature, let us pin down exactly what the words "minimum" and "maximum" mean, so "bowl" and "dome" are not just pictures.
The picture: "local" means look only close by. A valley floor may not be the deepest valley on Earth, but among its own neighbours it is lowest — that is enough to be a local minimum. The three shapes in the next section (bowl, dome, pass) are exactly these three cases.
For many inputs (back to bold x∈Rn), curvature also depends on direction, so we need a whole grid of second derivatives.
Why n×n? Every pair of directions has a bending relationship, and there are n×n ordered pairs. The diagonal (i=j) holds pure up/down bending along each axis; off-diagonal entries hold twist. See Second-Order Optimization.
The Hessian is a table of numbers; we need to squeeze one verdict out of it.
Why scan all d? If some direction gives a negative value (an escape route downhill) while another gives positive, that mix is the saddle signature.
Why eigenvalues instead of the raw table? They are the cleanest summary of curvature — one number per independent direction. Their signs give the whole verdict:
All λi>0
curves up everywhere
minimum (bowl)
All λi<0
curves down everywhere
maximum (dome)
Mixed signs
up some ways, down others
saddle (pass)
Some λi=0
flat in a direction
degenerate — look higher
This is the engine of the classification table in the parent note. Bowls are the friends we chase in Convex Optimization; saddles are the traps escaped by Momentum and Adam.
The left branch (slopes → gradient) finds where the flat spots are. The right branch (bending → Hessian → eigenvalues) tells us which kind of flat spot. The topic is exactly these two branches meeting at the verdict box.