This page assumes nothing. Before you can read the parent note Network Flow (parent), every squiggle it uses is built here from a picture. Read top to bottom; each block earns the next.
Everything below lives on one drawing: dots joined by arrows, water flowing left-to-right from a tap s into a bucket t.
Look at that figure. A dot is a place. An arrow is a pipe that only lets water go the way it points. That is the entire vocabulary — now we name each part precisely.
The letters u and v are just stand-ins for any two dots — like "person X and person Y". When you see (u,v), read it aloud as "some arrow from a dot I'll call u to a dot I'll call v."
The notation c(u,v) reads: "the capacity functionc, asked about the specific pipe from u to v." A function is just a lookup table: you hand it a pipe, it hands you a number.
In figure s02 the middle dot has 3 units arriving and must send 3 out (say 2+1). That balance is conservation. The symbol ∑ (capital Greek "sigma") just means "add up all of these" — here, add every flow arriving, then every flow leaving, and demand the two totals match.
The bars ∣⋅∣ here do not mean absolute value — they are just traditional notation for "size / value of the flow". This single number ∣f∣ is the thing the whole topic wants to make as big as possible.
Figure s03 draws a dashed wall. The amber arrows crossing left-to-right count toward c(S,T); the cyan arrow crossing right-to-left is free. The symbol u∈S reads "u is a member of team S" (∈ = "belongs to").
Once some flow is running, we redraw the network to show what moves are still legal. This redraw is the residual graph, and it powers every algorithm in the parent note.
An augmenting path is any route from s to t using only arrows with cf>0. Its bottleneck is the smallest cf along it — the most water that whole route can carry.
We use it to compare algorithms: Ford–Fulkerson's speed depends on the capacity values (O(E⋅∣f∗∣)), while Edmonds–Karp's does not (O(VE2)) — a big deal when capacities are huge.
Read the map top-down: dots and arrows come first, then labels (capacity, flow), then the two headline objects — max flow and min cut — which the theorem glues together. The augmenting-path branch relies on BFS and leads toward Edmonds-Karp-style methods and Dinic's Algorithm. The theorem itself is a special case of a broader duality: see Linear Programming Duality and Menger's Theorem, and it underpins Bipartite Matching.