2026/07/15 36.6k words

Transformer System #numinens#transformer#lora#low-rank#intrinsic-dimension#subspace#ntk#fine-tuning#optimization#linear-algebra

M6.7 - Low-Rank Theory: Intrinsic Dimension, Subspaces, and Dynamics

M6.7 - Low-Rank Theory: Intrinsic Dimension, Subspaces, and Dynamics

0x00 Overview: Four Different Claims Hide Behind “Fine-Tuning Is Low Rank”

M6.3 derived the LoRA operator, tensor shapes, gradients, initialization, memory ledger, and merge path. M6.4 compared methods that change rank allocation, scaling, initialization, precision, optimizer dynamics, or weight parameterization. This article steps back from method selection and asks the harder question:

Under what assumptions can a low-rank parameterization recover useful fine-tuning behavior, and where do those assumptions fail?

The popular answer is often one sentence:

Fine-tuning has a low intrinsic dimension, therefore a low-rank adapter is enough.

That sentence compresses several different mathematical objects:

  1. the dimension of a subspace in the entire model parameter vector within which an objective can be optimized;
  2. the matrix rank of one layer’s dense full-fine-tuning update;
  3. the rank bound imposed by one LoRA factorization;
  4. the dimension of the function changes or gradient features observed on a finite dataset.

None of these is automatically equal to the others.

The difference is not philosophical. It changes what an experiment proves. A rank-8 adapter working on one benchmark does not establish that the objective intrinsic dimension is eight. A random 200-dimensional full-model subspace succeeding does not establish that every adapted matrix has rank 200. A theorem in a fixed neural-tangent-kernel regime does not establish that a long, high-learning-rate continued-pretraining run stays in that regime.

This article keeps the claims separate and connects them only when the assumptions are visible.

0x00A The Question Predates LoRA

Large pretrained models contain far more scalar parameters than many downstream datasets contain examples. A raw parameter count therefore creates a puzzle: why can an optimizer expose hundreds of millions of coordinates to a small supervised dataset and still find a useful solution?

The first line of evidence used here did not begin with a low-rank matrix factorization. Li et al. measured objective-landscape intrinsic dimension by replacing native optimization with training in a fixed, randomly oriented global subspace. Aghajanyan et al. carried that protocol into pretrained language-model fine-tuning, introduced direct and structure-aware variants, and measured the smallest tested coordinate dimension that recovered a chosen fraction of full-fine-tuning performance. These are experimental protocols over the full parameter vector. They establish that a successful low-dimensional optimization path can exist under the tested projection, task, model, seed, optimizer, and performance threshold. They do not identify the rank of each layer update.

LoRA made a different move. It froze a selected dense matrix and constrained its update to a trainable product:

This is a structured, layer-local parameterization. It gives a mergeable operator and a hard rank upper bound, but it is not the random global coordinate system used by an intrinsic-dimension experiment. The original LoRA paper connected the two through a hypothesis: successful adaptation may have a low-dimensional structure, and weight changes may exhibit low intrinsic rank. The hypothesis motivated an operator; it did not make the two measurements identical.

Later work split the original question into several research programs:

  1. measurement: how many trainable coordinates recover a performance threshold under a fixed subspace protocol;
  2. geometry and approximation: how well a dense update can be reconstructed at rank , and which row/column spaces are retained;
  3. optimization dynamics: how factor initialization, scaling, gauge freedom, and optimizer choice alter the path even when the product begins at the same matrix;
  4. function-space dynamics: when a linearized or neural-tangent-kernel description predicts fine-tuning behavior;
  5. expressivity and generalization: which targets a rank-constrained network can represent under theorem-specific assumptions, and what finite-data bounds follow;
  6. retention: how the restricted update changes target-domain learning and out-of-domain forgetting.

Those programs overlap, but none subsumes the others.

0x00B One Slogan, Six Evidence Contracts

The phrase “fine-tuning is low rank” is only meaningful after naming the object, protocol, and success criterion.

ContractObject being restricted or measuredEvidence operationA valid conclusionAn invalid shortcut
optimization-subspace existenceflattened model parameter vectortrain in fixed random/structured coordinates and sweep dimensiona tested subspace can reach a stated score thresholdevery layer update has that matrix rank
matrix approximationone measured dense update SVD and rank- reconstructionrank captures a stated norm-weighted fraction of this updatethe low residual guarantees task quality
factorized optimizationtrainable factors inspect gradients, singular spectra, conditioning, and trajectoriesinitialization and gauge affect the optimization pathall zero-product initializations are dynamically equivalent
kernel approximationJacobian features or empirical kernel on a datasetcompare linearized/full trajectories or kernelsa tested regime is compatible with a kernel descriptionlong nonlinear training remains in that regime
expressivity theoremmodel class under explicit width, depth, rank, and target assumptionstheorem/proofthe parameterized class can represent or approximate the stated targetthe theorem supplies a universal practical rank
retention experimenttarget and non-target evaluations over a training protocolcompare LoRA/full fine-tuning with controlled budgetsthe tested restriction changes learning/forgetting tradeoffsLoRA always preserves knowledge or always matches full fine-tuning

This table is the article’s epistemic firewall. A later section may connect two contracts only by stating the additional assumptions or by running an experiment that measures both.

0x00C Historical Evidence Map

The sequence below explains why the article moves from protocols to matrix geometry, then to dynamics and function-space claims.

Source lineageQuestion askedEvidence class used hereWhat enters this articleWhat remains outside the claim
Li et al. (ICLR 2018)how many coordinates are needed to find a solution in an objective landscape?externally verified protocol and source-reported resultsrandom-subspace measurement ancestrylanguage-model-specific or LoRA-specific conclusions
Aghajanyan et al. (2020)can pretrained language models be fine-tuned in low-dimensional global/structured coordinates?externally verified protocol and source-reported resultsDID, SAID, and thresholded measurementequality between and per-layer matrix rank
Hu et al. (LoRA, v2)can selected dense updates be parameterized as low-rank products?externally verified operator plus source-reported experimentslow-rank operator and subspace-similarity diagnosticuniversal adequacy of one rank across tasks and layers
Vandereycken; Billaud-Friess et al.what is the local geometry of exact fixed-rank matrices?externally verified geometrymanifold dimension, tangent/normal spaces, orthogonal projector, and fibreequivalence between quotient-manifold optimization and ordinary LoRA training
Eckart and Young (1936)which rank-constrained matrix minimizes least-squares reconstruction error?peer-reviewed theoremtruncated-SVD optimum and gap-dependent uniquenessLoRA optimization or task-quality preservation
Roy and Vetterli (EUSIPCO 2007)how can effective dimensionality vary continuously with a singular spectrum?peer-reviewed definitionsingular-value entropy conventionequality with squared-energy entropy, configured rank, or task-sufficient rank
Yang et al. (CorDA v3)how can activation context orient a PEFT decomposition?primary method contractcontext-oriented decomposition as an alternativeequality between CorDA’s construction and output-weighted dense-update reconstruction
Malladi et al. (ICML 2023)when can kernel dynamics describe language-model fine-tuning?peer-reviewed theorem/experiment contractlinearization and subspace-kernel lensunrestricted nonlinear-training behavior
Zeng and Lee; Jang et al.what can LoRA express or optimize under theorem assumptions?theorem contractsrank thresholds and assumptions, kept theorem-localbenchmark-optimal rank or universal task quality
Zhu et al.; Hayou et al.do the two factors play symmetric optimization roles?theorem and source-reported experimentsfactor roles and initialization-dependent dynamicsletter-name conventions or universal optimizer behavior
Biderman et al.what changes when LoRA is compared with full fine-tuning at larger adaptation budgets?source-reported controlled experimentstarget-learning versus retention tradeoff“LoRA always matches full fine-tuning”

The 2018 and 2020 papers establish existence under a measurement protocol. LoRA establishes a particular structured parameterization. Kernel and expressivity papers add conditional explanations. Initialization and retention papers expose cases where the simple slogan is insufficient.

The handwritten A22 source also introduces a decomposition taxonomy: adaptation can reconstruct an existing subspace, extend it with new directions, or combine both operations. The figure is useful as a historical taxonomy, not as proof that every PEFT method shares one optimization geometry.

A22 source taxonomy of reconstruction, extension, and combination views

Source-local figure from A22, derived there from Si, Yang, and Shen’s decomposition framework. Retained for historical orientation. M6.7 later defines reconstruction, expansion, and composition operationally; it does not adopt the figure’s categories as a theorem.

0x00D Evidence Classes And Claim Status

This article uses five evidence classes and never treats them as interchangeable:

source-local
    what handwritten A22 says, including its organization and figure lineage

externally verified protocol or theorem
    what a pinned primary paper states under its assumptions

source-reported empirical result
    a result reported by a paper, not reproduced in this repository

executable local derivation
    algebra, finite-dimensional examples, or test oracles implemented here

rewrite interpretation
    synthesis that connects sources while preserving their scope

The source manifest pins paper revisions because theorem statements, experimental details, and even figure numbering can change between arXiv versions. A citation proves provenance; it does not by itself reproduce a training run.

0x00E Owner, Boundary, And Loop Contract

M6.7 consumes the LoRA operator, tensor shapes, first-order gradients, and checkpoint semantics from M6.3. It consumes variant axes and method-selection language from M6.4. It owns:

dimension taxonomy and intrinsic-dimension protocols
rank-manifold geometry and factor gauge
SVD reconstruction and output-weighted diagnostics
initialization asymmetry and factor dynamics
kernel-regime arguments and their failure boundary
expressive-power theorem scope
learning-versus-forgetting experimental contracts
rank-adequacy diagnostics

It explicitly defers:

variant catalog and deployment selection                 -> M6.4
adapter paging, batching, and runtime lifecycle           -> M6.5
routed, shared, and continual adapter composition         -> M6.9
general empirical scaling-law fitting and extrapolation   -> M4.7-M4.9

The article is therefore not a survey of every LoRA variant and not a claim that one theorem settles practical rank selection. Its twelve-loop reconstruction proceeds from immutable objects and protocols, through derivations and executable oracles, to paper-by-contract comparison and publication closure. Loops 1—11 now freeze the historical evidence surface, immutable study objects, intrinsic-dimension protocol, fixed-rank geometry, reconstruction and subspace diagnostics, factor dynamics, kernel and expressivity boundaries, retention decision policy, typed failures, experimental design, sources, and responsive visual provenance. Loop 12 closes formulas, browser rendering, accessibility, and cross-article ownership without changing those scientific contracts.

For provenance, the original Loop 1 entry gate is retained verbatim: “Loop 2 next freezes the parameter, matrix, function, dataset, rank, and protocol manifest.” That historical sentence records sequencing; the current handoff is Loop 12 publication closure.

0x00F Immutable Study Manifest: Objects Before Results

A low-rank result is not reproducible if its nouns can change underneath it. “The update,” “the rank,” “the dataset,” and “the baseline” are not identifiers. Two runs can use the same configured LoRA rank while adapting different tensors, starting from different base revisions, selecting checkpoints by different metrics, or measuring rank with different tolerances. They are then different experiments.

M6.7 uses one immutable study manifest with six linked namespaces:

LowRankStudyManifest(
    manifest_id       = "m6-7-linear-study-v1",

    parameter_schema  = "row-major W[4,6] -> theta[24]",
    parameter_objects = {theta_0, theta_full, delta_theta_full, u},
    matrix_objects    = {W_0, W_full, delta_W_full, A, B, delta_W_lora},
    function_objects  = {f_theta, F_train, J_train, K_train},
    dataset_objects   = {train_v1, eval_v1, retention_v1},
    rank_policies     = {configured, algebraic, numerical, stable, energy, entropy},
    protocols         = {DID, SAID, full_update, LoRA, SVD,
                         output_weighted, overlap, kernel, retention},
)

The manifest is a deliberately small linear teaching fixture. It exists so later loops can execute exact algebra and reject identity drift. It is not a miniature language model and its derived numbers are not paper results.

Immutable object and protocol graph for the M6.7 low-rank study

Every arrow in the figure is directional. A dataset and a parameter object determine a function trace; a measured dense update and a rank policy determine a reconstruction diagnostic; a protocol consumes those objects and emits a result record. A result record never retroactively changes the object that produced it.

0x00G Parameter Coordinates, Matrices, And Factors Have Different Identity

The teaching parameter vector has ambient dimension and is the row-major flattening of one matrix . The coordinate schema is part of the identity:

A dense fine-tuning delta is defined only when the base and trained objects have the same tensor schema and coordinate order:

Changing a tensor name, transpose convention, vocabulary row order, shard layout without reconstruction, or base revision invalidates this subtraction. Shape equality alone is insufficient.

The global intrinsic-dimension fixture introduces a separate coordinate vector and a fixed projection:

The baseline manifest uses , but this is a teaching configuration, not a measured intrinsic dimension. The protocol later sweeps candidate values of and creates a distinct projection identity for every projection family, dimension, and seed.

The LoRA fixture acts on the matrix object instead:

Its configured rank is , scale is , and factor count is . The factors, their product, and the dense reference update have distinct IDs. A gauge transformation can change and without changing , so a factor checkpoint cannot be compared coordinate by coordinate with another checkpoint until its gauge convention or alignment operation is declared.

IdentityFrozen fieldsLegal derived objectIllegal collapse
theta_0base revision, tensor schema, coordinate order, dtype rolefunction at the base point”same shape” means same base
delta_theta_fullbase ID, trained ID, subtraction schemaper-layer reshapesa LoRA factor vector
delta_W_fulllayer ID, input/output axes, base/trained IDsSVD diagnosticsglobal intrinsic dimension
A, Bfactor IDs, orientation, rank, scale, initializationsBAuniquely identifiable coordinates
delta_W_lorafactor artifact IDs and multiplication orderrank-bounded operator deltaproof that configured rank is realized
M, uprojection family, dimension, seed, ambient schemaglobal subspace update Mua layer-local low-rank factorization

0x00H Functions, Jacobians, And Datasets Are First-Class Objects

Parameter-space statements become function-space statements only after fixing inputs. For a dataset matrix , define the stacked output trace:

If each example produces measured outputs, the dataset Jacobian at the declared base point is:

The corresponding empirical output-space kernel is:

is a different parameter-space Gram matrix. Calling both objects “the NTK” without axes would make later kernel comparisons ambiguous.

The teaching fixture freezes three disjoint synthetic splits:

SplitRowsPurposeFrozen identity fields
train_v16optimizer updates and train lossordered sample IDs, numeric payload, labels, transform revision
eval_v14checkpoint selection and target scoreordered sample IDs, payload, labels, metric revision
retention_v14non-target behaviorseparate dataset ID, payload, labels, metric revision

Real experiments must additionally freeze model/tokenizer revision, prompt or sequence construction, truncation, label mapping, deduplication, data order, batch construction, and all random seeds. A dataset name is not a split manifest. A benchmark score without a checkpoint-selection rule is not a protocol result.

For output-weighted reconstruction, the sampled input matrix is also part of the metric:

Changing changes the weighting of right-singular directions even when and are unchanged.

0x00I “Rank” Is A Policy Family, Not One Stored Integer

The manifest records the configured bottleneck and every measured-rank policy separately.

Rank recordDefinitionRequired policy fieldsMain limitation
configured rank factor bottleneck chosen before trainingtarget matrix, factor orientation, rankonly an upper bound on rank(BA)
algebraic rank number of nonzero singular values in exact arithmeticexact matrix objectunstable as a floating-point diagnostic
numerical rank singular values above a declared thresholdmatrix, dtype, SVD backend, tolerance rulechanges with scale and tolerance
stable rank norm-ratio proxymatrix and norm conventionnon-integer and not a factor bottleneck
energy rank smallest prefix capturing fraction of squared singular massmatrix, sort order, energy thresholdignores task/output weighting
entropy effective rank exponential entropy of normalized spectral energymatrix, zero-spectrum policy, logarithm baseanother smooth summary, not algebraic rank

For the numerical-rank policy used by later teaching oracles:

The stable-rank policy is:

The energy-rank policy is:

For entropy effective rank, let over nonzero spectral mass:

These estimators can disagree without any implementation bug because they answer different questions. Every reported rank must carry the matrix ID and policy ID that produced it.

0x00J Protocol Identity: One Result, One Envelope

The manifest gives each later experiment its own immutable envelope.

Protocol IDTrainable objectFixed objectsRequired sweep or comparisonResult contract
did_v1global coordinates base, projection family/seed, train/eval splitscandidate and projection seedsscore distribution and threshold-qualified
said_v1 plus declared layer scalesbase, structured projection, budget conventioncandidate total coordinate budgetscore plus explicit scale-coordinate accounting
full_update_v1full parameter objectbase and data protocoloptimizer/seed replicationcheckpoint ID, score, and aligned dense delta
lora_v1declared factors onlybase, target matrix, scale/initrank and seed sweepcheckpoint ID, score, and product delta
svd_reconstruction_v1nonealigned dense deltarank and tolerance policiesnorm residuals, never task quality by itself
output_weighted_v1nonedense delta and named input splitrank sweepsampled output residual
subspace_overlap_v1nonetwo named matrix/subspace objectsretained dimensions and normalizationprincipal angles or overlap statistic
kernel_v1protocol-dependentbase point, named dataset, Jacobian conventionfull versus restricted featureskernel discrepancy under declared axes
retention_v1full or adapter parametersmatched budgets and checkpoint rulemethod/rank/seed sweeptarget and retention metrics together

Every training protocol records optimizer name and revision, hyperparameters, schedule, steps or tokens, batching, precision, clipping, regularization, seed roles, evaluation cadence, and checkpoint-selection rule. Every analysis protocol records the exact checkpoint IDs, matrix extraction rule, SVD/rank policy, and numerical backend. Reusing a result under a changed envelope creates a new result ID; it does not silently mutate the old one.

0x00K The Teaching Ledger And Its Evidence Boundary

The checked Loop 2 fixture derives only structural facts:

ambient parameter coordinates D                 = 24
global teaching subspace coordinates d          = 3
dense matrix coordinates 4 * 6                  = 24
configured LoRA factor coordinates 2*(6+4)      = 20
generic rank-2 matrix-manifold dimension         = 2*(6+4-2) = 16
factor gauge redundancy                         = 2^2 = 4
train / eval / retention rows                    = 6 / 4 / 4
stacked train outputs N*C                        = 6*4 = 24
train Jacobian shape                             = [24,24]
output-space empirical-kernel shape              = [24,24]

The manifest validator checks shapes, identities, split separation, rank-policy fields, protocol envelopes, and these cross-object ledgers. It does not optimize , train LoRA, compute an SVD, evaluate a kernel approximation, establish an expressivity theorem, or reproduce a paper score. Those operations belong to later loops and must consume this exact manifest rather than inventing new objects mid-derivation.

0x01 A Vocabulary Of Dimensions

0x01A Ambient Parameter Dimension

Flatten every trainable model tensor into:

Full fine-tuning exposes up to scalar coordinates to the optimizer. is an ambient count, not proof that every coordinate is needed or independently identifiable on the downstream data.

0x01B Optimization Subspace Dimension

Choose a map and optimize:

When for a fixed matrix , training is restricted to one -dimensional linear subspace of the full parameter space.

This is a global optimization coordinate count. It does not describe the rank of any one reshaped parameter update.

0x01C Matrix Update Rank

For one layer:

the matrix rank is the number of nonzero singular values:

This rank says how many independent input-to-output directions the update uses at that layer. It says nothing directly about the rest of the model.

0x01D LoRA Rank

LoRA imposes:

and therefore:

The configured is an upper bound. Training may produce an effective update rank below because factors become dependent, singular values collapse, or regularization suppresses directions.

0x01E Representation Or Feature Dimension

Hidden states can also occupy a low-dimensional subspace on a dataset. That is an activation-space claim. A model can have low-dimensional observed features while requiring a high-rank weight update outside that sample, or a low-rank update can alter high-dimensional activations through nonlinear network composition.

0x01F Do Not Conflate The Objects

QuantityObjectTypical measurementWhat it does not prove
full parameter vectorcount tensor elementsall coordinates are needed
optimization objective under a subspace protocolrepeated subspace trainingone layer update has rank
one layer updateSVD with a toleranceobjective intrinsic dimension equals this rank
LoRA factor bottleneckconfigurationall directions are used
stable/effective ranksingular spectrumthreshold, entropy, or norm ratioexact algebraic rank
feature dimensionactivations/JacobianPCA, spectrum, kernelparameter update is low rank

0x02 Intrinsic Dimension Is A Protocol

The primary intrinsic-dimension study for language-model fine-tuning defines an objective’s intrinsic dimension as the minimum number of parameters needed to reach a satisfactory solution, then estimates it through low-dimensional subspace training. The first clause is an idealized property of an objective and success criterion. The second is a finite experiment with a projection family, sampled subspaces, optimizer, budget, metric, threshold, and search grid.

The experiment can therefore return a reproducible protocol estimate. It does not reveal a unique architecture constant.

Intrinsic dimension measurement protocol

0x02A Direct Reparameterization And Gradient Pullback

Let be a fixed random projection and be trainable:

Initialize , so the run begins at the pretrained parameters . During training:

The optimizer sees the full-model gradient only after it has been projected into coordinates. The effective full-space update is:

for one plain gradient-descent step. Thus the method is not selecting original parameters. It optimizes combinations of all parameters defined by .

The forward and reverse tensor trace is:

