A configuration holding the request's antipode resolves through an original server
ProvedKServer.antipode_config_resolves_originalLet be the work function of a -server instance ending with the request , in the antipodal extension of a bounded space, and consider a configuration holding the request's antipode together with two original points. Every configuration resolves --- some server moves to at exactly the cost of the move --- but a priori the resolving server could be the one at , whose move costs the full . The theorem rules that out as the only option:
the configuration always resolves through one of its original servers, never only through the antipode.
Why
The one-sided bounds (and with ) are -Lipschitzness; the content is that one of them is tight. By the envelope theorem the value is attained through an original configuration , matched coordinatewise: the -slot contributes and the - and -slots contribute plainly. If sits in facing the -slot, replacing by in the target removes exactly from the matching, so the -resolution is tight; likewise for . The interesting case is facing the -slot: then one permutes --- the work function is blind to the relabelling, the matching is not --- so that faces 's neighbour instead, and the triangle inequality shows the permuted matching still pays for the -resolution. So an original-server resolution is always available.
Role
This is the missing case in the proof of Lemma 21 of Coester and Koutsoupias (the lemma that pushes the request to the last anchor slot, valid for and false for ). Their argument resolves the configuration and treats the resolutions from and from , tacitly discarding resolution from ; this theorem is the justification: a - or -resolution always exists, whatever the resolution oracle returns. It feeds directly into the first-slot pushing lemma and thence into the case analysis of their Theorem 23 on trees.
Formalization note
Stated in the antipodal extension on with originals embedded by Sum.inl and ; is workFnU. The proof uses only the envelope theorems and permutation invariance --- no tree structure, no finiteness of .
import Mathlib import Definitions.Def_KServer_workfunctionU import Definitions.Def_KServer_antipodal_extension
namespace KServer
theorem antipode_config_resolves_original (M : Type) [MetricSpace M] (Δ : ℝ) (hΔ0 : 0 < Δ)
(hΔ : ∀ u v : M, dist u v ≤ Δ) (C₀ : Config 3 M) (σ : List M) (r y z : M) :
@workFnU 3 (M ⊕ M) (antipodalExtension M Δ hΔ0 hΔ)
(fun i => Sum.inl (C₀ i)) ((σ ++ [r]).map Sum.inl) ![Sum.inr r, Sum.inl y, Sum.inl z]
= @workFnU 3 (M ⊕ M) (antipodalExtension M Δ hΔ0 hΔ)
(fun i => Sum.inl (C₀ i)) ((σ ++ [r]).map Sum.inl) ![Sum.inr r, Sum.inl r, Sum.inl z]
+ dist y r
∨ @workFnU 3 (M ⊕ M) (antipodalExtension M Δ hΔ0 hΔ)
(fun i => Sum.inl (C₀ i)) ((σ ++ [r]).map Sum.inl) ![Sum.inr r, Sum.inl y, Sum.inl z]
= @workFnU 3 (M ⊕ M) (antipodalExtension M Δ hΔ0 hΔ)
(fun i => Sum.inl (C₀ i)) ((σ ++ [r]).map Sum.inl) ![Sum.inr r, Sum.inl y, Sum.inl r]
+ dist z r := by sorry
end KServer