A meta-theorem template (the "master minimax") for optimality claims in the induced-metric optimizer family, paired with a "tautology test" that flags when such a claim is merely an algorithmic re-derivation of a known optimizer rather than a genuine optimality result. The project's diagonal minimax (derived optimizer) and Kronecker minimax (pullback unification → KFAC) are both run through the test and shown to be tautological — which reframes them as algorithmic derivations from embedding geometry, not novel optimality theorems.
The induced-metric framework gives a clean family of optimizers, parameterised by the choice of embedding. Each choice produces a preconditioner; each preconditioner has a worst-case convergence rate on some class of loss landscapes. A natural reframing of the optimisation question is to fix a class of landscapes and ask which preconditioner is provably best, in a precise minimax sense, on that class.
This entry sets up that reframing as a meta-theorem template (the master minimax) and identifies a structural pitfall that nearly any "optimality" theorem in this style falls into (the tautology test). Two existing optimality results from the project (the diagonal minimax in the derived optimizer and the Kronecker minimax in the pullback unification entry) are run through the test as worked examples, and both turn out to be tautological. This does not invalidate them, but it does change what they should be advertised as: they are algorithmic derivations of known optimizers from the embedding geometry, not novel optimality claims.
After running a year of experiments, the project's empirical evidence does not support a clean "this is a better optimizer than Adam" claim (see the empirical sections of the individual method entries, e.g. the learnable diagonal §9 and the base induced metric §9-11). But the embedding framework still has structural content that does not depend on whether a particular hyperparameter sweep wins. The right question to ask of a theoretical framework is not
Can we find a better optimizer?
but rather
Given a problem class , a preconditioner class , and a rate functional , what is the optimizer that is provably optimal under those assumptions?
This is a meta-question about the framework, not a benchmark question. Every concrete optimality theorem in the program is an instance of it. The point of writing down the template is to make the assumptions explicit, so that the reader can immediately see what an "optimality" claim is and is not asserting.
Fix three objects.
Preconditioner class . A set of embeddings (or, equivalently, base metrics , ambient metrics , and embedding maps ) that the optimizer is permitted to use. Each determines a pullback metric and an update rule
Problem class . A family of loss landscapes, or, for quadratic local analysis, a family of symmetric positive definite Hessians.
Rate functional . A scalar measure of optimizer performance on a specific loss. Typical choices are the worst-case condition number , the asymptotic contraction rate, the iteration complexity to reach -accuracy, or a generalisation gap.
The optimal pullback embedding for the triple is
This is the single equation that the framework revolves around. Every optimality theorem in the program is an instance: pin down , solve for , and compare the resulting optimizer to known ones.
The trap is the following. If the preconditioner class is rich enough to invert every element of the problem class, then the minimax trivially returns the per-instance inverse and there is no real optimisation happening. We have asked a class that contains every answer to produce the answer, and unsurprisingly it does.
Definition. An instance is tautological if for every there is a with (equivalently, ), where the proportionality absorbs the learning-rate gauge, and is monotone in .
When the test flags tautology (the condition above holds), the minimax-optimal is by construction the unique element (up to gauge) that satisfies on each , giving preconditioner . The theorem then states "the optimal preconditioner is the exact inverse of the Hessian," which is true but uninformative.
The project's two existing optimality theorems both fail the tautology check. They are still useful as algorithmic derivations, but the framing needs to be honest.
The tautology check flags this instance: for any diagonal , the choice (the mean-centered form required by the gauge constraint, with the residual scalar absorbed into the learning rate) makes and the preconditioner , exactly the Newton step. The minimax reduces to "equalise across ," giving
Sign convention note. The derived optimizer uses the opposite convention: it parameterises the preconditioner directly as (no inverse), so its Newton formula reads . The two formulas describe the same theorem; they only differ by which object parameterises (metric versus preconditioner). When cross-referencing, flip the sign of .
This is the result that drives the derived optimizer. It is genuinely useful: it identifies the algorithmic form of the Newton diagonal as the unique minimax-optimal log-diagonal scaling, and forces the mean-centering convention. But as a minimax theorem it says "if the preconditioner class can invert the Hessian, the optimal thing to do is invert it." That is the definition of the class.
The tautology check returns : for any Kronecker , the choice and gives , hence preconditioner ; exactly the Newton step on the Kronecker block. The minimax reduces to "equalise the pairwise products ," and the rank-one factorisation argument (Section 7 of the pullback unification entry) forces and .
Again the theorem is useful: it gives an algorithmic derivation of KFAC from minimax over the Kronecker class, independent of the Fisher-approximation derivation in Martens and Grosse. But it is also tautological: the Kronecker class can invert any Kronecker Hessian, and minimax forces it to do so.
Tautology is a property of the class choice, not of the theorem's value. Both worked examples are real contributions in the following sense: they identify the unique algorithmic form that satisfies a clean optimality criterion on a clean problem class. Without the theorems we would not know that the natural form of the Newton diagonal is
(the mean-centering term is not arbitrary; it is forced by the gauge constraint), or that the natural form of the Kronecker-factored metric approximation (whose inverse is the applied preconditioner) is
(the normalising constants are forced by the volume constraint, which is itself just a gauge fix; the individual factors are not separately determined since leaves invariant).
A tautological theorem can still surprise. What it cannot do is demonstrate that the framework produces optimizers that beat known methods on the chosen problem class, because by construction the framework's optimum is the per-instance inverse, which is also the per-instance optimum of any reasonable rate functional. To demonstrate novelty in that sense, the problem class needs to be richer than the preconditioner class.
There are four structural ways to make .
Rank restriction. has lower expressive rank than . The cleanest example is the spike-bulk minimax of Section 8: diagonal preconditioner () on a Hessian with a single rank-one off-diagonal spike ().
Structural restriction. is constrained to a specific symmetry or sparsity pattern that does not share. For example, restrict to block-diagonal but let contain dense Hessians.
Information restriction. is chosen using only observables of (gradients, Hutchinson Hessian-vector-product samples), not itself. This is the usual setting for an online optimizer, and is what makes a stochastic version of even a tautological class non-tautological in practice.
Cost restriction. is parameterised with bounded compute or memory: representing exactly exceeds the budget. This is the situation for any finite-time optimizer that maintains less state than a full Hessian.
The common theme: the adversary (the worst-case ) can produce curvature structure that the preconditioner cannot match, so the optimizer must approximate rather than invert. The interesting theorems are about the structure of that approximation.
The framework covers update rules of the form
where is determined by the embedding and depends only on the current (plus possibly auxiliary metric-learning state that evolves deterministically from the history of ). The update at step is memoryless given . No look-ahead, no velocity state, no first-moment accumulator.
Under the convention of Section 2, with the metric and the applied preconditioner:
These optimizers are excluded by construction, not by accident: they are not pullback metrics on alone, regardless of which embedding is chosen.
This is an honest restriction. The framework is set up to describe one family of optimizers and does not claim to subsume momentum-style methods. The method entries' empirical sections compare against Adam, SGD, Muon, AdamW, and several momentum baselines for context, but no optimality theorem in this program claims to dominate them.
The framework allows the metric itself to carry slow-timescale state, such as a learnable diagonal evolving via an EMA of curvature estimates. What is excluded is fast-timescale state on 's trajectory: velocity, momentum, look-ahead. The restriction is honest and carves out the subset of optimizers the framework is actually equipped to describe.
The first interesting application of the master template is a minimax problem whose tautology check fails. The setup.
The tautology check now fails. By Sherman-Morrison,
The second term has at least one nonzero off-diagonal entry (whichever has ). No has off-diagonal entries, so . The instance is non-tautological.
The next theorem in the program (in progress) is to solve this minimax explicitly: what is the optimal diagonal scaling given a rank-one off-diagonal spike, and how badly does it underperform the (unavailable) exact inverse? The answer should quantify how much off-diagonal structure the diagonal class can absorb, and where it cannot.