forward:
    u[d]
      -> M @ u
    delta_theta[D]
      -> theta_0 + delta_theta
    theta[D]
      -> model and loss
    L[]

reverse:
    g_theta[D]
      -> M^T @ g_theta
    g_u[d]

The adjoint identity is the implementation check:

It catches a wrong transpose, a changed flattening order, or a forward/adjoint projection generated from different seeds.

0x02B When Is And Is Not A Projector

If the columns of are orthonormal,

then:

is the orthogonal projector onto . It is symmetric and idempotent:

and the rejected gradient is orthogonal to the subspace:

If has full column rank but non-orthonormal columns, the orthogonal projector is instead:

Plain gradient descent in the coordinates still induces , not . The reachable subspace is the same, but its coordinate metric changes the optimization trajectory. Replacing by and by preserves represented points for invertible , yet generally does not preserve SGD or Adam steps. A subspace identity and an optimizer-coordinate identity are separate fields.

The original objective-landscape study normalized dense random columns and relied on high-dimensional approximate orthogonality unless an explicit orthogonalization was used. A Fastfood-style map should not be called an orthogonal projector merely because it is random.

0x02C Dense, Sparse, And Implicit Projection Choices

Li et al. compared three ways to realize the fixed map. They share the same reparameterization contract but have different state and arithmetic costs.

Projection familyStored representationLogical application costImportant qualification
dense Gaussian-style valuescolumns can be normalized or orthogonalized; state is prohibitive at large
very sparse randomnonzero values and indicessource-reported theoretical improvement over densesparse metadata and framework kernels determine realized cost
Fastfood-style implicitsigns, Gaussian diagonal, permutations, and block state time and state in the cited constructionpadding, stacking, normalization, trimming, and adjoint must be implementation-defined

Aghajanyan et al. give a concrete scale example: a dense map for RoBERTa-Large with would require roughly 1.42 TB for the projection alone under their accounting. That motivates an implicit map; it does not make every structured map numerically equivalent.

0x02D Fastfood Forward, Padding, Stacking, And Adjoint

Storing a dense matrix is infeasible for large language models. Aghajanyan et al. use a Fastfood-style structured random transform built from Hadamard transforms, random diagonal matrices, and a permutation so the projection can be applied without materializing a dense matrix.

The paper’s schematic form is:

where the factors are fixed and only is trainable. The exact normalization and dimensions belong to the implementation; the important distinction is that the measurement uses a fixed global random projection, not a learned low-rank factor at each layer.

For an executable implementation, let , pad to , and define one normalized block:

The factor represents two normalized Hadamard transforms. Other normalizations are legal only when recorded. Stack independently parameterized blocks and trim the last block:

The exact forward order is:

u[d]
  -> zero-pad to p
  -> B_b sign diagonal
  -> Hadamard
  -> Pi_b permutation
  -> G_b diagonal
  -> Hadamard
  -> divide by p
  -> stack blocks
  -> trim to D

Reverse mode must undo trimming, then apply every transpose in reverse order:

because and are diagonal and is symmetric. Contributions from all output blocks are summed before the padded coordinates are removed. Reusing the forward permutation instead of its inverse is a shape-correct adjoint bug.

Direct and structure-aware intrinsic-dimension projection traces

The Loop 3 exact fixture uses , a shared coordinate width of four, six Fastfood-style blocks of width four, two parameter groups, and rational diagonal values. Rational values make the local adjoint trace exact; they are not claimed to be samples from the paper’s Gaussian distribution.

0x02E Structure-Aware Intrinsic Dimension Is Bilinear

For declared parameter groups, SAID reserves coordinates for learned group scales and uses the remaining coordinates for one shared projected update. Let:

and let select the coordinates of group . The update is:

The total trainable-coordinate ledger is therefore:

not plus uncounted scale parameters. With ambient gradient , the exact gradients are:

and:

SAID is bilinear in . If but , scale gradients begin at zero while can receive a gradient. If both and every , both paths are blocked. Initialization is therefore part of the protocol, not harmless metadata.

The case has no shared projected coordinate. It is a legal coordinate count but a degenerate no-update fixture when is empty. A search implementation must report that outcome rather than silently reinterpret as the shared width.

SAID is still not LoRA. Its learned scales multiply groups of one global projected update; it does not constrain each reshaped matrix to a product of rank at most .

0x02F The Grid Estimate

The protocol first obtains a full-fine-tuning score , then searches for the smallest whose subspace-trained score reaches a specified fraction, historically 90%:

Here is the candidate-dimension grid, indexes projection/training seeds, indexes the declared hyperparameter search, and is a declared seed aggregator such as the median. The superscript matters: the result is the first passing tested value, not the exact minimum over all integers or all possible subspaces.

If accuracy is 85%, the historical threshold example is . This multiplication only makes sense for a score whose scale and direction support it. Loss, perplexity, signed correlation, or offset metrics need a quality transform and threshold defined in that metric’s own contract.

That threshold has a limitation: it ignores the pretrained baseline. If the base model already scores 75%, reaching 76.5% captures only a small fraction of the full fine-tuning gain. A deployment audit may instead use normalized gain:

and require . This is an evaluation alternative, not the original paper’s definition.

The Loop 3 synthetic result table uses:

base score                                  0.600
full-reference score                        0.850
historical 0.9 * full threshold             0.765
90% normalized-gain threshold               0.825

DID median score at d = 4 / 6 / 8           0.750 / 0.780 / 0.830
SAID median score at d = 2 / 4 / 6 / 8      0.600 / 0.770 / 0.810 / 0.840

Under the historical threshold, the grid estimates are DID and SAID . Under the normalized-gain threshold, both first pass at . These are deliberately synthetic scores used to test selection semantics. They are not Aghajanyan et al.’s measurements.

0x02G Crossing, Bracketing, Censoring, And Non-Monotonicity

A result record has three possible boundary states:

crossed within grid:
    first passing tested d and previous tested d form a grid bracket

first tested d already passes:
    left-censored; report d_estimate <= d_min, not d_estimate = d_min

no tested d passes:
    right-censored or optimization-unreached; report > d_max / unresolved,
    not d_estimate = d_max

Random-subspace scores need not be monotone in across independently sampled projections. A larger candidate can receive an unlucky subspace, optimizer path, or hyperparameter choice. Do not force scores through a cumulative maximum before publishing them. Define the selection rule, preserve raw results, and report uncertainty across seeds.

For the synthetic DID table, fails and passes, so the tested-grid bracket is . This is not proof that every integer between four and six behaves monotonically.

0x02H What The Primary Protocol Actually Ran

The pinned language-model study reports, for its sentence-prediction experiments:

dimensions d from 10 to 10,000 on a log scale
100 subspace-training runs per dataset/model sweep
a small search across four learning rates per training run
u initialized to zero so the base pretrained point is preserved
the randomly initialized classification head included in the d-coordinate budget
both DID and SAID implemented through a Fastfood-style transform

For its pretraining-trajectory experiment, it instead reports a binary search from 100 to four million and reuses learning rates under a stated rule. These are source-reported protocol details. They should not be blended into one fictional universal search.

The earlier objective-landscape paper used multiple projection constructions and, in several plots, defined crossing from the median of three runs. Its appendix explicitly treats the estimated intrinsic dimension as projection- and experiment-dependent. M6.7 preserves that caution rather than copying only a headline number.

0x02I Executable Direct And SAID Oracles

Loop 3 checks three independent mechanisms:

  1. a exact orthonormal teaching matrix verifies , gradient pullback, projector idempotence, rejected-gradient orthogonality, and adjoint parity;
  2. a six-block, width-four Fastfood-style rational trace verifies padding, block order, stacking, trimming, inverse permutation, transpose accumulation, and adjoint parity;
  3. a two-group SAID trace verifies the coordinate ledger, and gradients, the first- and second-order coefficients of its bilinear directional polynomial, and initialization blocking.

For a linear probe loss , perturbing both SAID coordinate classes gives:

The nonzero quadratic coefficient is direct evidence that learned group scales make the coordinate map bilinear rather than one fixed linear subspace.

0x02J Measurement Pseudocode

def estimate_intrinsic_dimension(
    pretrained,
    train_data,
    eval_data,
    candidate_dims,
    projection_seeds,
    hyperparameter_candidates,
    seed_aggregate=median,
    threshold_ratio=0.90,
):
    full_score = train_and_evaluate(
        model=clone(pretrained),
        trainable="all_parameters",
        train_data=train_data,
        eval_data=eval_data,
    )
    target = threshold_ratio * full_score

    records = []  # append-only run records; never overwrite failed seeds
    for d in candidate_dims:
        selected_seed_scores = []
        for seed in projection_seeds:
            projection = fixed_structured_projection(
                ambient_dim=pretrained.num_parameters(),
                subspace_dim=d,
                seed=seed,
            )
            trials = []
            for hyperparameters in hyperparameter_candidates:
                u = zeros(d, requires_grad=True)
                result = train_subspace_coordinates(
                    pretrained=pretrained,
                    coordinates=u,
                    projection=projection,
                    train_data=train_data,
                    eval_data=eval_data,
                    hyperparameters=hyperparameters,
                )
                trials.append(result)

            selected = select_by_declared_eval_rule(trials)
            selected_seed_scores.append(selected.score)
            records.extend(trials)

        aggregate = seed_aggregate(selected_seed_scores)
        append_dimension_summary(d, aggregate, selected_seed_scores)

    return classify_grid_crossing(
        raw_records=records,
        target=target,
        preserve_censoring=True,
    )

For SAID, subspace_dim=d must be replaced by shared_dim=d-m, and the manifest must count the learned scales inside the same total budget. A classification head, prompt parameters, or other trainable branch must likewise be included or separately disclosed.

0x02K What The Result Does And Does Not Mean

The experiment supplies an empirical upper-bound estimate under the sampled subspaces and training procedure. Failure at dimension does not prove that no useful -dimensional subspace exists; the sampled map, coordinate metric, optimizer, budget, or hyperparameter search may have failed. A seed aggregate passing does show that the declared protocol reached its threshold at a tested coordinate budget.

It still does not establish:

that every random subspace of dimension d succeeds
that the exact minimum lies at the first passing grid value
that another projection family has the same coordinate geometry
that a per-layer update has matrix rank d
that a LoRA adapter with rank d is equivalent
that lower protocol dimension causes better generalization
that source-reported model-size trends extrapolate universally

Publish the raw run table, projection and seed identities, optimizer/search budget, metric direction, full and base references, threshold definition, aggregation rule, and censoring state. Without that envelope, is a slogan rather than a measurement.

0x03 The Geometry Of One LoRA Update

Loop 3 measured a global optimization-coordinate protocol. This section changes objects. It studies one matrix:

represented by:

The owner question is: how many locally distinct matrix directions does this factorization represent, and which factor-coordinate changes leave the matrix unchanged?

LoRA factor geometry and effective degrees of freedom

0x03A Row Space, Column Space, And Rank Bound

Every output column of is a linear combination of the columns of :

Likewise, every row is a linear combination of the rows of :

Therefore:

Applied to one input :

extracts latent input coordinates. maps those coordinates into output directions. The factor-role interpretation is useful, but the letters are not universal across papers or codebases. M6.3 remains authoritative for the repository’s operator orientation.

0x03B Exact Rank, Rank At Most, And The Strata Boundary

Three sets must remain separate:

and the factor-coordinate space:

Vandereycken proves that is a smooth embedded manifold. The closure also contains lower-rank strata. Those lower-rank points are singular for the rank-at-most- variety: one cannot attach the same rank- tangent dimension to every factor product.

Standard LoRA parameterization maps all of into . It does not guarantee that , , or realize rank during training.

0x03C Derivation One: Choose Two Subspaces And An Invertible Core

At a generic exact-rank point, write a compact SVD:

The column space is a point in the Grassmannian , whose dimension is:

The row space contributes:

Once the two subspaces are fixed, the map between them is an invertible core with coordinates. Hence:

This derivation counts represented matrices directly. It does not begin from LoRA factors.

0x03D Derivation Two: Factor Coordinates Minus The Fibre

The factors store:

coordinates. For every invertible :

so an entire -dimensional change of latent basis represents the same matrix. Billaud-Friess et al. formalize this fixed-rank geometry through a principal bundle whose typical fibre is .

Subtracting the fibre dimension gives the same count:

This is not a claim that factor entries are individually unused. The redundancy is a coupled transformation of both factors.

A concrete shear makes the equivalence visible:

and change, their norms and conditioning can change, but their product does not.

0x03E The Factor Map Differential And Its Adjoint

Perturb both factors:

The first-order factor-to-matrix map is therefore:

The quadratic remainder is why the full feasible set is not one linear subspace. The tangent image is linear only after the base factors are fixed.

For an ambient probe , Frobenius adjointness gives:

Thus:

This is a geometry identity and an executable transpose check. M6.3 owns the complete LoRA backward operator, dropout, scale, and base-weight integration. Loop 7 will own optimizer dynamics and conditioning.

The tensor and flattening contract used by the Loop 4 oracle is:

factor perturbation vector[20]:
    vec_row_major(dot_B[4,2])
    then vec_row_major(dot_A[2,6])

Dphi Jacobian J_phi[24,20]:
    one output column per factor-coordinate basis vector
    each output column = vec_row_major(dot_B A + B dot_A)

ambient matrix vector[24]:
    vec_row_major(dot_W[4,6])

Changing any one of those orders changes the Jacobian even though every shape still fits.

0x03F The Infinitesimal Gauge Is The Differential Kernel

Let for arbitrary . Then:

and:

The associated factor perturbation is:

Applying the differential:

When has full column rank and has full row rank, these independent gauge directions span the entire kernel of . Rank-nullity then gives:

This proves the same dimension a third way: by the rank of the local factor-to-matrix Jacobian.

0x03G Tangent Space From The Compact SVD

For , Vandereycken gives:

with:

The three blocks have dimensions:

and sum to . The first block changes the core inside the current row/column spaces. The second rotates the column space. The third rotates the row space.

For full-rank factors with , the same tangent space is the image:

The factor differential and SVD chart are two coordinate descriptions of the same local matrix directions.

0x03H Normal Space And Orthogonal Tangent Projector

Define the orthogonal subspace projectors:

For any ambient matrix , the Frobenius-orthogonal tangent projection is:

The equivalent normal component is:

Expanding the normal expression proves the decomposition:

The normal space can also be recognized without an SVD. A matrix is orthogonal to every exactly when:

Its dimension is:

so ambient dimension reconciles:

Do not confuse with one Euclidean SGD step in arbitrary factors. The former is the orthogonal matrix-space projection. The latter depends on the chosen factor gauge and optimizer metric.

Factor gauge, tangent image, and normal-space decomposition

0x03I Exact , Rank-Two Reconciliation

The Loop 2 matrix schema fixes:

m = 4 output rows
n = 6 input columns
r = 2 configured factor width
ambient matrix coordinates             = 4*6                 = 24
factor coordinates                     = 4*2 + 2*6           = 20
finite/infinitesimal GL(2) gauge       = 2*2                 = 4
generic exact-rank-2 manifold          = 2*(4+6-2)           = 16
normal-space coordinates               = (4-2)*(6-2)         = 8
tangent + normal                       = 16 + 8               = 24
factor - gauge                         = 20 - 4               = 16

The exact fixture chooses:

so has rank two. The factor Jacobian has shape , exact rank 16, and nullity four. Four gauge basis vectors generated by the elementary matrices lie in its kernel and have rank four, so they span that kernel.

For an ambient probe containing row-major values 1 through 24, retains the first two rows and the first two columns of the last two rows. retains only the lower-right block. The oracle verifies:

P_T + P_N equals the original probe
P_T and P_N are Frobenius orthogonal
P_T is symmetric and idempotent as a 24x24 operator
Dphi* satisfies exact dot-product parity
every normal probe satisfies B^T N = 0 and N A^T = 0

0x03J What Breaks At A Lower-Rank Factor Point

Now keep full row rank but set . The represented matrix is rank zero, not rank two. The differential becomes:

All directions disappear at first order. For the fixture, the differential rank drops from 16 to:

This is the exact local geometry behind the familiar first-step asymmetry of a zero-product initialization. It does not mean training is permanently confined to eight dimensions: once moves, the path can open. Loop 7 derives that time-dependent optimization behavior.

The key distinction is:

configured factor width r:
    storage and rank upper bound

realized product rank:
    rank of BA at one checkpoint

factor-Jacobian rank:
    number of first-order matrix directions available at (B,A)

rank-r manifold dimension:
    generic local dimension only when the represented matrix has exact rank r

0x03K Coordinate Choices And Design Alternatives

RepresentationCoordinatesRedundancy or constraintLocal implication
unconstrained factors gaugesimple dense factors; Euclidean optimizer is gauge-dependent
compact SVD nominally entriesStiefel constraints plus sign/rotation conventionsexposes row, column, and core geometry; updates require constraint handling
quotient-manifold factors effectivegauge classes are identified by the metric/connectionremoves vertical directions conceptually; needs specialized optimization
fixed , train row subspace fixed by first-order image is at most and cannot rotate the row basis through
fixed , train column subspace fixed by first-order image is at most
fixed row and column bases, train coreboth subspaces fixedchanges only the map inside existing subspaces
dense updateno rank restrictionmaximal local freedom and full training state

This table compares geometry, not benchmark quality. M6.4 owns adaptation-method selection and composition. M6.7 only states what each coordinate choice can represent locally.

0x03L Executable Geometry Oracle

def factor_map_jacobian(B, A):
    columns = []

    # Row-major B coordinates first.
    for i in range(B.rows):
        for j in range(B.cols):
            dot_B = basis_matrix(B.shape, i, j)
            columns.append(row_major_flatten(dot_B @ A))

    # Then row-major A coordinates.
    for i in range(A.rows):
        for j in range(A.cols):
            dot_A = basis_matrix(A.shape, i, j)
            columns.append(row_major_flatten(B @ dot_A))

    return stack_columns(columns)  # [m*n, m*r+r*n]


def tangent_project(Z, U, V):
    P_U = U @ U.T
    P_V = V @ V.T
    return P_U @ Z + Z @ P_V - P_U @ Z @ P_V


def normal_project(Z, U, V):
    return (I_m - U @ U.T) @ Z @ (I_n - V @ V.T)

The checked oracle uses exact rational elimination rather than a floating-point rank tolerance. It obtains a factor Jacobian of rank , a four-dimensional nullspace spanned by the four elementary gauge directions, a rank- tangent projector, and a rank- normal projector. At the lower-rank fixture with full-row-rank , the same coordinate map has differential rank and nullity . All 58 one-field counterexamples are rejected. Later empirical rank diagnostics must name their numerical threshold separately.

0x03M Per-Layer Restrictions Compose Through A Nonlinear Network

If every adapted matrix has rank at most , the end-to-end function change need not have rank in any simple global sense. Residual connections, nonlinearities, attention, and layer composition combine local matrix changes.

Conversely, a desired end-to-end behavior may require several layers to change jointly even if each local update is low rank. Adapting more projection types at modest rank can therefore outperform placing a larger rank on one matrix in a specific experiment. That observation is source-reported evidence, not a theorem obtained from the manifold dimension.

0x04 Reconstruction: What Rank Can Approximate

0x04A Freeze The Object Before Decomposing It

The reconstruction target is not an unnamed “fine-tuning direction.” It is the immutable Loop 2 object:

with object ID matrix_delta:W_full-minus-W_0:layer0.linear:v1, output-by-input orientation, and one fixed checkpoint-selection contract. Changing the base revision, adapted tensor, subtraction order, or checkpoint creates a different matrix and invalidates the comparison.

For , its compact singular value decomposition is:

where , , and:

The full SVD may add orthonormal columns spanning unused complements. Those extra columns do not change the nonzero singular expansion. Compact and full SVD are storage choices, not different reconstructions.

0x04B Why Truncation Solves The Frobenius Problem

The singular expansion is a sum of Frobenius-orthogonal rank-one atoms:

Keeping the first atoms gives:

and orthogonality immediately gives its tail error:

That calculation proves the residual of truncation, but optimality requires a lower bound for every other rank-at-most- matrix . Let project onto any -dimensional subspace of . Then , so:

The Rayleigh—Ritz minimum over all such projectors selects the right-singular directions with the smallest eigenvalues of . Its value is . Truncation reaches that lower bound, which is the Eckart—Young least-squares result.

The spectral-norm lower bound has an equally useful geometric proof. The -dimensional space must intersect in a nonzero vector. For a unit in that intersection:

and reaches the bound:

For the Frobenius objective, a strict gap makes the rank- truncated matrix unique. A tie at the boundary permits several optimal -dimensional singular subspaces. “The SVD” therefore does not always identify one unique factor pair, and the gauge from 0x03 means even a unique reconstructed matrix has many factorizations.

0x04C Matrix Reconstruction And LoRA Optimization Are Different Experiments

One exact factorization of the truncation is:

A balanced choice can split across both factors. The two choices are gauge-equivalent matrix representations when all retained singular values are nonzero. Neither is the trajectory produced automatically by stochastic LoRA training.

post-hoc truncated SVD
    input: one already-measured dense update
    operation: deterministic matrix decomposition
    objective: best matrix residual under a named norm

LoRA optimization
    input: base model, factors, data, optimizer, and initialization
    operation: bilinear training through the model loss
    objective: training objective under a finite budget

