Plain-English statement
The Kantorovich cost is the smallest extended expected cost among all couplings of two measures.
Mathematical statement
T_c(mu,nu) = inf_{gamma in C(mu,nu)} integral c(x,y) dgamma(x,y).
Intuition
A coupling chooses how mass from the first law is paired with mass from the second; the infimum selects the cheapest such joint law.
Conditions
- two measurable state spaces and measures
- an ENNReal-valued cost
- the feasible set consists of measures with the prescribed marginals
Why these conditions cannot be dropped
- ENNReal preserves the possibility of infinite cost
- lower semicontinuity is not needed for the value definition but is needed to prove a minimizer exists
Proof route
- define the coupling set through first and second marginals
- take sInf of all coupling lintegral values
- use the product measure to verify nonemptiness for probability marginals
Lean interface notes
- lintegral is used because the cost is ENNReal-valued
- sInf is noncomputable and represents the extended-real infimum
- no optimal transport plan is constructed here
Read the mathematics first, then descend into Lean
You do not need to know Lean before opening this panel. The page keeps the paper-level theorem, rigorous proof obligations, exact Lean declaration, and proof dependencies as separate layers so a first-time reader can move down one layer at a time.
Proof architecture
Start with the tree when learning: prerequisites sit below the theorem and downstream results sit above it. Switch to the network when you want to understand where this declaration lives in the local formal library. Every mapped node is clickable.
Graph rule: only dependencies found by the ASTIS source scan are drawn. Missing tactic indirection is treated as an under-approximation; the site never invents an edge just to make a prettier graph.
How to read the exact Lean declaration
Read a Lean theorem left-to-right exactly as you would unpack a mathematical sentence: name → ambient types → automatically inferred structures → explicit hypotheses → conclusion → proof. Then read the proof top-to-bottom as transformations of the current goal.
- NameWhat reusable mathematical fact is being created?
- ParametersWhich symbols are arbitrary, and which structures are inferred by typeclass search?
- PropositionAfter the colon, translate the Lean expression back into a paper statement.
- Proof actionsAfter
by, ask what each tactic does to the mathematical goal—not only what syntax it uses.
Syntax used on this page
This glossary is filtered to syntax that actually occurs in the declaration above. Open a symbol only when you meet it, rather than memorizing Lean grammar in advance.
Source voice and ASTIS voice stay separate
When Samplinglib shows a short quotation from Chewi, it is labeled as a source excerpt and linked to the canonical book page. Intuition, expanded proof steps, hidden regularity assumptions, and Lean explanations are ASTIS-authored commentary. A quotation never substitutes for a formal proof, and an ASTIS explanation is never attributed to the textbook author.
Lean statement
noncomputable def transportCost {α β : Type*} [MeasurableSpace α] [MeasurableSpace β]
(c : α × β → ℝ≥0∞) (μ : Measure α) (ν : Measure β) : ℝ≥0∞ :=
sInf {r : ℝ≥0∞ | ∃ γ ∈ couplingSet μ ν, r = ∫⁻ z, c z ∂γ}
/-- Source-facing expansion of the Kantorovich value in display (1.3.2). -/
Open AutoSamplingTheory/TechnicalLemmas/Measure/Transport.lean:36published source at 7bcd37294df1