This note interprets the scaling result for the shipped lpp_seed program.
It is not the repository's cross-category summary. For the current retained leaders, see CANDIDATE_CATEGORIES.md.
This note explains what the completed reproducible exact scaling results suggest, and what they do not prove.
The completed reproducible exact scaling stages do not support the idea that the current LPP seed keeps its lead as the horizon rises.
On stage_a and stage_b, li_inverse_seed has the best worst-case, mean, and median seed ppm in every tested family:
boundary_windowoff_lattice_decimaldense_local_window
That means the current best exact reading is not:
LPP found a stronger seed law that keeps beating the classical seeds as the horizon rises.
The current best reproducible exact reading is:
LPP was unusually strong on the baseline regime, but the deeper completed exact stages favor
The old exact stage_c path has now been replaced in local workflow.
Instead of trying to regenerate a higher exact stage in local workflow, the repository now uses a local continuation on
That continuation is useful because it keeps the scaling workflow alive on this machine without heavy oracle tooling.
It does not mean the reproducible exact reading changed. It means the repository now has a second stage with a different contract.
The main question in the scaling program was about worst-case seed ppm.
That answer is now clear on the completed horizon:
- baseline:
lpp_seedwins the tail - completed deeper stages:
li_inverse_seedwins the tail
So the current LPP correction architecture does not keep the baseline tail advantage once the reproducible exact horizon is extended through the completed stages.
The average story is even less favorable to LPP on the completed reproducible exact stages.
On stage_a and stage_b, li_inverse_seed also wins mean and median seed ppm in every family. So the deeper exact evidence does not merely take away the tail lead. It takes away the average lead as well.
The boundary heatmaps are still useful. They show that LPP has coherent signed-error structure near decade transitions instead of chaotic noise.
That is interesting, but it is not enough on its own.
An orderly residual pattern can still be larger than a classical comparator's residual pattern. That is what the completed scaling stages now show.
The current correction architecture still appears to be doing something real in the baseline regime.
The log-squared pull still looks like a meaningful curvature correction to the Cipolla-style backbone. The sublinear lift still looks like a real residual-scale correction in the baseline range.
But the completed deeper reproducible exact stages suggest that these two fixed corrections do not track the deeper residual structure as well as the inverse-log-integral seed does.
The most natural reading is:
- the LPP corrections improved the backbone in a finite regime
- that improvement was not stable enough to beat
$li^{-1}(n)$ on the deeper completed reproducible exact stages
These results do not prove an asymptotic law either way.
They do not prove that LPP must always lose beyond the completed stages.
They do not prove that
They do show something narrower and important:
The strongest current reproducible exact evidence no longer supports the claim that the present LPP seed architecture scales best.
The new local continuation shows something different and also important:
When the local stage is labeled by its declared local continuation source, the local continuation strongly favors LPP.
That tells us the current LPP structure is much closer to the local continuation than it is to the inverse-log-integral seed on that stage.
The honest next moves are now much narrower:
- decide whether the repository still wants a published exact or reproducible exact
stage_c, or whether the local continuation is the intended local stage from now on - test whether a different fixed correction architecture can recover a tail lead on deeper reproducible exact stages
- derive a theory-backed correction form instead of treating the current one as the final structure
Until then, the best current reproducible exact answer is the one already recorded in SCALING_RESULTS.md.