SVD answers whether a dense reference is compressible after the fact. It does not prove that rank- LoRA reaches the same matrix, the same function, or the same task quality.

0x04D Exact Rank Sweep

The executable fixture uses:

Therefore . Every row below is reconstructed from the declared factors using exact rational arithmetic:

retained squared energyretained singular-value mass
0
1
2
3
4

The second and third columns are deliberately both present. “Retains 90% of the singular values” is ambiguous: sum of singular values and sum of squared singular values are different mass policies.

0x04E Derive Sampled Output Error From Tensor Shapes

Weight-space Frobenius error weights every matrix entry equally. A linear layer sees inputs. Let:

The changed layer outputs are and , both in . Their mean squared residual is:

Move through the trace one operation at a time:

where:

Because is positive semidefinite, it has a positive-semidefinite square root. The same objective is:

This derivation explains the final form: calibration variance stretches input directions before reconstruction error is measured.

0x04F Full-Rank Covariance Turns The Problem Into A Whitened SVD

If , multiplication by is invertible and preserves rank. Define:

Then , so:

Eckart—Young now applies to , not generally to :

The matrix to decompose is . Replacing the square root by changes the objective. CorDA is a useful context-oriented design alternative, but its decomposition of pretrained and inverse-covariance reconstruction belong to CorDA’s method contract; they are not this output-error theorem.

0x04G Singular Covariance Exposes A Calibration Blind Spot

Real activation covariances can be singular because , features are dependent, or some directions are absent. Let:

on the observed support. A minimum-norm optimal representative is:

where denotes the Moore—Penrose pseudoinverse. But any matrix satisfying is invisible to the sampled loss:

Such additions can change matrix rank and behavior outside the calibration support. The sampled objective therefore does not identify a unique global update. It identifies behavior only on directions represented by .

0x04H Same Rank, Different Winner: An Exact Counterexample

The immutable train_v1 split is the six-dimensional identity basis. It gives , so its raw output residual equals the Frobenius residual and its mean output residual is one sixth of that value. This validates tensor orientation, but it cannot expose a difference in direction weighting.

Loop 5 therefore adds a separately named sensitivity probe, without replacing train_v1:

The ordinary weight-space rank-one truncation keeps the first axis because . The transformed update is:

so the output-weighted rank-one solution keeps the second axis. Exact direct multiplication and the covariance trace agree:

rank-constrained candidateretained update axisraw mean output residual
weight-SVD rank oneaxis 1, value
output-optimal rank oneaxis 2, value
weight-SVD rank twoaxes 1 and 2

The output optimum is five times better than the weight optimum at the same rank. Yet the zero covariance on input axes 4—6 means this probe assigns zero loss to some nonzero residuals. Better calibration fit is not a task-safety guarantee.

SVD reconstruction, output weighting, and distinct rank diagnostics

0x04I Rank Is A Family Of Named Policies

For the same fixed matrix with spectrum , the immutable policies report:

policydefinitionresultwhat it answers
configured LoRA rankfactor bottleneck widthmaximum rank the configured factors can express
algebraic rankexact count of nonzero singular valuesexact matrix rank
numerical rankcount rank under one relative tolerance
stable rankcontinuous spectral concentration
99% energy ranksmallest with squared-energy prefix at least budget for one named energy threshold
entropy-energy rank, continuous effective count under squared energy
task-sufficient ranksmallest rank passing target, retention, and stress gatesnot measured heredeployment adequacy under one protocol

Numerical rank depends on scale and tolerance. The threshold probe uses singular values with . Because the frozen policy is strictly greater than, the boundary value is excluded and the numerical rank is two. A >= implementation would silently return three.

0x04J Two Entropy Conventions Must Not Share One Label

Roy and Vetterli’s effective rank normalizes singular values:

For this gives . The Loop 2 manifest deliberately defines a different entropy-energy diagnostic:

Both are valid continuous summaries when named. They are not the same statistic. For the zero matrix the normalization has zero mass, so the manifest explicitly returns effective rank zero instead of dividing by zero or inventing a probability distribution.

0x04K Tensor And Code Trace

def reconstruct_by_rank(delta, ranks):
    # delta: [d_out, d_in], immutable dense-update object
    U, sigma, Vh = svd(delta, full_matrices=False)
    rows = []

    for r in ranks:
        # Unbalanced exact factors; balanced square-root factors are optional.
        B_r = U[:, :r] * sigma[:r][None, :]   # [d_out, r]
        A_r = Vh[:r, :]                       # [r, d_in]
        delta_r = B_r @ A_r                   # [d_out, d_in]
        residual = delta - delta_r

        rows.append({
            "rank": r,
            "frobenius_squared": sum(residual * residual),
            "spectral": sigma[r] if r < len(sigma) else 0,
        })

    return rows

Output-weighted reconstruction needs an explicit support tolerance distinct from the numerical-rank tolerance:

def output_weighted_rank_r(delta, X, r, covariance_tol):
    # X: [N, d_in]; delta: [d_out, d_in]
    C = (X.T @ X) / X.shape[0]                # [d_in, d_in]
    eigenvalues, Q = eigh(C)                  # ascending PSD spectrum
    keep = eigenvalues > covariance_tol

    Qp = Q[:, keep]                           # [d_in, support_rank]
    sqrt_lam = sqrt(eigenvalues[keep])
    C_sqrt = (Qp * sqrt_lam[None, :]) @ Qp.T
    C_pinv_sqrt = (Qp / sqrt_lam[None, :]) @ Qp.T

    transformed = delta @ C_sqrt              # [d_out, d_in]
    transformed_r = truncated_svd(transformed, r)
    delta_r = transformed_r @ C_pinv_sqrt     # minimum-norm representative

    direct = sum_square(X @ (delta - delta_r).T) / X.shape[0]
    traced = trace((delta - delta_r) @ C @ (delta - delta_r).T)
    assert_close(direct, traced)
    return delta_r

Production code must pin dtype, accumulation dtype, SVD backend, convergence status, singular-value ordering, covariance cutoff, and tie behavior. Randomized SVD can reduce cost for large matrices, but it changes the evidence class from exact decomposition to an approximation with seed, oversampling, iteration, and residual checks.

0x04L Alternative Design Choices

design choiceadvantagecost or failure boundary
exact compact SVDdeterministic reference for small matricesexpensive at model scale
randomized or iterative SVDtargets leading componentsapproximation error and seed/backend state must be recorded
Frobenius truncation of data-independent matrix diagnosticcan prioritize directions absent or rare in deployment inputs
output-weighted truncationmeasures one sampled function tracecalibration shift and covariance nullspace can hide failures
per-layer independent replacementlocalizes residuals and tensorsignores cross-layer compensation and nonlinear composition
joint end-to-end replacement sweepmeasures actual composed behaviormore expensive and confounds which layer caused failure
post-hoc decompositiondiagnoses an existing dense referencedoes not explain how to train the low-rank model
direct LoRA trainingoptimizes the task objective in factor coordinatesmay not match the dense reference or its singular subspaces

CorDA, PiSSA, LoftQ, and rank-allocation methods make different choices about which matrix is decomposed, which residual remains in the base, and which components become trainable. M6.4 owns those method contracts. This section supplies the diagnostic algebra used to compare them without collapsing their objectives.

0x04M What A Small Reconstruction Residual Does Not Prove

The evidence ladder is strict:

small weight-space residual
    -> the measured matrix is compressible under one norm

small sampled-output residual
    -> the replacement is close on one captured activation distribution

preserved end-to-end target metric
    -> the composed model passes one target evaluation

preserved retention and stress metrics
    -> the candidate passes the declared deployment gates

No arrow is reversible without additional assumptions. A low SVD tail does not prove LoRA optimization succeeds. A low sampled-output error does not cover covariance-nullspace directions. A local layer match does not prove a multilayer nonlinear model match. Practical rank selection therefore requires all four evidence levels, not a single spectrum plot.

0x05 Reconstruction, Expansion, And Composition

The A22 decomposition taxonomy separates three questions that are often collapsed into one word, rank:

reconstruction
    Can one rank-r matrix approximate one already-defined dense update?

expansion
    Does a sequence of rank-limited stages accumulate new directions?

composition
    What operator results when independently trained updates are added,
    weighted, selected, or routed?

The first question was closed in 0x04. This section owns the second and the static algebraic boundary of the third. M6.9 owns learned routing and serving of multiple adapters.

Three low-rank operations: reconstruction, expansion, and composition

0x05A Freeze The Composition Object Before Adding Matrices

For stage or task , freeze:

and a scalar coefficient . A static composition is:

The coefficients, factor revisions, target module, orientation, dtype, and merge order are part of the object identity. A sum of adapters trained against different base checkpoints is not automatically a meaningful sum in one common coordinate system.

0x05B Derive The Concatenated Factorization And Its Tighter Rank Bound

Put all output factors side by side and all scaled input factors on top of one another:

where . Block multiplication gives:

Therefore:

The familiar bound is only the loosest part. Output-space reuse limits ; input-space reuse limits ; coefficient cancellation can reduce the final product further.

The exact fixture uses two rank-one updates with coefficients 2 and 3:

Both construction paths reconstruct exactly and the result has rank two.

0x05C Why More Stages Do Not Guarantee More Rank

For two rank-one updates and , additive rank growth requires more than a new vector on one side. If is collinear with , then:

and the sum remains rank at most one even when and are independent. The dual statement holds when the row direction is shared:

For two nonzero rank-one terms, independent left vectors and independent right vectors make the sum rank two. Higher-rank sums can still lose dimensions through cross-term cancellation, so actual rank must be measured after composition.

The executable ledger makes each boundary explicit:

compositionleft updateright updaterank of sumreason
aligned amplification1same row and column directions
new row, shared column1 has rank one
new column, shared row1 has rank one
independent both sides2both concatenated spans expand
exact cancellation0coefficients cancel the matrix

Gauge-invariant subspace diagnostics and exact rank-sum outcomes

0x05D Directional Novelty And Destructive Interference Are Different

Subspace novelty asks whether row or column spans expand. Interference asks what the coefficients do inside those spans. The Frobenius norm exposes the cross term:

Positive alignment amplifies. Negative alignment cancels. Orthogonality in matrix Frobenius geometry removes this one cross term, but it does not prove two task objectives are compatible after the updates pass through a nonlinear network. Row-space overlap, column-space overlap, matrix inner product, sampled-output interference, and end-to-end task interference are separate measurements.

0x05E Post-Hoc, Staged, And Joint Composition Are Different Experiments

experimentwhat is trainedbase seen by later updateswhat can be concluded
post-hoc static sumadapters trained independentlyusually the same frozen basealgebraic merge and interference of frozen artifacts
merge and reinitializeone stage at a timestage sees the previously merged basetrajectory-dependent rank expansion under an explicit reset policy
jointly trained parallel factorsall factor blocks togetherone shared evolving effective operatorcoupled optimization under one loss
orthogonality-constrained stagesnew stage plus overlap penaltyprior subspaces frozen or referencednovelty under the selected row, column, or matrix metric
post-hoc SVD compressionno training in the decomposition stepone already-composed matrixbest approximation under the selected residual norm
conditional mixturerouter and one or more adaptersinput- or token-dependent pathnonlinear/routed operator, not one static merge

Merge-and-reinitialize can fail to expand rank when each stage relearns the same directions. Forcing orthogonality can increase novelty while harming transfer if tasks share useful structure. Joint training can coordinate cancellation or specialization, but its factors are not equivalent to independently trained artifacts merely because their final shapes match.

0x05F Why Input-Dependent Composition Is Not Generally Mergeable

If coefficients depend on the current input:

then is generally nonlinear even when every is linear. A one-dimensional exact counterexample needs only:

For , the adapter output is . For , it is . Any fixed linear matrix that maps to must map to , not . Therefore no one constant merged matrix reproduces this gated operator on both inputs.

Special cases can still collapse to a static merge: constant gates, algebraically redundant experts, or a restricted finite input set may admit one equivalent matrix. That is an equivalence to prove, not a default property of routing. M6.9 owns router gradients, task provenance, batching, cache identity, and runtime integration.

0x05G Tensor And Code Trace

def compose_static(adapters, coefficients):
    # Each B_j: [d_out, r_j]; A_j: [r_j, d_in].
    B_cat = concat([B_j for B_j, _ in adapters], axis=1)
    A_cat = concat([
        coefficient * A_j
        for coefficient, (_, A_j) in zip(coefficients, adapters)
    ], axis=0)

    delta_from_factors = B_cat @ A_cat
    delta_from_sum = sum(
        coefficient * (B_j @ A_j)
        for coefficient, (B_j, A_j) in zip(coefficients, adapters)
    )
    assert_close(delta_from_factors, delta_from_sum)
    return delta_from_sum

For staged expansion, persist the update matrix or a rank-revealing decomposition at every stage. Comparing only current factors is insufficient because factor gauge can change without changing the update.

for stage in stages:
    delta_stage = reconstruct_adapter(stage.B, stage.A)
    delta_total = delta_total + stage.coefficient * delta_stage

    report({
        "rank_stage": numerical_rank(delta_stage, tolerance),
        "rank_total": numerical_rank(delta_total, tolerance),
        "row_basis": right_singular_basis(delta_total, tolerance),
        "column_basis": left_singular_basis(delta_total, tolerance),
        "task_metrics": evaluate_target_and_retention(model, delta_total),
    })

The tolerance, decomposition backend, coefficient dtype, accumulation dtype, base revision, and stage order belong in the artifact manifest.

0x05H Composition Alternatives And Failure Boundaries

designuseful whenfailure boundary
sum merged matricescoefficients are static and artifacts share one base contractdestructive cancellation or rank growth beyond release budget
concatenate factors without dense mergeruntime supports a larger live adapterextra adapter FLOPs and memory scale with total factor width
compress composed matrix by SVDone static release needs a lower rankreconstruction loss can erase task-specific directions
orthogonalize new stagenovelty is explicitly desiredshared useful directions are suppressed
select one adaptertasks are separable and identity is knownselector error and fragmented batching
mix adapters with dynamic gatesinputs benefit from conditional sharingno global merge; routing and provenance become runtime state

0x06 Subspace Similarity, Principal Angles, And The LoRA Experiment

Subspace comparison must answer four questions before reporting one scalar:

Which matrix object is decomposed?
Is the input-side row space or output-side column space compared?
How is numerical rank selected?
Does the normalization mean similarity, containment, or directed coverage?

Without those fields, a heatmap can be visually precise and mathematically ambiguous.

0x06A Raw Factor Entries Are Not Gauge-Invariant Objects

Take the exact rank-two update:

and the invertible coordinate change:

Define and . Then:

but the raw factor diagnostics change:

Scaling can make factor norms vary arbitrarily while preserving the product. Entrywise distance, factor cosine, and unaligned factor norms therefore do not define an intrinsic distance between LoRA updates.

0x06B Extract Gauge-Invariant Row And Column Bases

For one reconstructed update with numerical rank :

define:

and projectors:

The bases can rotate inside a repeated-singular-value subspace, but the projectors remain unchanged. At full factor rank, and . Under rank collapse, those equalities can shrink, so decomposing is safer than assuming configured factor width equals learned update rank.

A rank-revealing QR can extract a span without a full SVD. The SVD is still needed when comparison means leading energy-ordered directions rather than the complete numerical span.

0x06C Derive Principal Angles From One Cross Matrix

Let and have orthonormal columns, and let . The first principal angle solves:

Write and . The objective becomes:

over unit and , whose maximum is the largest singular value of the cross matrix. Constraining later vectors to be orthogonal to earlier principal vectors recursively yields:

This is the QR-then-SVD numerical contract developed by Björck and Golub: rank-reveal the input spans, orthonormalize them, then decompose the small cross matrix. Computing an SVD directly on arbitrary raw factors measures factor scaling and conditioning as well as span geometry.

0x06D Derive Projection Overlap, Chordal Distance, And Projector Distance

Because the squared Frobenius norm is the sum of squared singular values:

The original LoRA normalization is:

The squared chordal/projection distance used by that normalization is:

Therefore the correct normalized identity is:

Projector distance keeps unequal-rank surplus dimensions visible:

For equal rank , this reduces to . For unequal ranks it also charges the dimensions that have no paired principal angle.

0x06E Exact Principal-Angle Ledger

The immutable fixture compares the base row space with four alternatives. The -- case uses:

so the principal cosines are and the angles are .

row-space caseprincipal cosines
identical
-- rotation
one shared direction
orthogonal

These are exact rational checks, not rounded output from a numerical SVD. A production run must additionally record decomposition backend, dtype, singular-value cutoff, convergence status, and ordering/tie policy.

0x06F Row And Column Spaces Answer Different Questions

For :

row space in R^n
    Which input directions can the update read or distinguish?

column space in R^m
    Which output directions can the update write?

The fixture’s column_partial case has identical row spaces but only one shared output direction:

row principal cosines       = (1, 1), overlap = 1
column principal cosines    = (1, 0), overlap = 1/2

One score cannot substitute for the other. Comparing only the down-factor row space can miss a changed output builder; comparing only the up-factor column space can miss changed input features.

0x06G Min-Rank Normalization Means Containment, Not Equality

Let:

Then and , so:

The score correctly says the smaller subspace is fully contained in the larger. It does not say the spaces are equal. Directed coverage keeps both statements:

For this example:

Always report both directed coverages when retained ranks differ. Alternatively, report projector distance, which charges the unmatched dimension automatically.

0x06H A Random Baseline Depends On Ambient Dimension And Rank

A raw overlap value has no rank-free random baseline. For independent Haar-distributed subspaces with ranks in , rotational symmetry gives:

Hence:

and:

For , , and , the expected projection mass is one and the normalized overlap is . A heatmap cell of can therefore be strong or unremarkable depending on ambient dimension, retained ranks, and null model. Learned subspaces are not Haar random; the formula is a baseline contract, not a p-value.

0x06I Procrustes Aligns Basis Coordinates Only After Span Extraction

Two orthonormal bases of the same subspace can differ by an orthogonal coordinate rotation. For equal rank, solve:

If:

then the orthogonal Procrustes solution is , and:

The fixture rotates the basis of by 90 degrees. Its raw basis difference is four, its projector difference is zero, and its aligned difference is zero.

This procedure begins after QR or SVD has produced orthonormal bases. It does not solve arbitrary gauge in raw LoRA factors. Projectors and principal angles remain the primary invariant diagnostics; aligned bases are useful only when direction-by-direction correspondence is needed.

0x06J What The Original LoRA Experiment Actually Compares

The original LoRA paper’s Section 7.2 and Appendix G compare the leading right singular-vector directions of learned down factors and in selected GPT-3 attention projections. These vectors live in the common input ambient space even though the two factor matrices have different configured ranks. The paper notes that an analogous left-singular analysis can be done for .

Original LoRA paper subspace-similarity heatmaps

Source: LoRA, Figure 3. The source reports that the leading directions for the rank-8 and rank-64 factors overlap in the tested layer and that one shared direction has normalized similarity above 0.5 for the shown query/value cases. The paper also compares rank-64 runs across seeds and random Gaussian matrices. These are source-reported experiments, not reproduced measurements here.

The distinction between factor row space and update row space matters. If has full column rank, . If collapses rank, some directions in do not survive into . A modern replication should report both factor-space and reconstructed-update diagnostics rather than silently treating them as identical.

0x06K Executable Tensor Trace

def subspace_report(delta_left, delta_right, tolerance):
    # Both updates are [d_out, d_in] and share the same module identity.
    U_l, s_l, Vh_l = svd(delta_left, full_matrices=False)
    U_r, s_r, Vh_r = svd(delta_right, full_matrices=False)

    rank_l = count(s_l > tolerance * s_l[0])
    rank_r = count(s_r > tolerance * s_r[0])

    Qcol_l = U_l[:, :rank_l]                 # [d_out, rank_l]
    Qcol_r = U_r[:, :rank_r]                 # [d_out, rank_r]
    Qrow_l = Vh_l[:rank_l, :].T              # [d_in, rank_l]
    Qrow_r = Vh_r[:rank_r, :].T              # [d_in, rank_r]

    def compare(Q_l, Q_r):
        cross = Q_l.T @ Q_r                  # [rank_l, rank_r]
        cosines = svdvals(cross)              # length min(rank_l, rank_r)
        mass = sum(cosines * cosines)
        p = min(Q_l.shape[1], Q_r.shape[1])

        return {
            "principal_cosines": cosines,
            "principal_angles": arccos(clip(cosines, 0, 1)),
            "min_rank_overlap": mass / p,
            "left_covered_by_right": mass / Q_l.shape[1],
            "right_covered_by_left": mass / Q_r.shape[1],
            "chordal_squared": p - mass,
            "projector_distance_squared": (
                Q_l.shape[1] + Q_r.shape[1] - 2 * mass
            ),
        }

    return {
        "row": compare(Qrow_l, Qrow_r),
        "column": compare(Qcol_l, Qcol_r),
    }

Near one, clip principal cosines only after recording the unclipped floating-point excess. A value such as is a numerical symptom, not a physical angle. Rank-zero updates need an explicit policy because min-rank normalization would divide by zero.

0x06L A Reproducible Subspace Protocol

1. Freeze base checkpoint, target module, factor orientation, adapter revision,
   dataset, seed, optimizer, step, and merge state.