For the first non-tautological instance, the rate functional is
This functional has four useful properties. It is scale-invariant ( is invariant under ). It is monotone in the standard contraction-rate functional for gradient descent on a quadratic (so a smaller is a tighter convergence-rate bound). It is tractable symbolically for rank-one and small-rank perturbations via the secular equation. And it is the functional used in both worked examples in Section 4, so the master notebook can reproduce those as sanity checks under the same .
Later instances may use different functionals: iteration complexity, stochastic-convergence rate, generalisation-gap upper bound, or a hybrid. The Phase 1 instance uses to minimise the conceptual distance from known results.
Every theorem in the program follows the same recipe.
Step 1. State precisely. must be a family of Hessians or losses with a structural parameter (dimension, rank, condition-number bound). must be a subset of embeddings described by a parameter vector. must be a scalar function of .
Step 2. Run the tautology check. Verify whether . If yes, the theorem is a re-derivation of a known optimizer, not a new one. Still publishable as a unification, but the framing must say so.
Step 3. Compute the rate symbolically. For quadratic this reduces to a spectral calculation on . Sherman-Morrison and Woodbury make low-rank cases tractable.
Step 4. Solve the minimax. For tractable instances this yields a closed-form as a function of the problem-class parameters. Otherwise characterise via KKT conditions.
Step 5. Verify numerically. Plug specific rational parameter values into a small numerical script and confirm that the symbolic is the true minimum over a large random sample of competitors.
Step 6. Scenic-route writeup. Narrative explanation in the project's house style, with derivations shown rather than asserted.
What the framework does claim, after this entry.
What the framework does not claim.
The framework is the bridge between two halves of the project. On the theory side, it organises every optimality theorem (diagonal, Kronecker, spike-bulk, and future extensions) under one template, with a built-in honesty check. On the empirics side, it makes the structural assumptions explicit so the reader can see exactly what assumption fails when a derived optimizer underperforms in practice (typically the structural assumption on , as in the derived optimizer's failure analysis).
The next theorem in the program is the spike-bulk minimax of Section 8, whose tautology check fails. After that, the natural extensions are to information-restricted classes (preconditioner uses only HVP samples, not ) and to cost-restricted classes (preconditioner has a fixed memory budget).
A subtler version of the tautology question arises when the preconditioner is chosen using observables rather than itself. Even if the deterministic version of the class can invert every , the stochastic version (where is estimated from Hutchinson HVP samples) is non-tautological: the estimator has finite variance, so the achieved preconditioner is a random approximation of the deterministic minimax-optimal one, and the rate functional must account for the variance.
The robustness theorem in the derived optimizer (Appendix B) addresses exactly this question for the diagonal case. The version for the Kronecker case (relative error on each factor) is straightforward but has not been written up.
In both the diagonal and Kronecker minimax theorems, the preconditioner class is restricted by a determinant constraint ( in the diagonal case, in the Kronecker case). These are not substantive assumptions; they fix the gauge degeneracy that comes from the symmetry
which leaves the update invariant. Without a gauge fix, the minimax problem has a one-parameter family of equivalent solutions, and the theorem statement would have to quotient by this. The constraint just picks a canonical representative.
The companion materials.
repo/notebooks/hp-minimax-master.nb: Mathematica module implementing Embedding[], Pullback[], Rate[], and Minimax[]. Reproduces the diagonal and Kronecker theorems as worked examples and computes the spike-bulk minimax symbolically for small .
scripts/hp_tautology_check.py: Numerical utility that takes samplers for and , computes the Frobenius distance from each to its projection onto , and reports the empirical tautology check (the test fails when this distance is consistently positive).
Scripts (scripts/):
scripts/hp_tautology_check.py: numerical verification of tautology checks for arbitrary pairs.scripts/make_figures.py: reproduces every figure shown in this entry (PDF and PNG written to figures/).Notebooks (notebooks/):
notebooks/hp-minimax-master.nb: symbolic implementation of the master template (Frobenius projection, tautology check, gauge-fixed Newton-target solver).notebooks/worked-examples.nb: the diagonal, Kronecker, and spike-plus-bulk minimax instances run through the master template.