2. Reconstruct the exact update matrix in a named accumulation dtype.
3. Select algebraic or numerical rank with an explicit threshold and tie rule.
4. Extract both row and column orthonormal bases.
5. Compute principal cosines from the small cross matrix.
6. Emit angles, projection mass, min-rank overlap, both directed coverages,
   chordal distance, and projector distance.
7. Add a rank- and ambient-dimension-matched random baseline.
8. Report matrix inner products and sampled-output interference separately.
9. Evaluate target, retention, and stress metrics before claiming compatibility.
10. Preserve all artifacts needed to rerun the decomposition.

The immutable Loop 2 protocol already required principal angles and normalized overlap. Loop 6 makes the basis, rank, side, coverage, and null-model fields executable instead of changing that historical contract.

0x06M What Similarity Does And Does Not Prove

observationsupported interpretationunsupported leap
at equal ranksthe two numerical subspaces coincidethe update magnitudes or task effects coincide
at unequal ranksthe smaller span is contained in the largerthe larger has no additional directions
low row overlapupdates read different input directionstasks cannot transfer
low column overlapupdates write different output directionstheir end-to-end outputs never interfere
high overlap across stagesstages reuse directionsthe matrix sum has identical coefficients or quality
high overlap across seedsstable span under the tested protocoluniversal intrinsic rank
low random-baseline-adjusted overlapmore separation than the chosen nullstatistical significance without a sampling protocol

The original LoRA result does not establish that every task has rank one, every layer has the same useful rank, rank-64 tails are useless, another optimizer learns the same directions, or intrinsic dimension equals a shared matrix-subspace dimension. It supports a narrower source-reported conclusion: leading factor directions were shared across some tested ranks and seeds while low configured ranks remained competitive in those experiments.

0x07 Initialization Is An Optimization Contract, Not A Zero-Product Trick

M6.3 owns the implemented LoRA operator, its tensor shapes, and its local backward pass. This section consumes that closed contract and asks a different question:

Once two factors represent the same initial update, what motion does the optimizer induce in the represented matrix?

The answer requires freezing more than . A reproducible dynamics statement must name:

product order and factor shapes
which factor entries are random, zero, or structured
factor-entry variance as width and rank change
adapter scale s
learning rate for each factor
simultaneous or sequential factor updates
optimizer state, epsilon, clipping, and decay
factor and optimizer-state dtypes

The exact Loop 7 fixture uses , , one frozen dense gradient , exact rational arithmetic, and simultaneous plain-SGD gradients evaluated at the same old factor state. It is a local algebra oracle, not a model-training experiment.

LoRA factor dynamics, gauge conditioning, rank scaling, and optimizer boundaries

0x07A Derive The Factor Gradients From One Differential

Let:

with:

The differential of the product is:

Using the Frobenius inner product:

Therefore:

and:

The formulas are reciprocal. The current scale and orientation of determine the gradient seen by ; the current scale and orientation of determine the gradient seen by .

0x07B Derive Motion In Product Space

Under continuous plain gradient flow with factor-specific rates and :

Differentiate the represented update rather than either factor:

Substitution gives:

This is not ordinary dense gradient descent on . Factorization inserts two state-dependent operators:

TermActs onGeometric role
input side of right preconditioning by the row geometry of
output side of left preconditioning by the column geometry of

At a zero- start only the right-preconditioned path exists. At a zero- start only the left-preconditioned path exists. Once both factors move, the two paths interact.

0x07C Exact Tensor Trace

Freeze:

Then:

The two product-space contributions are:

and:

Thus:

The exact fixture recomputes every entry from the factors. The values are not copied from a paper table.

0x07D A Simultaneous Finite Step Has An Extra Product Term

For simultaneous old-state SGD:

Expanding gives:

The first two terms are the Euler approximation to the continuous flow. The third is a finite-step multiplicative cross term. In the exact trace:

Therefore:

An implementation that updates , recomputes from the new , and then updates executes a different sequential algorithm. The distinction is not an implementation footnote: it changes the finite-step map.

0x07E Derive The Weighted Gram Invariant And Its Scope

Both and are latent-coordinate Gram matrices. Under the frozen continuous flow above:

and:

Divide by the corresponding learning rates and subtract:

For the exact trace, the conserved matrix is:

This local derivation is related to the balancedness lineage for homogeneous factorizations in Du, Hu, and Lee (NeurIPS 2018). It does not establish that the same matrix is conserved by finite steps, sequential updates, clipping, factor decay, adaptive moments, stochastic rounding, or arbitrary mixed-precision LoRA code.

0x07F Four Zero-Product Mechanisms

The statement "" hides different derivative states.

Initial LoRA factor gradients under three zero-factor choices

Standard: random , zero

The first product motion is:

is initially a fixed input-side feature map. This is the initialization specified by the original LoRA paper: random Gaussian , zero , and therefore zero initial adapter output.

Reversed: zero , random

with:

The initial function is identical to the standard start, but the first gradient is projected on the output side instead of the input side.

Both factors zero

Ordinary first-order optimization cannot leave this point.

Both factors nonzero but

Zero product does not imply a zero factor. For example:

gives , yet the exact fixture obtains:

Both factors can move immediately. A zero function perturbation, a zero factor, and a dead first-order state are three different claims.

0x07G The Initialization Paper Varies Width, Not Rank

The Impact of Initialization on LoRA Finetuning Dynamics compares two zero-product paths under a specific asymptotic contract:

Paper notationRandom factorZero factorAsymptotic variable
Init[] with entry variance model width , rank fixed
Init[] with entry variance model width , rank fixed

Using the paper’s learning-rate exponent notation, its analysis reports:

Init[A]: stable when gamma[eta] <= -1/2
         efficient feature learning at gamma[eta] = -1/2

Init[B]: stable when gamma[eta] <= -1
         cannot efficiently train both factors in that asymptotic setup

Those are theorem-scoped statements. They do not establish a universal finite-width learning rate, optimizer-independent superiority, or a rank-scaling law.

Source-reported optimal LoRA learning rate versus model width for two initializations

Source-reported evidence: Figure 2 from “The Impact of Initialization on LoRA Finetuning Dynamics,” arXiv:2406.08447v1, extracted without redrawing under the paper’s CC BY 4.0 license. The paper reports that the selected learning rate decreases with width and differs between Init[] and Init[] in its experiment. This repository did not reproduce the runs.

0x07H Tensor And Optimizer Trace

The gradient calculation and the factor update must be separate operations:

def factor_gradients(B, A, G, scale):
    grad_B = scale * (G @ A.T)
    grad_A = scale * (B.T @ G)
    return grad_B, grad_A


# Both gradients read the same old factor state.
grad_B, grad_A = factor_gradients(B, A, G, scale)

B_next = optimizer_B.step(B, grad_B)
A_next = optimizer_A.step(A, grad_A)

delta_before = scale * (B @ A)
delta_after = scale * (B_next @ A_next)
product_step = delta_after - delta_before

For diagnostics, record both the factor-space and product-space quantities:

diagnostics = {
    "norm_A": frobenius_norm(A),
    "norm_B": frobenius_norm(B),
    "norm_grad_A": frobenius_norm(grad_A),
    "norm_grad_B": frobenius_norm(grad_B),
    "norm_product": frobenius_norm(scale * (B @ A)),
    "norm_product_step": frobenius_norm(product_step),
    "right_gram": A.T @ A,
    "left_gram": B @ B.T,
    "latent_balance": B.T @ B / eta_B - A @ A.T / eta_A,
}

The final line is a diagnostic under a named plain-flow comparison. It is not an assertion that a practical optimizer must conserve it.

0x07I Factor Letters Are Not An Interface

Some papers and libraries swap the letters used for the down and up projections. A statement such as “initialize to zero” is therefore not portable. State the full ABI:

down factor: [r, d_in]
up factor: [d_out, r]
product order: up @ down
zero factor: up or down
random-factor distribution and variance
stored scaling and factor-specific optimizer groups

M6.3 owns the checkpoint and merge implementation of that ABI. M6.7 owns the consequence: changing any one field can change the trajectory even when the step-zero product is unchanged.

0x08 Factor Gauge, Scaling, Optimizers, And Conditioning

0x08A Feature Extractor And Output Builder Are Source-Scoped Roles

For , maps an input into latent coordinates and maps those coordinates into the output space. Asymmetry in Low-Rank Adapters of Foundation Models studies this distinction and reports settings in which freezing a random projection factor while training the output-building factor remains competitive.

That result does not make one factor universally disposable. It depends on the paper’s random-feature assumptions, models, tasks, ranks, and optimization protocol. If the fixed input projection omits task-relevant directions, training only cannot create them.

0x08B Gauge-Equivalent Factors Need Not Follow Gauge-Equivalent Paths

For nonzero scalar :

But the Gram operators become:

With unchanged factor learning rates:

The exact fixture uses . The product remains , but the equal-rate velocity changes from:

to:

Loop 4 established that gauge-equivalent factors represent one matrix. Loop 7 establishes the complementary fact: Euclidean factor optimization is coordinate-dependent.

0x08C A Local Plain-Flow Gauge Compensation

To preserve the two coefficients in the immediate continuous flow after , , choose:

For :

and the exact immediate product velocity matches the base velocity.

The compensation also holds for finite plain-SGD steps, not only for the immediate velocity. Under the gauge, and , so one simultaneous step with the compensated rates gives:

The new factors are again gauge-equivalent, so . The multiplicative cross term of 0x07D is included: , and the and gradient scales cancel. In the exact trace both parameterizations reach:

Because depends only on the product, the next gradient is the same in both runs, and the argument repeats at every step. Plain SGD with compensated rates therefore follows the same product trajectory; only operations that act on factor coordinates break the match:

factor clipping thresholds are coordinate-dependent
factor decay is coordinate-dependent
adaptive moments carry their own coordinate history
finite-precision range depends on factor magnitude

0x08D Why The Compensation Does Not Transfer To Adam

At the first bias-corrected Adam step from zero moments, ignoring weight decay:

so each coordinate uses:

Under the scalar gauge, scales by while scales by . The additive prevents these directions from being homogeneous rescalings. Even before later moment history appears, the plain-flow learning-rate compensation is no longer an optimizer equivalence.

With , the exact oracle obtains:

but the compensated gauged factors produce:

They are not equal. This one-step counterexample does not characterize long-run AdamW behavior; it disproves a simpler and commonly implied claim that a plain-SGD gauge compensation automatically transfers to an adaptive optimizer.

0x08E Factor Decay Is Not Product Decay

A factor penalty:

becomes, under the scalar gauge:

Although is unchanged, the penalty is not. Its balancing gauge satisfies:

In the exact case, the base penalty is and the same-product penalty is . Applying L2 regularization or decoupled weight decay to factors therefore chooses a factor gauge as well as constraining magnitude. It is not equivalent to regularizing .

0x08F Derive Rank Scaling Together With Initialization Variance

At the standard start:

Suppose the rows of are independent, zero mean, and have coordinate covariance:

Then:

and:

The first -gradient moment obeys the matching dependence:

Parameterize both choices:

The rank exponent of the initial product velocity is:

Rank-independent scale requires:

This derivation explains why a scaling rule cannot be judged independently of factor initialization:

Initialization varianceStable exponent Corresponding scale
factor-entry variance independent of rank0
factor-entry variance proportional to 10constant

rsLoRA analyzes the first regime and motivates under its stated assumptions. The result is not assumption-free and does not say that every existing initialization must use the same scale.

0x08G Exact Rank Ledger

The exact fixture repeats rows and compares ranks and . Its row-coordinate second moment is .

Factor normalizationScaleCoefficient at Coefficient at Trend
rank-independent rows, shrinks
rank-independent rows, stable
rows divided by , shrinks
rows divided by , constant stable

The table is not a quality benchmark. It verifies one initial product-velocity coefficient exactly.

0x08H Rank Asymptotics And Width Asymptotics Are Different Experiments

Two primary sources vary different axes:

SourceVariesHolds fixed or assumesSupports
initialization dynamics, arXiv:2406.08447v1model width rank fixed; source-specific variance and LR exponentswidth-dependent stability and feature-learning analysis
rsLoRA, arXiv:2312.03732v1adapter rank source-specific initialization moments and optimization assumptionsrank-dependent adapter scaling

One cannot substitute for in either theorem. A practical sweep may vary both, but then it is a third protocol and must report both variance rules and both scale rules.

0x08I Dtype Feasibility Is Gauge-Dependent

In exact arithmetic:

If those coordinates are stored directly in IEEE binary16:

largest finite value: 65504
smallest positive subnormal: 2^-24

c = 2^16:
    B' = 65536 is above the finite range

c = 2^-25:
    B' is below the smallest subnormal
    A' = 2^25 is above the finite range

The product is mathematically identical, but the factor representation is not equally storable. This is a coordinate witness, not a claim that every LoRA run stores master factors or optimizer state in binary16. M6.3 owns the actual mixed-precision state contract; M8 owns general numerical representation.

0x08J Alternative Factor-Training Designs

The derivations expose several genuinely different choices:

DesignTrainable stateInitial product pathBenefit soughtMain limitation
random , zero , train bothboth factorsright-preconditioned first motionstandard zero-output start and later feature learningasymmetric early dynamics
zero , random , train bothboth factorsleft-preconditioned first motionreverse output-side startnarrower stable-rate regime in the cited width analysis
freeze random , train output builder onlyfixed right preconditionerfewer trainable parameters and fixed random featurescannot change the input projection
train both with factor-specific ratesboth factors plus two optimizer groupsrate-weighted left/right motionrebalance factor movementratio is protocol-dependent
data- or weight-informed initializationmethod-specificstructured initial subspacealign early motion with selected directionschanges state conversion and evidence contract
periodic rebalancing or refactorizationfactors plus transformation stateproduct preserved at transform timeimprove factor conditioningoptimizer moments must also be transformed or reset

M6.4 owns named variants such as LoRA+, rsLoRA, PiSSA, and LoRA-FA. This table explains the dynamical axes that those methods alter; it does not re-open their implementation catalog.

0x08K Training And Resume Integration

A trajectory-reproducible checkpoint needs more than a merged :

base checkpoint identity
A and B tensors with shapes and dtypes
stored scale and rank
initialization family and random seed when relevant
optimizer class and per-factor parameter groups
optimizer moments, step counters, and epsilon
weight-decay and clipping policy
gradient-accumulation and loss-scaling state
factor rebalance or conversion history

Merging into preserves the current function but destroys the factor gauge and generally cannot reconstruct optimizer moments. Resuming factor training from an arbitrary refactorization is a new optimization trajectory even if its first forward pass is identical.

For distributed training, factor ownership and optimizer-state sharding also matter. The mathematical gradients may be identical while reduction order, overflow handling, or per-shard clipping changes the realized step. Those are implementation claims and require runtime evidence rather than matrix algebra alone.

0x08L Failure Lab And Diagnostics

FailureObservable symptomRoot causeCorrective evidence
both factors initialized to zeroadapter remains exactly zeroboth first-order gradients vanishgradient-nonzero assertion after first backward
same , different training curvefactor norms or optimizer state differgauge-dependent gradients and optimizer coordinatesfactor, moment, and product-step logs
high rank learns more slowly with initial product step shrinks with rankscale and initialization variance imply negative rank exponentfreeze , , and gradient-moment ledger
still shrinks was already normalized by scale and initialization both divide rank growthderive before the sweep
balancedness diagnostic driftsfinite step, clipping, decay, or Adam usedcontinuous-flow invariant applied outside contractcompare against named optimizer schedule
factor penalty changes after exact refactorizationsame product receives different regularizationfactor L2 is gauge-dependentlog factor penalty and product penalty separately
merged checkpoint cannot resume equivalentlyloss jumps or path diverges after refactorizationfactor and moment identity was discardedpreserve live factors and optimizer state
NaN, inf, or zero factor after rebalancefactor gauge exceeds storage rangeexact product equivalence ignored dtypepre-transform range and post-transform finite checks

The minimum diagnostic record for a rank or initialization comparison is:

step and tokens processed
loss and evaluation protocol
||A||_F, ||B||_F, ||sBA||_F
||grad_A||_F, ||grad_B||_F
||Delta_{t+1} - Delta_t||_F
singular values and numerical rank of Delta
factor-specific learning rates and update norms
optimizer moments or their summary statistics
overflow, clipping, and skipped-step counters

Without that record, a claim about “initialization” may actually be a claim about scale, optimizer grouping, factor gauge, or finite-precision behavior.

0x09 A Kernel Explanation Is A Conditional Trajectory Model

The owner question is not merely, “What is the NTK at initialization?” It is:

Under which parameter coordinates, optimizer metric, data split, scale, and training horizon does an initial tangent model predict the actual adaptation trajectory?

Loop 7 established that equal products need not have equal factor-coordinate dynamics. Loop 8 carries that result into function space. It owns the derivation from factor Jacobians to empirical kernels, the distinction between an instantaneous current-kernel identity and a frozen-kernel approximation, and the diagnostics that can falsify the approximation. It does not re-own the vanilla LoRA operator from M6.3, variant training recipes from M6.4, serving kernels from M6.5, routed composition from M6.9, or the expressive-power theorems in 0x0A.

0x09A Freeze The Function, Dataset, Axes, And Optimizer Metric

Let a fixed probe split contain examples and let the model expose measured outputs per example. Stack those outputs in a declared order:

and define the empirical Jacobian:

where is the number of trainable coordinates in the protocol being studied. Changing from full weights to LoRA factors changes , the columns of , and the optimizer state associated with those columns. Changing the output selection, example order, token mask, dropout state, or probe split changes the rows. A kernel comparison without these axes is not reproducible.

For a loss , write the output gradient as:

Plain parameter gradient flow obeys:

The chain rule then gives an instantaneous exact identity:

This statement does not freeze anything. The empirical tangent kernel can change continuously with the parameters.

For a fixed symmetric positive-semidefinite parameter metric or preconditioner :

Thus even a local kernel is optimizer-coordinate dependent. is the Euclidean plain-SGD metric, not an optimizer-independent property of the function.

0x09B A Frozen Kernel Adds Two Approximations

Taylor-expand around the pretrained or adapter initialization :

where is the nonlinear remainder. The corresponding linearized model is:

Training that linearized model with plain gradient flow gives:

Calling the nonlinear run “fixed kernel” therefore makes two claims:

  1. linearization: remains small on the measured outputs;
  2. fixed features: remains close enough to under the relevant optimizer metric.

Malladi et al. use these as separate parts of their kernel-behavior definition. The distinction matters: one finite step can have zero Taylor remainder while still activating a factor Jacobian that changes all later tangent features.

Fixed-kernel and feature-learning adaptation regimes

The original NTK paper proves a constant limiting kernel for specific infinite-width networks under its parameterization, initialization, and gradient-flow assumptions. It does not define every finite empirical kernel to be constant. Chizat, Oyallon, and Bach further show that lazy behavior depends on scaling. Yang and Hu construct different infinite-width parameterizations that retain feature learning. Width alone is therefore not the contract; parameterization and update scaling are part of it.

0x09C Restricting Coordinates Produces A Metric, Not Automatically A Projector

Suppose full parameters are restricted through fixed coordinates:

The Jacobian with respect to is:

Euclidean gradient flow in induces:

If , then is the orthogonal projector onto the chosen parameter subspace. If columns are merely scaled, structured, or non-orthogonal, also contains that coordinate metric. Calling every such object “the projected full kernel” hides a consequential design choice.

For scalar output rows of :

A Johnson—Lindenstrauss argument can preserve these pairwise inner products for a finite set of gradient features with high probability when the normalized random projection is sufficiently wide. The rank depends logarithmically on the number of protected pairs and inversely on the requested error. This is a probabilistic finite-dataset statement. It does not guarantee preservation for all inputs, all checkpoints, or a factor map that later changes.

0x09D Derive The Two LoRA Factor Jacobians

Consume M6.3’s orientation:

For a batch matrix , isolate one linear layer:

With column-major vectorization, use the identity :

and also:

Therefore:

The concatenated factor Jacobian and its plain-SGD empirical kernel are:

Expanding the Kronecker products gives:

For full-weight coordinates:

At the usual start, . Only the random path contributes:

This is the tensor-level form of the random-projection explanation. In a deep network, the layer’s upstream output sensitivities multiply this input Gram term. Malladi et al.’s Appendix D writes the resulting layer kernel as the Hadamard product of an output-sensitivity Gram and the projected input Gram. Their theorem then applies a finite-set random-projection bound under a named SGD and kernel-behavior contract.

0x09E Initialization-Time Preservation Is Not Trajectory Preservation

The exact fixture chooses:

This deliberately uses full rank so the initialization algebra is transparent; it is not a compression result. Under the declared parameter order :

and:

Use target:

and loss . With simultaneous plain SGD and :

so:

The first output step is exactly tangent because did not move. But now:

and the kernel becomes two copies of:

The fixture reports:

relative Jacobian drift squared = 3/16
relative kernel drift squared   = 7/128
kernel alignment squared        = 361/366

High alignment does not mean equality, and exact first-step linearization does not imply fixed features.

Exact LoRA initialization-kernel equality, Jacobian drift, and second-step prediction trace

0x09F The Second Step Separates Current Tangent, Frozen Kernel, And Exact Factors

At state one, the old-state gradients are:

For simultaneous changes , the exact finite update is:

The current-tangent model includes the middle two terms. The last term is finite bilinear curvature. The frozen-kernel model additionally replaces by . The three state-two outputs are:

Their exact difference exposes the finite factor cross term:

The squared errors are:

The frozen-kernel discrepancy is larger because it combines feature drift with finite bilinear curvature. Reporting only one aggregate error cannot identify which approximation failed.

0x09G A Smaller Rank Can Delete Probe Directions

Now set , , and on the same fixture. Then:

so:

The projected kernel has rank two while the full kernel has rank four, with squared Frobenius discrepancy two. This deterministic case does not contradict the random-projection theorem. It shows why the theorem needs randomness, normalization, a sufficiently large projection dimension, a finite protected set, and a probability statement.

0x09H The Optimizer Changes The Kernel Analog

For plain SGD, the tangent metric is:

For a fixed preconditioner, it is . Adaptive moments make depend on coordinate history, data order, clipping, epsilon, and decay. There need not be one fixed symmetric matrix that describes the full trajectory.

Malladi et al. analyze an early-stage SignGD approximation to Adam and define an asymmetric kernel analog:

For the exact probe:

the three candidate objects are:

The asymmetric analog is visibly not and not symmetric. The source paper also studies a symmetric sign-feature variant for kernel regression. Neither object licenses replacing a general late-stage AdamW run with the plain-SGD NTK.

0x09I What The Source Experiment Actually Shows

Malladi et al. compare a pretrained model, its initial linearization, and the actual fine-tuned model across their task and prompt protocols. The gap varies substantially across tasks and between SGD and Adam. That is evidence that kernel behavior must be measured under the protocol rather than presumed from model size.

Source-reported pretrained, linearized, and fine-tuned task results from Malladi et al. Figure 2

The image is a crop of Figure 2 from A Kernel-Based View of Language Model Fine-Tuning, reproduced without redrawing under CC BY 4.0. It reports the authors’ experiments on their selected tasks, prompts, optimizers, splits, and hyperparameters. It is not a result of the exact fixture and not a universal comparison between LoRA and full fine-tuning.

The paper’s LoRA preservation argument has an explicit implication order:

full fine-tuning exhibits kernel behavior under the named protocol
    plus
the normalized random LoRA projection preserves finite-set gradient inner products
    implies
the LoRA kernel analog is close on that protected set

Reversing that implication is invalid. A close initialization kernel does not prove that the nonlinear full-fine-tuning or LoRA trajectory stays in the kernel regime.

0x09J Diagnostics Must Separate Three Residuals

On an immutable probe split, record at every diagnostic checkpoint:

and a scale-insensitive kernel alignment:

These answer different questions:

DiagnosticDetectsDoes not prove
failure of the initialization Taylor model on selected outputsthat the kernel itself is stable
coordinate-level gradient-feature driftuseful learned representations; it is gauge and parameterization sensitive
drift of the chosen tangent metric on the probe splitlow drift off the probe split or under another optimizer metric
directional agreement after discarding overall scaleequal convergence rate or equal kernel magnitude
task and retention metricsoperational learning and forgettingmechanism without the trajectory diagnostics

Parameter distance alone is insufficient. Loop 7 showed that an exact factor gauge can make and arbitrarily large or small while preserving ; conversely, a modest parameter move can materially change selected function outputs.

0x09K Do Not Materialize A Production-Scale Kernel

For large models, use Jacobian-vector and vector-Jacobian products. For random output probes :

and estimate kernel-difference energy with:

The probe distribution, count , seed, output stacking, dtype, and estimator uncertainty are part of the result.

probe = freeze_probe_split(
    examples=probe_examples,
    output_selector=selected_logits,
    dropout=False,
    order="example_then_output",
)

theta0 = load_adapter_initial_state()
F0 = forward(theta0, probe)

for checkpoint in checkpoints:
    theta_t = load(checkpoint)
    Ft = forward(theta_t, probe)
    F_linear = F0 + jvp_at(theta0, theta_t - theta0, probe)

    for z in fixed_random_output_probes:
        K0_z = jvp_at(theta0, vjp_at(theta0, z, probe), probe)
        Kt_z = jvp_at(theta_t, vjp_at(theta_t, z, probe), probe)
        accumulate_kernel_drift(Kt_z - K0_z)

    record(
        output_linearization_residual=relative_error(Ft, F_linear, F0),
        kernel_drift_estimate=finalize_probe_estimator(),
        optimizer=optimizer_state_contract(checkpoint),
        task_metrics=evaluate_target(checkpoint),
        retention_metrics=evaluate_retention(checkpoint),
    )

If the optimizer metric is , compute instead of silently using . For AdamW this requires a declared approximation to moment state and decoupled decay; there is no automatic fixed-kernel shortcut.

0x09L Training And Runtime Integration

A defensible experiment runs at least three matched paths:

  1. the nonlinear LoRA model with both factors trainable;
  2. the initialization-linearized LoRA model under the same declared optimizer analog;
  3. a fixed-random-feature path that freezes the initially nonzero factor.

Optionally add full fine-tuning, but match data order, tokens, batch construction, checkpoint selection, output definition, and evaluation cadence. “Same learning rate” is not automatically a fair comparison when parameter coordinates and optimizer metrics differ.

Checkpoint state must include:

base checkpoint and tokenizer identity
adapter factor tensors, scale, orientation, and target modules
optimizer moments, step counters, clipping, decay, and scheduler
probe-split identity and selected output coordinates
dropout/eval state and numeric precision
JVP/VJP estimator seeds and probe vectors
linearization base point and checkpoint distance
target, validation, and retention measurements

Kernel diagnostics are offline evidence. They do not change the merge or serving ABI owned by M6.3 and M6.5. A deployment still serves the nonlinear adapter unless a separate release explicitly packages a linearized surrogate.

0x09M Design Alternatives Expose Different Assumptions

DesignMoving features?Kernel objectWhat it isolatesMain limitation
initialization linearizationno or declared optimizer metricfrozen-kernel predictionomits feature drift and finite curvature
freeze , train no factor-feature change in this linear-layer pathprojected random-feature kernelrandom projection adequacycannot rotate the input factor
train both yes after the zero factor movesbilinear feature adaptationkernel and factor gauge evolve
fixed orthonormal subspace noglobal coordinate restrictionnot layer-local low-rank geometry
plain full fine-tuningmodel dependentfull empirical NTKunrestricted tangent featureshighest trainable state and forgetting risk
fixed preconditioned flowmaybeoptimizer metric sensitivityfixed does not model adaptive history
SignGD analogsource-contract dependentasymmetric sign kernelearly normalized-gradient behaviornot a general AdamW trajectory theorem
feature-learning parameterizationyes by construction in the cited limitevolving/data-adapted featuresrich-regime alternativetheorem assumptions differ from finite LoRA

0x09N Paper-By-Contract Comparison

SourceFrozen objectMain result consumed hereRequired boundary
Jacot, Gabriel, and Honglerlimiting NTK under their infinite-width setupfunction-space kernel gradient and constant limiting kernelfinite LoRA empirical kernels need not be constant
Chizat, Oyallon, and Bachinitialization linearization under lazy scalinglazy behavior is scaling-induced and paths can be bounded near linearizationlaziness is not synonymous with overparameterization alone
Yang and Huparameterization-dependent infinite-width limitfeature learning can survive a different infinite-width scalingnot a direct finite-LLM LoRA guarantee
Malladi et al.optimizer-specific initialization kernel analogkernel-behavior definition, LoRA projected-kernel formula, finite-set preservation, task evidencemeaningful only when the underlying fine-tuning protocol exhibits kernel behavior
Jang, Lee, and Ryuan NTK-regime affine prediction problemlow-rank solution and landscape theoremsowned by 0x0A; not evidence that a practical run remains in the NTK regime

0x09O Kernel-Regime Failure Lab

FailureHidden collapseObservable consequence
quoted as fixed-kernel proofcurrent kernel vs an exact chain-rule identity is misread as a lazy-training theorem
initial kernel equality treated as trajectory equalityinitialization vs pathactivated columns and later drift are ignored
first-step Taylor equality treated as long-run linearizationone zero gradient vs persistent fixed featuressecond-step bilinear cross term appears unexplained
called a projector without subspace vs coordinate metricscaling changes the apparent kernel
random projection theorem applied to deterministic rank oneprobabilistic finite-set guarantee omittedprotected directions disappear
layer-local input Gram treated as the whole network kernellocal Jacobian vs upstream sensitivityoutput-gradient geometry is absent
used for AdamWplain SGD metric vs adaptive historykernel prediction follows the wrong update direction
low alone called kernel behaviorfixed features vs output linearizationnonlinear remainder can still be large
high kernel alignment called equalityangle vs magnitudelearning rates and convergence times disagree
Jacobian drift called beneficial feature learningmotion vs utilityfeatures move while target and retention quality worsen
parameter distance used without gauge normalizationfactor coordinates vs functionexact refactorization looks like large learning
probe split reused for model selection without disclosurediagnostic vs selection dataoptimistic kernel-fit evidence
source Figure 2 treated as a LoRA benchmarkfull-fine-tuning source protocol vs local fixtureunrelated methods and tasks are conflated

0x09P Loop 8 Handoff

Loop 8 establishes what a kernel explanation can and cannot claim. Loop 9 may now study expressive-power and NTK-regime optimization theorems, but it must consume this boundary: a theorem stated inside an NTK model does not prove that an observed nonlinear training run entered or remained inside that model.

0x0A Expressive Power, Optimization Geometry, And Deep Composition

The phrase “rank is enough” is incomplete. Enough to represent one matrix? Enough for a constructive deep-network existence theorem? Enough to remove spurious second-order stationary points in a perturbed linearized objective? Enough to compress one gradient-descent trajectory?

Those are different questions with different mathematical objects. Loop 8 already established another boundary: a theorem inside an NTK model does not prove that an observed nonlinear run entered or stayed in that model. This section consumes that boundary rather than silently discarding it.

0x0AA Owner Contract: Carry The Quantifiers With The Rank

Every claim in this section must declare six coordinates:

CoordinateQuestion that must be answered
ObjectOne matrix, a product of matrices, a ReLU FNN, a Transformer, a linearized empirical loss, or a training trajectory?
QuantifierDoes the result say “there exists,” “for every target,” “with probability one,” or “almost every perturbation”?
ArchitectureWidth, depth, residual path, weight shapes, biases, target modules, and nonlinearities?
OptimizationNo optimizer, gradient descent, second-order stationary points, or an optimizer-specific trajectory?
Rank statementNecessary, sufficient, an upper bound, an approximation tail, or a configured factor width?
ExclusionWhich practical conclusion is not proved?

Four distinct low-rank theorem contracts

The section owns theorem assumptions, proof structure, exact finite counterexamples, and diagnostics. It does not reopen M6.3’s vanilla operator, M6.4’s variant catalog, M6.5’s multi-tenant serving state, or M6.9’s routed composition system.

0x0AB One Known Matrix: Exact Rank Is Necessary And Sufficient

Freeze one matrix and one target matrix . Their additive functionality gap is

An adapter with configured rank writes

Necessity is one line:

If , then necessarily

Sufficiency comes from the compact SVD. If

then for any one valid padded factorization is

Therefore, for one known additive matrix gap,

Below that threshold, Eckart—Young gives a different statement:

That is an optimal post-hoc matrix approximation. It does not say factor training finds the truncation, nor that a small weight residual preserves task behavior. Loop 5 owns those reconstruction and output-weighted distinctions.

Exact Trace

The Loop 9 fixture freezes

so

A rank-two factorization is

and exactly. The residual ledger is

Configured rankBest squared Frobenius residual

No deep-network rank has been inferred. The fixture has proved only what it computed.

0x0AC A Product Of Adapted Matrices Has A Telescoping Rank Budget

Depth changes the object. Let the frozen linear map be

and the adapted map be

Do not expand all interaction terms. Insert and subtract one partially adapted product at a time:

Each summand has rank at most . Therefore,

when every layer uses rank at most .

This derivation supplies a necessary rank budget for the product gap. It does not yet establish that every rank-at-most- gap can be allocated to valid layer updates. The constructive reverse direction needs the invertibility conditions in Zeng and Lee’s product lemma: left and right context products must remain invertible while the low-rank pieces are assigned sequentially.

Why Allocation Matters

Take two frozen identity layers and target product

One allocation puts the complete gap in the first layer:

with update ranks . Another distributes the gap:

with update ranks . Both satisfy

For the distributed case, the telescoping terms are

and

Their sum is the rank-two product gap. Depth reduced the maximum per-layer update rank from two to one without changing the end-to-end function.

This does not make rank additive in general. Loop 6 already showed that low-rank sums can align, cancel, or grow. Here the point is narrower: one end-to-end function can admit multiple layerwise allocations.

0x0AD From Product Algebra To ReLU FNN Expressivity

Zeng and Lee study whether adapters exist. Their paper explicitly excludes optimization and generalization from the expressive-power question.

Use separate notation for the two depths:

target FNN:
    depth L_target
    square width-D weights W_bar_i

frozen/adapted FNN:
    depth L_frozen >= L_target
    square width-D weights W_l + Delta W_l

The input domain is bounded, biases may be changed, and an ordered partition

assigns consecutive frozen layers to each target layer. For one partition block, define its matrix functionality gap

Why Bias Updates Appear

A product lemma alone is linear. To make a block of ReLU layers implement one target ReLU layer, the construction uses biases in the earlier layers of the block to keep their preactivations positive over the bounded input set. Those ReLUs then act linearly. The final layer in the block restores the target preactivation and target bias before the remaining ReLU.

So the proof does not say arbitrary intermediate ReLUs disappear during ordinary training. It constructs biases that linearize selected intermediate layers over the theorem’s bounded domain.

This yields an immediate scope requirement:

theorem construction allows bias updates
!=
bias-frozen LoRA implementation

If a practical setup freezes all biases, this proof cannot be imported unchanged.

0x0AE Uniform Partition And Uniform Rank

For a uniform partition, let

be the number of adapted layers assigned to each target layer. The telescoping argument gives each block an aggregate rank budget . Under the paper’s Assumption 1, a sufficient exact-recovery condition is

The denominator is not magic. It comes from distributing a partition gap across rank- layer updates:

The nonsingularity assumption is what makes the constructive sequential allocation feasible. For independently sampled continuous random weights, the paper proves its assumption holds with probability one and derives the generic sufficient threshold

“With probability one” applies to the random matrix model in the corollary. It is not a frequency claim about pretrained checkpoints, and is not a recommended sweep endpoint.

0x0AF General Partitions And Nonuniform Ranks

Uniform allocation can waste rank. If the first target layer already matches its assigned frozen block, its gap rank is zero. Giving that block the same rank as a difficult block spends parameters without improving the theorem’s coverage.

The nonuniform theorem assigns rank per adapted layer and requires, for every partition block,

This is a partition coverage condition. It is not a claim that only the scalar sum matters during training. Location, conditioning, activation patterns, and optimizer state can still make two equal-budget allocations behave differently.

The theorem also separates two design choices that benchmarks often collapse:

ChoiceChanged object
Partition Which frozen depth composes to approximate each target layer
Rank vector How much rank budget each adapted matrix receives

M6.4 owns named adaptive-rank algorithms. M6.7 owns the theoretical reason nonuniform allocation can matter.

0x0AG Below Exact Recovery: Propagated Singular Tails

When a partition does not have enough aggregate rank, define

This is the first omitted singular value of the -th partition gap, not the task loss. Zeng and Lee’s approximation theorem propagates these local approximation terms through the target network. In structural form,

where collects the paper’s input-covariance and target-weight/bias magnitude terms.

The shape of the bound matters:

  1. a discarded singular tail enters locally;
  2. later target layers can amplify that local error;
  3. input covariance and parameter magnitudes are part of the contract;
  4. the result is an existence bound for constructed adapters.

A small alone is not enough to claim a small final function error. A small theorem bound still does not establish optimizer reachability or held-out task quality.

0x0AH Transformer Expressivity: Reconstruct The Architecture Before The Headline

The paper’s Transformer result is not stated for an ordinary residual LLM block. Its formal setup freezes these coordinates:

target and frozen network:
    same number L of Transformer blocks
    same embedding dimension D
    every weight matrix represented as D x D
    multi-head self-attention followed by tokenwise FFN
    skip connections excluded for analytical feasibility

adaptation:
    attention K/Q/V/O adapters
    final block's second FFN matrix adapter
    output-matrix adapter
    updated bias vectors
    other low-rank adapters set to zero in the construction

The no-residual choice is not cosmetic. Residual addition changes the block function and the algebra by which an adapted block is matched to a target block.

Why The Rank Bound Contains A Division By Two

Attention exposes matrix products, not isolated weights. Score logits depend on a product like

Adapting both factors changes that product by

Each term has rank at most , so the product gap has rank at most . The value/output path has the same structure through products involving and , with FFN bridge matrices entering after the first block.

The paper defines a block functionality-gap rank from these score and value-path product gaps, and an output-layer gap . Under Assumption 4, its sufficient condition is

The proof aligns attention scores before softmax, aligns the first FFN output before ReLU, and then chooses the output path to finish the equality. Under that construction,

For independently drawn continuous random weights, the paper’s corollary yields the headline sufficient rank . The full statement is therefore:

D/2 is sufficient with probability one
for the paper's random same-size, D x D, no-residual Transformer model,
under its nonsingularity assumption and constructive adapter/bias placement.

It does not say:

rank D/2 is necessary for pretrained residual LLMs
rank D/2 is the best benchmark rank
gradient training will find the constructed adapters
smaller ranks cannot solve structured downstream tasks

0x0AI Expressivity Does Not Imply Trainability

An existence proof answers

Training asks whether a declared optimizer, initialization, data order, regularizer, and finite precision trajectory reaches a useful solution. Those questions are not logically equivalent:

The constructive adapters can depend on target weights that are not available in downstream fine-tuning. That is acceptable for an expressivity theorem and unusable as a direct training algorithm unless those objects can be estimated.

This is where the NTK paper enters. It does not strengthen the same theorem. It changes the object from a deep-network function class to a finite-data linearized optimization problem.

0x0AJ The NTK Problem Is A Linearized Full-Update Object

Jang, Lee, and Ryu select pretrained weight matrices

and stack their updates into one matrix variable

where and . The Jacobian feature object is block diagonal across the selected matrices.

For examples and output coordinates, the nonlinear network is replaced by its first-order model:

The loss is assumed convex, nonnegative, and twice differentiable in the model output. Cross entropy and mean squared error fit that loss-side assumption; the network linearization remains a separate regime assumption.

The empirical linearized loss is

This function is convex in the full matrix but nonconvex in the factors .

0x0AK Why Factor Weight Decay Becomes A Nuclear Norm

The factor identity

connects factor weight decay to the nuclear-norm-regularized full-update problem

This identity requires a compatible regularizer on both factors. It does not mean arbitrary decoupled AdamW, per-factor learning rates, clipping, or exclusion rules optimize the same matrix objective. Loop 7 already showed that factor-coordinate optimizer choices change product dynamics.

0x0AL Low-Rank Existence Comes From A PSD Lift And Dimension Counting

Introduce

The update is an off-diagonal block of . The lifted objective depends on through at most scalar linearized predictions plus the trace regularizer.

If a rank- optimum has a nonzero symmetric direction inside its column space that is invisible to all prediction constraints, one can move along that direction while preserving the objective until an eigenvalue reaches zero. The rank falls. Repeat until no such direction remains.

The symmetric matrices supported on an -dimensional range have dimension

The measurement operator has rank at most . At the terminal low-rank optimum, dimension counting gives

The theorem therefore says: if the nuclear-norm-regularized linearized full-update problem has a global minimizer, there exists at least one global minimizer whose rank obeys this bound.

It does not say every minimizer is low rank. It does not say the original nonlinear full-fine-tuning update has that rank. It does not say a rank- factor optimizer reaches that minimizer.

0x0AM The Landscape Theorem Uses The Opposite Strict Inequality

The no-spurious-second-order-stationary-point result requires the configured factor rank to satisfy

This is not a contradiction. The two inequalities answer different questions:

InequalityRank variableConclusion
rank of at least one full-update optimuma low-rank optimum exists
configured factor widthgeneric perturbed factorized landscape has no nonglobal SOSPs

The landscape objective is also perturbed:

where . For almost every nonzero , all second-order stationary points are global minimizers of this perturbed objective.

Three qualifiers are load-bearing:

  1. almost every nonzero perturbation is not deterministic ;
  2. second-order stationary point is not every first-order stationary point or arbitrary stopped checkpoint;
  3. linearized loss is not the original nonlinear network objective.

The paper explicitly notes that its theorem does not apply directly to the practical deterministic choice . Its corollary instead bounds how far a minimizer of a sufficiently small random perturbation can be from the optimum value of the unperturbed objective.

Exact Triangular-Number Trace

For and ,

The largest rank satisfying the existence inequality is because

The smallest configured rank satisfying the landscape inequality is because

Writing only "" erases , the triangular count, strictness, the change of rank variable, and the perturbation.

Exact expressive-power and deep-composition teaching oracle

0x0AN Source Geometry: Constraint Count Versus Low-Rank Surface

Jang et al.’s Figure 1 uses a matrix and a rank-one surface to visualize the existence theorem. As the number of scalar constraints increases from one to three, the affine set of global minima shrinks. At in that toy setup, the global-minimum set no longer intersects the rank-one surface, although a rank-two optimum remains.

Source-reported Jang et al. Figure 1 left panel with one constraint

Source-reported Jang et al. Figure 1 middle panel with two constraints

Source-reported Jang et al. Figure 1 right panel with three constraints

These are the unmodified plot panels extracted from Jang et al., Figure 1, under the PMLR CC BY 4.0 publication agreement. They are source-reported geometric evidence, not a repository reproduction. The surfaces illustrate one theorem’s dimension count; they do not establish an LLM rank rule.

0x0AO What The NTK Experiments Do And Do Not Validate

The source experiment uses a linearized RoBERTa-base model, prompt-based fine-tuning, examples, and labels on six NLP tasks. For that count,

first holds at . The paper compares training curves under its declared setup and reports convergence behavior consistent with the analyzed landscape.

That experiment is not a test of nonlinear production LoRA with arbitrary AdamW settings. It does not validate a universal square-root rank rule. A practical nonlinear run needs the Loop 8 diagnostics: linearization residual, Jacobian drift, kernel drift, optimizer metric, and probe-split discipline.

The paper also gives a generalization bound under additional assumptions, including bounded Jacobian-feature norms, an attained nonzero population optimum, a declared regularization choice, and the perturbed-objective setup. “No spurious SOSPs” and “generalizes well” remain separate theorems even inside the same paper.

0x0AP Deep Factorization Changes The Trajectory Object Again

Yaras et al. begin with deep square matrix factorization, not Transformer fine-tuning. Freeze

and solve

where

Initialization is scaled orthogonal:

Gradient descent with optional weight decay follows

These coordinates are part of the theorem. Replacing squared matrix-recovery loss by cross entropy, GD by AdamW, square factors by arbitrary Transformer projections, or scaled-orthogonal initialization by standard LoRA initialization changes the problem.

0x0AQ The Invariant Block Has Width , Not

Let

The source theorem constructs fixed orthogonal matrices with such that every iterate has block form

where

The complement does not have arbitrary matrix dynamics. It remains one repeated scalar whose recurrence is

Why ? The first gradient can involve both the target’s rank- row/column directions and their images through the initialized factors. Bounding the union of those active directions yields a coordinate block; the orthogonal complement is invariant under the paper’s updates.

This is a trajectory theorem under a highly structured matrix-recovery setup. It is stronger than observing a low numerical rank at one checkpoint and narrower than claiming every language-model update follows the same invariant coordinates.

0x0AR Compression Drops A Small But Nonzero Complement

Write for the first active columns. Because adjacent bases match, the product becomes

The first term is the compressed active product. The second is the complementary block. At small initialization it is small, not identically zero.

The source proposition bounds the squared difference by

The optimized active factors use

parameters instead of , while the outer bases are fixed by the compression construction.

Exact Finite-Initialization Trace

Take , , , and

Then

Keeping only the active block gives

with exact squared error

The source bound gives the same fixture value:

This exact block calculation illustrates the bound. It does not reproduce the source dynamics theorem.

0x0AS The Language-Model Observation Is Empirical Evidence

Yaras et al. also measure deep overparameterized updates while adapting BERT on STS-B. Their source Figure 2 reports three different observables: singular-value spectra across adapted layers, alignment between current and final top-right-singular-vector subspaces, and training loss.

Source-reported Yaras et al. Figure 2 singular-value spectra across adapted layers

Source-reported Yaras et al. Figure 2 current-to-final subspace alignment

Source-reported Yaras et al. Figure 2 training loss trajectory

These unmodified panels were extracted from Yaras et al., Figure 2, under the PMLR CC BY 4.0 publication agreement. They are source-reported evidence, not a repository reproduction.

The three panels should not be collapsed:

small later singular values:
    numerical low-rank observation

high current-to-final subspace alignment:
    trajectory-direction observation under one metric

loss still decreasing:
    objective progress after alignment

The paper uses that observation to motivate Deep LoRA. The matrix-recovery theorem does not prove these BERT trajectories satisfy its exact block decomposition.

0x0AT Deep LoRA: From Full-Width Initialization To A Compact Trainable Graph

The paper’s method starts conceptually with a deeper update

whose uncompressed factors are full width. The pinned JAX/Flax reference implementation then constructs a compact module with

where

Its parameter ledger is

For the source’s usual depth , this is vanilla LoRA’s two rectangular factors plus

additional trainable parameters per adapted matrix.

For and :

StateParameters
Vanilla outer factors
Deep LoRA outer factors
Three inner factors
Deep LoRA total

That is parameter efficiency, not state equivalence. The deeper graph carries more activations, gradients, and optimizer tensors than vanilla LoRA.

0x0AU Pinned Code Trace: Compression Is An Initialization Pipeline

The reference code’s compressed path is not “instantiate a narrow deep factorization at random.” It performs a source-specific pipeline:

def initialize_compressed_deep_lora(base_model, first_batch, rank, depth):
    # 1. Materialize full-width, depth-L orthogonal factors.
    wide = build_full_width_deep_factors(depth=depth, scale=epsilon)

    # 2. Evaluate their end-to-end updates and one batch gradient.
    wide_update = multiply_factors(wide)
    wide_grad = grad(task_loss)(wide, first_batch)

    # 3. Move parameters, updates, and gradients to CPU/NumPy.
    left_basis, right_basis = gradient_informed_compression(
        wide, wide_grad, wide_update, rank
    )

    # 4. Keep rectangular outer factors and initialize each inner factor.
    compact.outer_left = left_basis            # [d_out, r]
    compact.outer_right = right_basis          # [d_in, r]
    compact.inner = [epsilon * I_r for _ in range(depth)]

    # 5. Use separate optimizer groups for outer and inner factors.
    return compact, multi_transform(inner_optimizer, outer_optimizer)

The implementation explicitly moves compression work to CPU to reduce GPU pressure. It also warns that creating the uncompressed factors can itself run out of memory before compression. Therefore the runtime contract includes a transient initialization peak:

Only after compression does the steady trainable state become compact.

The code assigns a scaled learning rate to the outer factors and the main optimizer to the inner factors. Loop 7’s lesson applies directly: optimizer-group identity is part of the method, not incidental plumbing.

0x0AV Training And Runtime Integration Contracts

The source Deep LoRA experiment adapts all attention and feedforward weights in BERT-base, reports 72 adapted matrices, usually uses , uses Adam, and compresses from a full-width depth-three orthogonal initialization with scale . Its limited-data experiments select learning rates under a declared protocol and train to convergence in training loss.

Those are source-reported choices, not defaults for another model. A faithful implementation record needs:

architecture state:
    exact adapted parameter paths and matrix orientations
    depth L, configured rank r, outer/inner shapes

compression state:
    first batch identity and preprocessing
    full-width initialization seed and epsilon
    gradient snapshot and compression code revision
    resulting outer bases and inner factors

optimizer state:
    inner and outer optimizer groups
    learning rates, decay, moments, step counters

checkpoint state:
    compact factors and group labels
    compression metadata and source revision
    base-model identity

serving state:
    materialized Delta W or live deep factor chain
    merge dtype and accumulation order
    latency measured separately from parameter count

M6.5 owns serving many adapters. This section only states why a deeper factor graph changes load, merge, and checkpoint semantics.

0x0AW Design Alternatives Answer Different Questions

AlternativeWhat changesWhat it can answerWhat it cannot inherit automatically
One matrix adapterOne additive gapExact rank and SVD tailDeep function expressivity
Final-layer tuningDense freedom at the endWhether one late map is enoughDistributed product budget
Uniform LoRA ranksSame at every selected layerSimple capacity ledgerEfficient allocation when gaps differ
Nonuniform ranksRank vector and partitionCoverage of heterogeneous gapsOptimizer success
Constructive FNN/TFN adaptersSpecific weights and biasesExistence under theorem assumptionsReachability from LoRA initialization
NTK factorizationLinearized finite-data lossLow-rank optimum and perturbed SOSP geometryUnrestricted nonlinear training
Vanilla LoRATwo-factor updateLow-state adaptationDeep-factor implicit bias
Deep LoRAOuter factors plus inner chainSource method’s depth/compression tradeoffUniversal generalization gain

Final-layer tuning is especially instructive. Zeng and Lee show a random one-layer target cannot generically be matched by tuning only the final layers of their deeper frozen FNN, while distributed LoRA can meet their constructive conditions. The comparison is about where trainable changes enter the composition, not merely the count of scalar parameters.

0x0AX Paper-By-Contract Comparison

PaperMathematical objectCore rank statementOptimization objectStrongest safe conclusion
Zeng—Lee expressive powerProduct/FNN/TFN function equalityGap rank distributed across layers; TFN bound through NoneConstructed adapters exist under architecture and nonsingularity assumptions
Jang—Lee—Ryu NTKFinite-data linearized losslow-rank optimum with triangular count ; factor width with count Perturbed bilinear objective and SOSPsA low-rank optimum exists and almost every declared perturbation removes nonglobal SOSPs
Yaras et al. matrix recoveryDeep square matrix product trajectoryactive coordinate block width GD from scaled-orthogonal initializationThe structured trajectory is compressible up to a finite-initialization bound
Yaras et al. Deep LoRACompressed deep adapter methodouter rank plus depth- inner chainSource JAX/Flax training protocolSource-reported limited-data behavior under one implementation and experiment

The papers are complementary because they study different missing links:

expressivity:
    can suitable adapters exist?

NTK optimization geometry:
    can a factorized linearized objective avoid bad SOSPs under a perturbation?

compressible dynamics:
    can one structured overparameterized GD trajectory be represented in fewer coordinates?

No row subsumes the others.

0x0AY Expressivity And Deep-Composition Failure Lab

FailureCollapsed objectsObservable contradiction
called the required LLM rankone matrix vs deep functionanother layer allocation reaches the same function with smaller per-layer rank
rank budgets called additiveupper bound vs equalityaligned terms fail to grow rank or cancel
FNN theorem applied with frozen biasestheorem construction vs implementationintermediate ReLUs cannot be forced into the proof’s linear region
quoted without architecturerandom no-residual theorem vs residual pretrained modelskip path and matrix shapes violate the formal setup
existence called trainabilityrepresentation vs optimizer trajectoryconstructed solution exists but training does not reach it
used as a recipeasymptotic shorthand vs exact inequalities, triangular count, strictness, and perturbation disappear
P=0 called coveredperturbed theorem vs practical losstheorem explicitly quantifies almost every nonzero PSD
every stationary point called globalSOSP vs FOSPnegative-curvature first-order points are outside the conclusion
NTK theorem applied after large driftlinearized model vs nonlinear trajectoryLoop 8 linearization/Jacobian diagnostics fail
invariant block called rank target rank vs active coordinate widthsource decomposition has a trainable block
compression called exactsmall finite complement vs zero complementresidual equals
BERT observation called theorem proofsource experiment vs matrix recoveryloss, optimizer, architecture, and initialization differ
compact parameters called low peak memorysteady state vs initialization lifecyclefull-width factors and gradients exist before compression
Deep LoRA merged like vanilla without metadatatwo factors vs deep chaincheckpoint and optimizer-group state cannot be reconstructed

0x0AZ Loop 9 Handoff

Loop 9 closes four theorem boundaries:

  1. a single matrix gap has an exact rank characterization;
  2. depth can distribute a product gap under feasibility assumptions;
  3. NTK low-rank existence and perturbed-landscape coverage use different inequalities and quantifiers;
  4. invariant deep matrix dynamics and Deep LoRA language-model experiments are different evidence classes.

Loop 10 may now build the composite rank, reconstruction, kernel, and retention oracle. It must not convert theorem-sufficient rank into a practical selector, use the NTK result without Loop 8’s regime diagnostics, or treat source-reported Deep LoRA behavior as a local reproduction.

0x0B Rank, Reconstruction, Kernel, And Retention Oracle

The preceding loops deliberately refused to answer a deceptively simple question:

What LoRA rank should this product use?

That refusal was necessary. A singular-value tail answers a matrix approximation question. Principal angles answer a subspace question. Factor norms and gradients answer a trajectory question. A kernel comparison answers a conditional function-space question. An expressivity theorem answers an existence question under its assumptions. None of those objects, alone, selects a deployable rank.

Loop 10 joins them only after the training, validation, retention, stress, cost, checkpoint, and test contracts are immutable.

0x0BA Owner Contract: Select A Candidate, Not A Universal Rank

This section owns one bounded decision protocol:

input:
    a frozen candidate set
    matched training budgets
    validation-only checkpoint identities
    target, retention, and stress measurements
    reconstruction and trajectory diagnostics
    declared product constraints

output:
    one candidate selected for one release contract

not output:
    a universal LoRA rank
    a theorem-derived deployment recipe
    a reproduced paper benchmark
    a claim that low reconstruction error implies quality

The exact local oracle is synthetic. It validates the accounting and selection logic with rational values; it does not train a model. The Biderman et al. results remain source-reported empirical evidence.

Six bounded evidence contracts feeding one measured product decision

The ladder is intentionally not an implication chain. A candidate can have a small reconstruction residual and fail retention. It can remain near its initial kernel and fail to learn. It can satisfy a theorem’s sufficient rank and still be unnecessarily expensive or unreachable by the chosen optimizer.

0x0BB Why Rank Adequacy Is A Product Decision

Let candidate have validation target score , retained base score , stress score , and cost . Assume all three quality metrics are higher-is-better. Relative to the frozen base candidate , define target gain

and forgetting

This sign convention matters. Positive means the adapted candidate retained less of the measured base behavior. If a retention metric is lower-is-better, it must first be oriented or normalized; silently mixing directions makes the tradeoff plot meaningless.

A low-rank run can therefore occupy at least four distinct states:

Target gainForgettingInterpretation
highlowstrong candidate under the measured axes
highhighuseful adaptation with a retention cost
lowlowconstrained movement; possibly underfitting
lowhighdominated failure

“Forgets less” is not automatically a success. If does not meet the product floor, low forgetting describes failure to adapt, not an efficient release.

0x0BC Reconstruct The Source Experiment Before Quoting It

Biderman et al. compare LoRA with full fine-tuning for Llama-2-7B across two domains and two training regimes:

AxisSource contract
domainsprogramming and mathematics
regimescontinued pretraining and instruction fine-tuning
continued-pretraining dataStarCoder-Python and OpenWebMath, up to 20B training tokens
instruction dataMagicoder-Evol-Instruct-110K and MetaMathQA, about 100K prompt-response pairs
LoRA ranks16, 64, and 256
scale, so across the rank sweep
dropout’lora_dropout = 0.05’
adapted module familiesquery, key, value, output, gate, up, and down projections
code target metricHumanEval pass@1 under the paper’s generation protocol
mathematics target metricGSM8K pass@1 under the paper’s prompting protocol
retention metricsHellaSwag, WinoGrande, and ARC-Challenge accuracies

This matrix blocks several invalid summaries. The paper did not test every model family, every rank, every adaptation surface, every domain distance, or every serving constraint. Its CPT and IFT conclusions are not interchangeable.

0x0BD The Source Tradeoff Is Empirical, Not An Algebraic Consequence

The paper reports that standard low-rank LoRA often learned less of the target domain than full fine-tuning in the studied settings, while retaining more out-of-domain behavior. Higher rank generally increased target learning and also changed forgetting. The exact tradeoff depended on domain and training regime.

Source-reported Biderman et al. Figure 3 learning and forgetting tradeoff for Llama-2-7B

Source-reported Biderman et al. Figure 3, extracted from the version-2 paper image stream under CC BY 4.0. The repository did not digitize the plotted values or reproduce the training runs.

The four panels are important because there is no single “LoRA frontier.” Code CPT, code IFT, mathematics CPT, and mathematics IFT place the same method names on different surfaces. Some high-rank instruction-tuning runs approach or match the target score of full fine-tuning while retaining more base behavior; some continued-pretraining settings preserve a substantial target gap.

0x0BE Derive The Full-Update Rank Measurement

For one frozen weight and its full-fine-tuned checkpoint , define

If

then the smallest rank explaining fraction of squared Frobenius energy is

The source uses for its layerwise full-update analysis. This is an energy-prefix rank, not algebraic rank, numerical rank, stable rank, configured LoRA rank, or the smallest rank that reaches a task score. Loop 5 derived those policies separately because their values need not agree.

0x0BF Full-Update Rank Varies Across Layer, Module, And Time

Source-reported Biderman et al. Figure 6 full-update 90-percent variance ranks by layer module and checkpoint

Source-reported Biderman et al. Figure 6, extracted from the version-2 paper image stream under CC BY 4.0. The y-axis is the rank needed to explain at least 90% of full-update variance; it is not a recommended LoRA rank.

The source reports three patterns in its code continued-pretraining run:

  1. measured full-update rank grows over training;
  2. MLP updates generally have higher energy ranks than attention updates; and
  3. middle layers often have higher ranks than boundary layers.

The earliest analyzed checkpoint already has 90%-energy ranks far above common LoRA configurations. That observation can explain a capacity gap, but it does not prove that no lower-rank task-sufficient solution exists. The full-update optimizer found one high-rank path. A different parameterization can reach a different update with similar outputs.

0x0BG The Immutable Run Manifest

Before training, freeze a row for every candidate:

candidate_id
base_model_id / tokenizer_id
method / configured rank / target-module surface
alpha / dropout / initialization
optimizer / schedule / precision / clipping
train dataset payload hash / sample order / token budget
seed / world size / gradient accumulation
checkpoint cadence / selection rule
target-validation split and metric revision
retention-validation split and metric revision
stress-validation split and metric revision
held-out test split identities
diagnostic probe identities
trainable-state and peak-memory accounting

Rank without surface is incomplete. Rank 16 on query and value projections is not the same capacity, cost, or function class as rank 16 on all attention and MLP projections. M6.4 owns the variant mechanisms; this loop records their changed objects as candidate metadata.

0x0BH Run And Artifact Identity Must Survive Resume

One logical run produces many artifacts:

run identity
    -> training configuration
    -> optimizer and scheduler state
    -> candidate checkpoints
    -> validation score records
    -> full-update deltas and spectra
    -> subspace / factor / kernel diagnostics
    -> selected release checkpoint
    -> held-out test report

The checkpoint selected on validation must retain the exact optimizer, dataset, seed, and metric lineage that produced it. A filename such as ‘lora_rank_16_final.pt’ is not enough. If a resumed run changes sample order, precision, target surface, or checkpoint-selection code, it is a new candidate identity.

0x0BI Checkpoint Selection Is Nested Inside Rank Selection

Let be the checkpoints for candidate . A predeclared validation rule chooses

Only then may ranks be compared:

Using test performance to choose either or leaks the final evaluation into model selection. “We only looked once” is still leakage if the result changes the chosen rank.

0x0BJ One Candidate Record Joins, But Does Not Collapse, The Evidence

The candidate record is a typed product:

Field familyConsumed resultForbidden inference
reconstructionLoop 5 rank, singular tail, sampled-output residuallow task loss
subspaceLoop 6 row/column angles and directed coverageretention
trajectoryLoop 7 factor norms, gradients, scale, optimizer, dtype stateuseful feature learning
function spaceLoop 8 Jacobian, kernel, and linearization diagnosticsgeneralization
theorem scopeLoop 9 assumptions and sufficient-rank statementspractical optimum
operational scorestarget, retention, stress, cost, uncertaintyuniversal rank

Joining means every field shares one candidate identity. It does not mean the fields are interchangeable.

0x0BK Seed Aggregation And Uncertainty Are Part Of The Metric

For declared seeds and score ,

with sample variance

When seeds or evaluation items are paired, compare paired differences

rather than pretending two independent error bars describe the difference. Publish a confidence or bootstrap interval whose resampling unit matches the actual dependence structure. Three seeds with a narrow observed range are not proof of a narrow population interval.

The exact oracle reports mean, minimum, maximum, and range only. Those are deterministic fixture summaries, not confidence intervals.

0x0BL Forgetting Must Name A Baseline And A Metric Direction

For higher-is-better retention score , the oracle uses

If the base scores 90 and a candidate scores 85, forgetting is 5 points. For a lower-is-better loss , the oriented degradation would instead be

Do not average raw heterogeneous metrics. The Biderman paper’s plotted retention axis averages three accuracies with the same direction. A product suite mixing accuracy, toxicity, latency, and calibration error needs separate units or an explicitly frozen normalization.

0x0BM Reconstruction Is A Gate, Not The Objective

Loop 5’s exact matrix has Frobenius tail squares

at ranks . Under its identity-input probe, mean output residuals are

Loop 10 consumes those values by digest and object identity. It does not recompute them under a new convention. In the fixture, a reconstruction gate requires

Rank 2 passes exactly. That still does not select rank 2: target, retention, stress, budget, and diagnostic gates must also pass.

0x0BN Subspace, Dynamics, And Kernel Checks Are Admissibility Checks

A candidate may be compared in subspace only after rank-revealing orthonormalization and gauge removal. A candidate may be interpreted through a fixed kernel only if the frozen probe, output coordinates, optimizer metric, Jacobian drift, kernel drift, alignment, and output linearization residual are all recorded.

The oracle therefore evaluates

kernel_gate = (
    not candidate.kernel_interpretation_requested
    or candidate.kernel_bundle_complete
)

It contains no universal “small drift” threshold. The threshold, horizon, probe, and estimator belong to the study manifest. A missing kernel bundle invalidates the kernel explanation; it does not automatically invalidate the candidate’s measured target score.

0x0BO Theorem Rank Cannot Enter The Tie-Breaker

Loop 9 produced sufficient-rank statements for specific matrix, FNN, Transformer, and linearized NTK contracts. Those ranks cannot be inserted into the candidate selector because they answer different objectives and may not prove reachability by the actual optimizer.

The fixture requires

theorem_rank_used_as_selector = false

for every candidate. Theorems can motivate sweep boundaries or explain a result after assumptions are checked. They cannot replace measurement.

0x0BP Pareto Dominance Preserves The Tradeoff Geometry

With target, retention, and stress higher-is-better and cost lower-is-better, candidate weakly dominates when

and at least one inequality is strict. The Pareto set is

This operation needs no arbitrary conversion between “one retention point” and “one megabyte.” It removes strictly inferior candidates while preserving the remaining product tradeoffs.

0x0BQ A Constrained Selector Makes Product Requirements Explicit

Let the validation floors be , let the maximum reconstruction residual be , and let mean all required diagnostic and budget checks pass. The feasible set is

The exact fixture then applies a lexicographic rule:

This means: meet quality first, then choose the least costly eligible candidate, then the smaller configured rank, then a deterministic identifier. It does not reward exceeding one quality floor enough to compensate for violating another.

0x0BR Exact Validation Oracle

The local fixture freezes

Its validation means are:

CandidateRankTargetRetentionStressForgettingCostTail Feasible
basen/a5090780030no
LoRA r116288822814no
LoRA r227485895165yes
LoRA r337382888241no
LoRA r4482749016320no
full FTn/a886593251200no

The numbers are pedagogical inputs. Their value is that the decision can be audited exactly:

  1. rank 1 fails target, stress, and reconstruction;
  2. rank 2 passes every gate;
  3. rank 3 has a better matrix residual but fails retention and lacks the requested kernel bundle;
  4. rank 4 and full fine-tuning improve target score but violate retention; and
  5. therefore only rank 2 is feasible under this product contract.

Exact synthetic rank retention and diagnostic decision oracle

0x0BS The Frontier And The Feasible Set Are Different

The exact four-objective frontier is

base
lora_r1
lora_r2
lora_r4
full_ft

‘lora_r3’ is dominated by ‘lora_r2’: it has lower target, retention, and stress means while costing more. The other candidates remain Pareto-relevant because each preserves a different extreme. Yet only ‘lora_r2’ belongs to the feasible set.

This distinction prevents two common errors:

Pareto-optimal
    does not mean deployable

constraint-feasible
    does not mean globally best under another product contract

Changing the retention floor can change the selection without changing any model. That is policy sensitivity, not model instability.

0x0BT Held-Out Test Is A Report, Not Another Selection Round

After selecting ‘lora_r2’, the fixture opens the held-out test report:

CandidateTest targetTest retentionTest stress
base499078
selected LoRA r2738588
full-FT reference876492

The selector does not run again. If the selected candidate fails a predeclared release gate on test, the outcome is no release or a new versioned study, not “pick the runner-up using test.”

0x0BU Executable Selection Trace

manifest = load_immutable_manifest()
assert disjoint(manifest.validation_splits, manifest.test_splits)
assert not test_store.was_opened()

records = []
for candidate in manifest.candidates:
    checkpoints = train_or_load(candidate)
    chosen = select_checkpoint(checkpoints, candidate.validation_rule)

    record = {
        "candidate_id": candidate.id,
        "checkpoint_id": chosen.id,
        "target": evaluate(chosen, manifest.target_validation),
        "retention": evaluate(chosen, manifest.retention_validation),
        "stress": evaluate(chosen, manifest.stress_validation),
        "cost": account_trainable_and_runtime_state(chosen),
        "reconstruction": run_reconstruction_protocol(chosen),
        "subspace": run_subspace_protocol(chosen),
        "dynamics": load_training_trajectory(chosen),
        "kernel": run_kernel_bundle_if_requested(chosen),
    }
    records.append(record)

frontier = pareto_frontier(records, manifest.objective_directions)
feasible = [row for row in records if passes_every_gate(row, manifest)]
if not feasible:
    # No candidate passes every gate: fail closed with no release.
    # Nothing is frozen and the held-out test store stays closed.
    record_no_release(manifest.digest)
    raise SystemExit("no release: the feasible set is empty")
selected = min(feasible, key=lambda row: (
    row["cost"],
    configured_rank_or_infinity(row),
    row["candidate_id"],
))

freeze(selected["candidate_id"], selected["checkpoint_id"], manifest.digest)
assert not test_store.was_opened()
test_report = evaluate_frozen_release(selected, test_store.open_once())

Production code should fail closed on missing metrics, mixed revisions, NaNs, unknown directions, duplicate candidate IDs, or a test-store access event.

0x0BV Artifact And Runtime Integration

The release candidate needs more than adapter tensors:

selection manifest digest
base model and tokenizer identity
adapter checkpoint and target-module map
optimizer/checkpoint lineage
validation score records with raw per-seed outputs
retention and stress suite revisions
reconstruction/subspace/kernel diagnostic artifacts
trainable-state, peak-memory, and wall-time ledgers
selected candidate and tie-break trace
held-out test access record
rollback candidate identity

M6.5 owns multi-adapter serving and M6.9 owns routed composition. Loop 10 only requires that any runtime state used as a cost or release gate be measured under a pinned deployment contract rather than inferred from rank alone.

0x0BW Alternative Decision Designs

DesignUseful whenMain risk
hard constraints then minimum costproduct floors are real requirementsfeasibility can be sensitive near thresholds
Pareto frontier plus human choicetradeoffs cannot be scalarized honestlydecision may be hard to automate
weighted utilityunits and business weights are stablehidden weights can manufacture a winner
knee-point selectionsmooth frontier has a meaningful curvaturescaling and normalization change the knee
confidence-bound selectionuncertainty is materialinterval and dependence assumptions must be valid
sequential racinglarge candidate grid is expensiveearly noisy metrics can eliminate the best run

This article uses hard constraints because every pass/fail condition is visible. It refuses an undeclared scalar score such as

because the units and weights have no natural equality.

0x0BX Paper-By-Contract Comparison

EvidenceObjectWhat it supportsWhat remains unproved
LoRAlearned low-rank perturbations on selected matriceslow-rank adaptation can be competitive in tested tasksuniversal adequate rank
Biderman et al.Llama-2-7B LoRA/full-FT learning and forgetting experimentssource-scoped target/retention tradeoffs and full-update spectrathat high full-update rank is necessary for task success
Loop 5 / Eckart—Youngone declared matrix and normbest post-hoc rank- approximationLoRA optimizer convergence or task quality
Loop 6update row/column spacesgauge-invariant subspace comparisonretention or compatibility
Loop 7factor-coordinate dynamicsexact local trajectory and conditioning factsgeneral AdamW behavior without its state
Loop 8 / kernel sourcesfinite-data Jacobian and kernel objectsconditional fixed-kernel interpretationuseful feature learning or generalization
Loop 9 theorem sourcessource-specific existence and landscape statementssufficient ranks under quantified assumptionspractical candidate selection
Loop 10 exact fixturedeclared validation measurements and policydeterministic selector and failure rejectionany paper benchmark or universal rank

0x0BY Rank And Retention Failure Lab

FailureHidden collapseConsequence
choose rank from alonefull-update reconstruction vs task solutionexcessive or insufficient adapter
praise low forgetting without target floorretention vs underfittingproduct learns too little
select best test scoreevaluation vs model selectionoptimistic final estimate
compare ranks with different surfacesrank vs trainable function classcapacity and cost are confounded
pick best checkpoint independently on testcheckpoint vs rank nestingdouble selection leakage
average metrics with mixed directionsscore orientation omittedreversed Pareto relation
use one aggregate without unitstradeoff vs arbitrary scalarizationinvisible product weights
call overlap retentionupdate geometry vs behaviorfalse compatibility claim
call kernel alignment qualitymechanism vs utilitystable but poor model accepted
use theorem rank as tie-breakersufficient existence vs measurementassumptions replace evidence
omit failed or missing diagnosticsunknown vs passincomplete candidate enters release
rerun selection after test failuretest report vs new studyheld-out set becomes validation
ignore seed or item dependencevariation vs independent evidenceconfidence is overstated
promote one fixture ranklocal oracle vs empirical lawrank 2 becomes a false recipe

0x0BZ Loop 10 Handoff

The fixture proves the selector, not the model.

Loop 10 closes the rank-selection algebra:

  1. five predecessor reports are consumed by immutable digest rather than reinterpreted;
  2. target learning and retention use explicit baselines and directions;
  3. checkpoint selection is nested inside candidate selection;
  4. Pareto and constraint feasibility remain different objects;
  5. test data cannot alter the selected rank;
  6. the exact fixture rejects every one-field contract mutation; and
  7. source figures remain empirical evidence rather than local reproduction.

Loop 11 may now expand the failure lab, complete source and visual provenance, add responsive variants, and turn the experimental protocol into release-facing checklists. It must not reopen test data as a selector or convert the exact fixture’s rank 2 into advice.

0x0C Failure Closure, Complete Evidence, And Experimental Design

Loop 10 proved that a frozen policy can join heterogeneous diagnostics without turning any one diagnostic into the objective. It did not establish that a real rank comparison has been designed correctly. A candidate table can be algebraically valid while its runs differ in data order, initialization, checkpoint opportunity, target modules, failed-run handling, or test exposure. Those differences can dominate the rank coordinate that the table claims to study.

Loop 11 therefore closes two different surfaces:

  1. every mechanism failure from Loops 2—10 receives a typed detector, consequence, and recovery owner; and
  2. a future empirical rank study receives an immutable design whose units, treatments, blocks, nuisance variables, estimands, stopping rules, and release decisions are fixed before outcomes are inspected.

The local fixture remains synthetic. It validates the design transaction; it does not execute the proposed training runs or supply evidence that one rank is best.

0x0CA Owner Contract: Close Evidence Without Inventing A Rank Benchmark

M6.7 owns the relation between a low-rank claim and the evidence needed to test it. In this loop that includes:

typed failure identity and bounded recovery
experiment unit, treatment, block, nuisance coordinate, and estimand
paired candidate comparison and incomplete-pair policy
seed, data-order, split, checkpoint, and evaluator provenance
validation-only selection and held-out-test isolation
static source, local-link, figure, visual, and negative-test closure

It still does not own adapter runtime residency, learned adapter routing, generic deployment packaging, or general scaling-law extrapolation. Those remain M6.5, M6.9, M8, and M4.7—M4.9 respectively. A failure record can hand an issue to those owners; it cannot absorb their mechanisms into this article.

0x0CB A Failure Record Needs Seven Coordinates

A prose warning such as “rank may be too small” cannot be tested or recovered. The machine-readable failure manifest gives each failure seven coordinates:

failure id and alarm family:
    stable identity plus the class of state or claim that became unsafe

origin loop and invariant:
    the first mechanism contract that must remain true

perturbation:
    one concrete drift that can violate the invariant

detector:
    an equality, digest, rank check, directional derivative, split audit,
    completeness test, or bounded discrepancy

consequence:
    the first derived result that can no longer be trusted

recovery owner:
    the only article, experiment stage, or release gate allowed to repair it

evidence limit:
    what a successful detector still does not prove

The final coordinate prevents a common escalation error. Exact finite-matrix parity proves an algebraic identity, not language-model quality. A complete source manifest proves provenance, not live network availability. A green static SVG audit proves structure, not mobile legibility.

M6.7 failures move from a typed low-rank invariant through a coordinate-specific detector to a bounded recovery owner and evidence limit

0x0CC Six Alarm Families Must Remain Distinct

The closure manifest has four failures for each mechanism loop from Loop 2 through Loop 10. Its thirty-six records belong to six alarm families:

Alarm familyRepresentative invariantDetectorTypical recovery
identity and protocolbase, tensor, split, rank policy, and protocol IDs denote the same study objectsmanifest digest, axis, split, and object-join auditreject the run or rebuild the manifest before execution
geometry and reconstructionrank, tangent, SVD, covariance support, and subspace metrics use their declared objects and thresholdsexact rank/projector/residual oraclerecompute the diagnostic; never relabel it
optimization and numericsfactor gauge, initialization, scaling, optimizer metric, and dtype path match the derived dynamicsgradient, product-velocity, range, and resume checksrestore factors/optimizer state or narrow the claim
function space and theoremJacobian, kernel, linearization horizon, theorem assumptions, and practical decision remain separatecurrent-versus-frozen trajectory and assumption ledgerinvalidate the explanation, not the observed score
experimental design and statisticscandidate cells are paired, complete, validation-only, and direction-awaredesign-cell, checkpoint, estimand, and test-access auditno selection; version a new study if policy changes
evidence, publication, and releasesources, figures, URLs, artifacts, and evidence classes are complete and correctly scopedprovenance, digest, route, and claim-firewall auditrepair metadata or block publication/release

No alarm substitutes for another. A passed SVD residual cannot repair a split leak. A paired score interval cannot establish a tangent-space theorem. A source-reported paper figure cannot validate the local selection oracle.

0x0CD Same Shape, Same Mean, And Same Seed Count Are Not Same Evidence

Several dangerous substitutions preserve the headline dimensions:

Superficially equal objectHidden mismatchRequired check
two deltasdifferent base checkpoint or tensor orientationbase/tensor identity plus executable output trace
two rank- productsdifferent row/column spaces or numerical rankspectrum and separate row/column projectors
two candidate meansdifferent seed tuples, missing runs, or checkpoint opportunitypaired-cell completeness and attempt lineage
two four-seed studiesone varies initialization, the other data orderexplicit nuisance-coordinate manifest
two retention scoresdifferent base metric or higher/lower-is-better conventionbaseline and metric-direction record
two validation tablesone chose hyperparameters after viewing testaccess log and frozen-candidate transaction
two successful rerunsone silently dropped an earlier failed attemptimmutable run ID with every attempt and termination reason

Even output equality at one probe is insufficient. Gauge-equivalent factors can compute the same product and take different optimizer steps. Two kernels can have high normalized alignment and different scale. A base model and an untrained zero-product LoRA branch can emit the same tensor while owning different gradients and artifact state.

0x0CE Define Unit, Treatment, Block, Nuisance, And Estimand First

The word “run” is too vague for an experimental record. One training unit is:

where is the candidate pipeline, is a frozen experimental block, is a nuisance tuple, and is a predeclared checkpoint step. The block includes domain, training regime, data budget, target-module surface, tokenizer/data revisions, base checkpoint, and evaluator revision.

The candidate is not “rank” unless every other treatment coordinate is fixed. If rank 16 also uses another target-module set, scale rule, optimizer schedule, or quantized base, the treatment is the whole pipeline:

with target set , branch scale , optimizer , initialization , and base representation . Calling the resulting contrast a pure rank effect would be wrong.

For one outcome , a bookkeeping model can expose the design coordinates:

This equation is an index decomposition, not an assertion that the effects are additive or Gaussian. Interactions remain in . Its purpose is to stop a nuisance change from being silently attributed to .

0x0CF Pair Candidates Across Nuisance Coordinates

When two candidate pipelines can share a nuisance tuple, the primary contrast should preserve that pairing:

The paired contrast removes variation common to the same block and nuisance tuple. It does not remove interactions between candidate and seed. If one side is missing, that pair is incomplete; substituting another seed breaks the pairing. A missing-cell policy must be frozen before outcomes are visible.

The base checkpoint is a deterministic baseline record rather than a fake training replicate. Full fine-tuning and LoRA can share data order, dropout, and optimizer RNG identities even though their trainable state differs. Any coordinate that cannot be meaningfully paired is named and analyzed as an unpaired source of variation.

Fine-tuning variance is not hypothetical. Dodge et al. varied weight initialization and data order across 2,100 BERT fine-tuning trials and reported that both contributed materially to outcome variation. Reimers and Gurevych showed in sequence tagging that one selected random seed could change the apparent method ranking and argued for score distributions rather than one score. These are source-reported results on their tasks, not variance estimates for this proposed study.

0x0CG A Seed Range Is Not A Confidence Interval

There are at least three sampling levels:

training-run level:
    initialization, data order, dropout, kernels, and optimizer trajectory

evaluation-item level:
    prompts, examples, tasks, users, domains, or generated samples

study-design level:
    split construction, data budget, hyperparameter search, checkpoint grid,
    candidate family, and evaluator revision

For paired candidate differences , the run-level sample variance is:

It estimates dispersion over the declared nuisance-tuple population only when those tuples were sampled under the stated design. The minimum and maximum of four seeds are descriptive endpoints, not a confidence interval. Treating thousands of test items from one trained checkpoint as thousands of independent training runs is pseudoreplication.

If a metric has valid item-level contributions, an item bootstrap should keep candidate predictions paired on the same resampled items. To combine item and run variation, a hierarchical procedure first resamples nuisance tuples and then paired items within the chosen tuple. Metrics such as pass@, correlated task suites, or judge-based scores need estimator-specific resampling; the article does not prescribe one universal bootstrap.

Bouthillier et al. model benchmarking as a pipeline with variation from data sampling, initialization, and hyperparameter choice. Their result supports exposing multiple variation sources; it does not prove that the additive bookkeeping equation above is a correct stochastic model for LoRA ranks.

0x0CH Selection Creates Multiplicity And Optimism

Rank, checkpoint, target modules, scale, and optimizer settings form a search family. Reporting the best validation value as if it were one prespecified measurement ignores selection. The immutable protocol therefore records:

  1. the candidate and checkpoint family before training;
  2. the metric directions and product gates before selection;
  3. the tuning budget allocated to every candidate;
  4. the selection rule, tie-breaker, and missing-run policy;
  5. the single frozen candidate identity before test access.

Comparing many ranks may require simultaneous intervals, a family-wise error procedure, false-discovery control, or an explicitly descriptive decision analysis. The correct method depends on the hypothesis, paired structure, metric distribution, and number of comparisons. Dror et al. make the same general point for NLP significance testing: test choice depends on the experimental setup and evaluation measure. A star beside one metric is not a universal evidence contract.

Test failure does not authorize selecting the validation runner-up. The valid outcomes remain release or no release. Changing the candidate family, gates, test interpretation, or retry policy creates a new versioned study with new held-out data.

0x0CI Early Stopping, Missing Runs, And Retries Need Attempt Lineage

Early stopping can save compute, but it is part of the candidate pipeline. The monitor, direction, patience, minimum delta, checkpoint cadence, warmup, and maximum step must be predeclared and validation-only. A rule cannot inspect a test metric, and failed candidates cannot be removed merely because they lower the mean.

Every training unit owns one immutable run_id and one or more attempt IDs:

run_id:
    candidate + block + nuisance tuple

attempt_id:
    run_id + retry ordinal + environment digest

termination class:
    completed, validation-stopped, numerical failure,
    infrastructure failure, admission failure, or operator cancellation

retry rule:
    infrastructure-only under the same semantic run identity;
    preserve the failed attempt and never choose the better retry by score

A numerical divergence is an outcome of the pipeline, not an infrastructure retry. An interrupted run may resume only from an exact state bundle whose optimizer, scheduler, scaler, RNG, sampler, counters, and data position restore before the next stochastic event.

0x0CJ Immutable Experimental-Design Manifest

Before the first outcome is observed, freeze:

question, primary estimands, secondary diagnostics, and non-claims
base checkpoint, tokenizer, data, split, contamination, and evaluator revisions
candidate family and every rank, target, scale, initialization, and optimizer coordinate
block definitions and which conclusions may pool across blocks
nuisance-tuple generation and pairing policy
training, checkpoint, early-stop, retry, and missing-cell policies
metric implementations, directions, aggregation levels, and uncertainty procedures
Pareto objectives, product gates, tie-breakers, and tuning budgets
test-access authority, audit log, frozen-candidate transaction, and no-release rule
artifact schemas, environment, code, dependency, kernel, and hardware identities
planned tables, figures, exclusions, deviations, and evidence-class labels

Pineau et al. describe code submission, reproducibility challenges, and a machine-learning reproducibility checklist as complementary mechanisms. The manifest above is this article’s synthesis for a rank-retention study. It is not claimed to be the NeurIPS checklist or a guarantee that another environment will reproduce every floating-point value.

0x0CK Exact Teaching Design And Publication Oracle

The exact fixture expands five trainable candidate pipelines across two blocks and four paired nuisance tuples:

Three predeclared checkpoints per unit create:

Two separate base-baseline records are block-specific and are not counted as training units. The candidate set, nuisance tuples, checkpoint steps, metric directions, missing-run policy, and test fence are generated without outcomes. The fixture also consumes the Loop 10 report and freezes its synthetic selected candidate only to test transaction identity.

M6.7 experimental design crosses candidate pipelines with blocks and paired nuisance tuples before validation selection freezes one candidate and opens held-out test reporting

The exact oracle checks cross-product completeness, pairing, checkpoint grids, split disjointness, attempt policy, source coverage, local links, A22 figure disposition, visual provenance, SVG accessibility structure, failure records, and all prior one-field-invalid families. It executes no training and computes no empirical rank effect.

0x0CL Execution Trace: Freeze, Run, Select, Then Test

design = load_and_validate_immutable_design()
assert design.test_access == "closed"

for block in design.blocks:
    evaluate_base_once(block)
    for nuisance in design.paired_nuisance_tuples:
        for candidate in design.trainable_candidates:
            run_id = derive_run_id(candidate, block, nuisance)
            attempt = execute_or_exactly_resume(run_id, design)
            record_every_attempt(attempt)
            if attempt.is_semantically_complete:
                evaluate_predeclared_validation_checkpoints(attempt)

assert complete_or_apply_predeclared_missing_cell_policy(design)
candidate_records = aggregate_validation_only(design)
selected = apply_frozen_pareto_constraints_and_tie_break(candidate_records)
freeze_candidate_and_artifact_identity(selected)

open_test_once(selected)
report_test_without_reselection(selected)
archive_design_runs_attempts_artifacts_and_deviations()

The order is the contract. Opening test before freeze_candidate invalidates the study. Aggregating before attempt classification can hide divergence. Dropping an incomplete pair after seeing its direction changes the estimand.

0x0CM Reproducibility Is A Chain, Not A Seed Field

A replayable claim joins:

study manifest
  -> run-cell manifest
  -> immutable attempt log
  -> exact-resume checkpoints
  -> prediction and diagnostic artifacts
  -> validation aggregation
  -> frozen decision report
  -> one held-out-test report
  -> release or no-release record

The chain carries content hashes and parent identities. A checkpoint without its base, factors, optimizer, RNG, data cursor, and code/environment revision is not an exact-resume artifact. Predictions without evaluator and dataset IDs are not reusable metric evidence. A figure without a source or fixture is not a reproducible claim.

Loop 11 closes the current static surface exactly:

32 source records
    3 digest-pinned local inputs
    29 version-pinned external primary sources

29 external URLs published in the article
7 normalized local article routes
53 A22 figure dispositions in source order
30 rendered visual elements and 32 desktop/mobile asset routes
36 typed failures across Loops 2-10
9 prior invalid-fixture families with 1,472 one-field mutations
24 new one-field design/publication mutations

Every external URL has one source record and every source record appears in the article. Every image route resolves and has cumulative provenance. Every SVG exposes role="img", a viewBox, <title>, and <desc>. These checks prove static identity and accessibility structure. They do not prove live URL availability, completed MathJax layout, theme contrast, mobile legibility, or absence of browser-console errors. Loop 12 owns normalized whole-article browser and final publication acceptance.

0x0CO Release-Facing Checklist

StageRequired evidenceFail-closed outcome
design admissionimmutable sources, blocks, candidates, nuisance tuples, estimands, budgets, stopping and retry rulesdo not start training
run admissionsemantic run ID, environment, artifact parents, exact target and optimizer statereject the attempt
validation closecomplete cells or predeclared missingness action, checkpoint lineage, all metric directionsno candidate selection
decision closePareto set, product gates, deterministic tie-break, frozen artifact identityno test access
test closeone candidate, one access transaction, uncertainty and deviations reported without reselectionrelease or no release
archive closemanifests, code/environment, attempts, checkpoints, predictions, reports, figures, and provenanceclaim remains non-replayable

0x0CP Experimental-Design Sources By Contract

SourceWhat it contributes hereWhat it does not establish
Reimers and Gurevych (EMNLP 2017)source-reported seed sensitivity and motivation to report distributionsLoRA-specific variance or a universal number of seeds
Dodge et al. (2020)source-reported separation of weight-initialization and data-order variation in BERT fine-tuningthe variance components of this rank-retention design
Bouthillier et al. (MLSys 2021)whole-pipeline sources of benchmark variation and comparison-design motivationvalidity of one additive random-effects model here
Dror et al. (ACL 2018)test selection depends on hypothesis, setup, and evaluation metricone mandatory test for every generative or retention metric
Pineau et al. (JMLR 2021)reproducibility mechanisms and checklist lineagebitwise cross-platform reproducibility or empirical replication
Loop 11 exact fixturecross-product, pairing, transaction, source, visual, and failure closureany trained model, empirical effect, paper reproduction, or release quality

0x0CQ Loop 11 Handoff

Loop 11 freezes the typed failure surface, experimental-design transaction, source and link closure, A22 disposition, cumulative visual provenance, responsive source structure, and negative-test inventory. Loop 12 may now audit final formulas, sources, browser rendering, accessibility, and cross-article boundaries. It must not modify the frozen candidate family after outcomes, reinterpret a seed range as a confidence interval, or claim that a static SVG check proves responsive legibility.

Loop 12 closes that handoff against the unchanged mechanism and experiment contracts. Its normalized browser profiles must render every MathJax source, select the intended desktop or mobile asset in each responsive pair, resolve every body image and local article route, preserve heading and anchor identity, and report no article-local horizontal overflow. Completed upstream owners are digest-pinned; unfinished M6.5 and M6.9 owners remain route-checked and duplication-checked without pretending that their current prose is immutable.

0x0D Alternatives And Design Choices

ChoiceWhat it restrictsAdvantageFailure mode
global random subspacefull parameter vector to coordinatesmeasures objective compressibilityprojection-dependent and expensive to measure
vanilla LoRAeach selected matrix to rank structured, mergeable, efficientlocal rank may miss required directions
fixed random down factortrain output factor onlylower parameter and activation staterandom features can be insufficient
spectral initializationinitial factor subspacesaligns trainable directions with chosen spectrumchosen spectrum may not match downstream need
adaptive rank allocationper-layer rank budgetspends parameters where evidence suggestsimportance estimator and pruning schedule add state
repeated merge/reinitializeaccumulated update rankcan expand beyond one stage ranknew stages can relearn old directions
full fine-tuningno local low-rank constraintmaximum adaptation freedommemory, storage, and forgetting cost

The correct choice follows from the target/retention objective and measured bottleneck, not from the phrase “low intrinsic rank.”

0x0E Failure Lab

FailureConflated conceptSymptom
called the LoRA rankglobal subspace dimension vs matrix rankunsupported rank recommendation
configured called effective rankupper bound vs learned spectrumhidden rank collapse
factor parameter count called manifold dimensiongauge redundancy ignoredovercounted degrees of freedom
LoRA treated as a fixed linear subspacebilinear tangent geometry ignoredwrong optimization explanation
truncated SVD used as proof LoRA training will convergeapproximation vs optimizationunexplained performance gap
weight Frobenius error used as task qualityinput covariance omittedlow matrix error but high output error
decomposed for the sampled-output objectivecovariance vs covariance square rootwrong direction weighting and no derivation from the declared loss
singular covariance treated as a unique global reconstructionobserved support vs covariance nullspacezero calibration error hides unconstrained off-support behavior
singular-value mass called squared energy vs irreproducible rank threshold
numerical rank reported without scale, tolerance, or comparisonalgebraic vs thresholded rankbackend- or dtype-dependent rank drift
randomized SVD reported as an exact spectrumapproximation vs exact decompositionmissing seed, residual, convergence, and oversampling evidence
and both zero initializedbilinear gradient path ignoredno learning
reversed zero initialization treated as identicalfirst-step asymmetry ignoredunstable or slower training
same treated as the same optimizer stateproduct gauge vs factor coordinates conflatedidentical forward pass but different next product step
continuous balancedness invariant applied to AdamWgradient flow vs finite adaptive optimization conflatedunexplained invariant drift
factor decay called product decaygauge-dependent factor penalty ignoredexact refactorization changes regularization
width asymptotic substituted for rank asymptotic vs conflatedunsupported scale or learning-rate rule
rank scale changed without initialization variance changed while is hiddenhigh-rank gradient shrinkage or growth
exact factor gauge assumed dtype-safeproduct equality vs coordinate range conflatedoverflow, underflow, or zeroed factor
raw factors compared across runsgauge invariance ignoredfalse subspace difference
only min-rank overlap reported for unequal rankscontainment vs equality ignoreda larger space’s unmatched directions disappear
row-space overlap used as column-space overlapinput features vs output directions conflatedone side appears stable while the other changed
unaligned orthonormal bases compared entrywisebasis coordinates vs subspace conflatedrotated coordinates look different despite identical projectors
stage count used as accumulated ranksubadditivity treated as equalityshared spans or cancellation hide rank stagnation
static adapter sum used for a dynamic gatefixed matrix vs input-dependent operator conflatedmerged release cannot reproduce routed outputs
and scaling treated as cosmeticrank-dependent variance ignoredhigh-rank gradient collapse
NTK result generalized to every fine-tuning runfixed-feature assumptions omittedtheory contradicts observed feature learning
current-kernel flow called frozen-kernel training vs omittedexact chain rule is mistaken for a trajectory approximation
initial kernel equality called path equalityinitialization vs later factors omittednewly active factor features are invisible
first exact tangent step used as long-horizon evidencezero initial factor gradient vs future movement omittedfinite bilinear curvature appears on the next step
deterministic narrow factor called a JL projectionfinite-set probability and width omitteddataset gradient directions are deleted
used as an AdamW kernelplain-SGD metric vs adaptive history omittedpredicted function update has the wrong direction
high kernel alignment called equal kernelsangular similarity vs magnitude omittedrates and convergence times differ
Jacobian drift called useful feature learningmotion vs task utility omittedtarget or retention quality can degrade
dense kernel materialized without axes or estimator stateoutput ordering, probe split, and metric omittedirreproducible or infeasible diagnostic
sufficient universal rank used as practical minimumtheorem objective misunderstoodexcessive adapter cost
low target learning praised as retentionproduct objective omittedunderfit deployment
one task/seed rank sweep generalizedsource scope omittedrank fails on distant domains

0x0F Claim Status And Evidence

ClaimStatusQualification
pretrained language-model fine-tuning can succeed in low-dimensional random subspacesexternally verifiedAghajanyan et al.; result depends on model, task, protocol, and threshold
is the rank required by LoRAfalsedifferent object and parameterization
has rank at most mathematical factexact over the stated shapes
generic rank- matrices have dimension mathematical factexcludes lower-rank singular points
the fixed-rank tangent projector is externally verified and exactly checkedapplies at an exact-rank point with the stated row/column projectors
the factor redundancy is the full differential kernel everywherefalse if generalizedexact at full-rank factors; lower-rank strata can have larger kernel and smaller Jacobian image
truncated SVD gives the best rank-at-most- Frobenius approximationexternally verified theorem and exact local derivationuniqueness at an interior truncation requires ; it does not characterize LoRA optimization
output-weighted rank- reconstruction is obtained by truncating mathematical fact under the derived sampled linear-layer objectiveinvertible covariance maps back with ; singular covariance identifies only observed support
configured, algebraic, numerical, stable, energy, and entropy ranks are interchangeablefalseeach policy has a distinct definition, threshold, and operational question
CorDA’s context-oriented decomposition is the sampled-output optimum derived herefalseCorDA decomposes a different object for a method-specific adapter construction
low ranks were competitive in original LoRA experimentsexternally verified, source-reportedspecific tasks, matrices, model, and training setup
singular values of are principal cosinesexternally verified definition and exact local checkbases must be rank-revealed and orthonormal; the result compares spans, not task quality
min-rank-normalized projection overlap proves two unequal-rank spaces are equalfalsescore one proves only that the smaller space is contained in the larger
orthogonal Procrustes makes raw LoRA factors identifiablefalseit aligns already-orthonormal basis coordinates, not arbitrary factor gauges
adding rank- adapters yields rank false if generalized is an upper bound; shared row/column spans and cancellation can reduce the sum
every input-dependent adapter mixture can be merged into one matrixfalsethe exact quadratic gate counterexample violates linear homogeneity
LoRA can preserve a full-fine-tuning kernel under suitable random-projection and kernel-regime assumptionsexternally verifiedMalladi et al.; conditional, not universal
plain parameter gradient flow moves outputs through the current empirical kernel mathematical chain-rule fact and externally verified lineagecurrent-kernel flow is not the same claim as freezing at
a fixed-kernel model requires both output linearization and sufficiently fixed gradient featuresexternally verified and locally derivedboth properties are protocol-, output-, optimizer-, and horizon-dependent
the linear-layer LoRA kernel is the sum of and mathematical fact and exact local checkuses the declared factor orientation, output stacking, and plain-SGD metric
equality between and guarantees equal later trajectoriesfalsethe exact fixture begins with equality and has nonzero Jacobian and kernel drift after one step
a sufficiently wide normalized random LoRA projection can preserve finite training-set kernel entriesexternally verified theorem contracthigh-probability finite-set claim under Malladi et al.’s assumptions, not every deterministic factor or later checkpoint
is the kernel analog for every optimizerfalsefixed preconditioners give ; adaptive history requires an optimizer-specific contract
Jacobian drift, kernel drift, and output linearization residual are interchangeablefalseeach diagnoses a different approximation boundary
Jacobian or kernel drift proves useful feature learningfalse if generalizedmovement must be connected to target and retention outcomes under a controlled experiment
LoRA has universal Transformer adaptation power at very small practical ranksnot supportedexpressive-power sufficient ranks can be much larger
standard -random/-zero and reversed initialization have different dynamicsexternally verified and directly derivedperformance conclusion remains source-scoped
factor gradient flow induces left- and right-preconditioned motion in mathematical fact and exact local checkstated for the frozen product-only gradient-flow contract
simultaneous finite factor SGD equals one Euler step in product spacefalseit also contains the exact cross term
is conserved by every LoRA optimizerfalse if generalizedexactly conserved only by the stated continuous factor-gradient flow; practical optimizer extensions require separate proof
gauge-equivalent factors have the same equal-learning-rate trajectoryfalsethe exact probe preserves and changes product velocity
factor-specific learning rates can locally compensate a scalar gauge under plain flowmathematical fact and exact local checkthe compensation is not an AdamW, clipping, decay, or dtype equivalence
is rank-stable independent of initializationfalse if generalizedthe derived exponent is ; the variance exponent must be fixed
the initialization-dynamics and rsLoRA papers prove the same asymptotic statementfalsethe former varies width with rank fixed; the latter studies rank scaling under its own assumptions
factor L2 or decoupled decay is product regularizationfalsethe factor penalty changes under an exact product-preserving gauge
LoRA always matches full fine-tuning while forgetting lessfalse if generalizedBiderman et al. report target gaps and retention tradeoffs in studied regimes
Biderman et al. define one universal LoRA learning-forgetting frontierfalsedomain, continued-pretraining versus instruction-tuning regime, rank, data, metric, and checkpoint all change the reported surface
full-update 90%-energy rank is the required LoRA rankfalseit measures one optimizer’s dense checkpoint delta under one spectral policy, not the minimum task-sufficient adapter
the exact Loop 10 fixture recommends rank 2falserank 2 is uniquely feasible only under the fixture’s synthetic scores and declared validation gates
a Pareto-optimal candidate is automatically deployablefalsePareto membership removes strict domination but does not enforce product floors
held-out test can choose the runner-up after a failed releasefalsethat reuses test as validation; the outcome is no release or a new versioned study
one random seed is enough to compare non-deterministic fine-tuning pipelinesnot supportedseed, data order, dropout, and pipeline-search variation require a declared repeated-run design
the range across four seeds is a confidence intervalfalseit is a descriptive range unless a valid sampling and interval procedure is declared
pairing candidates on nuisance tuples removes all training variationfalsepairing removes shared variation but candidate-by-seed interactions and unpaired coordinates remain
one significance test is valid for every NLP metric and study designfalsethe hypothesis, metric, dependence, pairing, and comparison family determine the test contract
early stopping is only a compute optimizationfalsemonitor, cadence, patience, and checkpoint opportunity change the candidate pipeline
the exact Loop 11 design fixture reproduces an empirical rank studyfalseit checks cells, identities, provenance, and transaction order without training a model

0x10 Handoffs

  • How should one train, initialize, scale, or quantize one adapter? See M6.3 and M6.4.
  • How are many adapters resident and batched at inference? See M6.5.
  • How are adapters routed, shared, composed, and retained across tasks? See M6.9.
  • How should a general scaling law be fitted and extrapolated? See M4.7.
  • How does low-bit training change adaptation state? See M8.7.

0x11 Publish Gate

CheckStatus
Ambient dimension, objective intrinsic dimension, matrix rank, LoRA rank, and feature dimension are separatepass
Direct and structure-aware intrinsic-dimension protocols are derivedpass
is presented as protocol-dependent evidence, not a universal constantpass
LoRA row space, column space, rank bound, and tensor path are explicitpass
Exact-rank manifold, rank-at-most variety, and factor-coordinate space are separatepass
is independently derived from Grassmann charts, the quotient, and differential rankpass
Factor-map differential, adjoint, gauge kernel, tangent/normal spaces, and orthogonal projector are explicitpass
Lower-rank initialization is not assigned the generic exact-rank tangent dimensionpass
LoRA is not mislabeled as one fixed linear subspacepass
Compact-SVD shapes, Frobenius and spectral lower bounds, residuals, uniqueness, and factor reconstruction are derivedpass
Sampled-output error is derived through trace and covariance-square-root formspass
Full-rank whitening, singular-support pseudoinverse, and covariance-nullspace non-identifiability are explicitpass
Exact weight-space and output-weighted rank-one candidates disagree in a checked sensitivity probepass
Configured, algebraic, numerical, stable, energy, and both entropy-rank conventions remain separatepass
SVD backend, tolerance, tie, dtype, and randomized-approximation state are implementation requirementspass
Reconstruction, expansion, and composition are separate operationspass
Original LoRA subspace evidence is source-scopedpass
Raw factors, orthonormal bases, update projectors, and aligned bases remain distinctpass
Principal-angle, projection-overlap, chordal, projector, and directed-coverage identities are derivedpass
Row-space and column-space similarity are computed and interpreted separatelypass
Unequal-rank containment and the Haar random-subspace baseline are explicitpass
Static factor concatenation, exact rank outcomes, cancellation, and dynamic non-mergeability are checkedpass
Factor gradients are derived from the product differential and reconciled in exact tensorspass
Continuous product velocity, simultaneous finite-step cross term, and weighted Gram invariant are derivedpass
Four zero-product mechanisms are separated, including nonzero-factor cancellationpass
Scalar gauge, local rate compensation, Adam counterexample, factor decay, and binary16 range are checkedpass
Rank scaling is derived jointly with initialization variance and kept separate from width asymptoticspass
Factor alternatives, checkpoint/resume state, diagnostics, and failure recovery are explicitpass
Current-kernel function-space flow and frozen-kernel training are algebraically separatepass
Restricted-coordinate kernels distinguish orthogonal projectors from general coordinate metricspass
LoRA factor Jacobians, Kronecker shapes, and the exact initialization kernel are derivedpass
The exact two-step fixture separates kernel drift, current-tangent error, and finite bilinear curvaturepass
Rank-one projection failure and finite-set random-projection preservation are not conflatedpass
Plain-SGD, fixed-preconditioner, asymmetric SignGD, and general AdamW contracts remain distinctpass
Linearization residual, Jacobian drift, kernel drift, and kernel alignment have separate definitionspass
Production-scale diagnostics use declared JVP/VJP estimators rather than requiring dense kernelspass
Source-reported linearization evidence is licensed, attributed, and not presented as local reproductionpass
NTK/subspace kernel preservation is derived and assumption-scopedpass
Expressive-power and NTK optimization theorems are not converted into universal rank recipespass
Full fine-tuning and LoRA learning/forgetting tradeoffs are explicitpass
Rank adequacy protocol includes spectra, outputs, end-to-end quality, overlap, and dynamicspass
The Biderman source experiment is reconstructed by model, domain, regime, rank, scale, surface, data, and metricpass
Full-update energy-prefix rank is derived and kept separate from task-sufficient and configured rankpass
Target gain and forgetting have explicit baselines and metric directionspass
Candidate checkpoint selection is nested inside validation-only rank selectionpass
Reconstruction, subspace, trajectory, kernel, theorem, operational quality, and cost fields remain typed rather than interchangeablepass
Seed summaries are not mislabeled as confidence intervalspass
Pareto dominance, constraint feasibility, and lexicographic tie-breaking are separately derivedpass
The exact candidate oracle consumes Loops 5-9 by immutable digest and selects only from validationpass
Held-out test is opened only after candidate identity is frozen and cannot trigger runner-up selectionpass
Source figures are licensed, attributed, and explicitly not digitized or reproducedpass
Thirty-six typed failures cover every mechanism loop from Loop 2 through Loop 10pass
Experiment units, candidate pipelines, blocks, nuisance tuples, checkpoints, and estimands are distinctpass
Candidate comparisons preserve declared nuisance pairing and incomplete-pair policypass
Run-level and item-level uncertainty are not collapsed into one sample countpass
Early stopping, retries, missing runs, and exact resume have immutable attempt lineagepass
Candidate multiplicity and checkpoint selection remain validation-onlypass
Test failure yields release or no release rather than runner-up selectionpass
All sources, external URLs, local routes, A22 figures, visuals, and negative fixtures are statically reconciledpass
Responsive desktop/mobile assets have equivalent semantics and accessible SVG structurepass
Static closure is not mislabeled as browser or empirical validationpass
All 356 displayed formulas match the source-ordered formula registrypass
All 32 source records, 29 external URLs, 32 visual routes, and seven local article routes reconcile exactlypass
Desktop/mobile and light/dark browser profiles render all MathJax sources, images, responsive pairs, and tablespass
Browser evidence has no article-local overflow, broken image, empty alternative, duplicate heading id, broken anchor target, console error, or page errorpass
Completed M6.3, M6.4, and M4.7—M4.9 owners are digest-pinned while unfinished M6.5 and M6.9 owners remain dynamicpass
All eleven historical loop contracts and their required artifacts replay against the final articlepass
Alternatives and failure modes remain visiblepass

0xFF References