High-contrast homogenization: Provider.Quenched.SmallContrastEndpointDataMinimal #
Imported from the Apache-2.0 HighContrastHomogenization development at commit
7a13dbcd8d6609264a713373f5c69ceeac870472.
The endpoint's frozen-side data, with the burn-in's own upper bound #
This is the half the polynomial burn-in cannot supply on its own.
exists_endpoint_frozen_data_minimal returns the burn-in N1 as an existential
and records only sK + 1 ≤ N1. That is everything the account needs and
nothing hentry needs: hentry must bound 3 ^ N1 above by a power of the
telescope's base, and an existential burn-in admits no upper bound at all.
The repair is the same one applied to the source scale and the gap
separately: expose the burn-in's decomposition. N1 = sK + 1 + gap is how
exists_bootstrap_smallness_uniform_minimal builds it, and gap comes from the
gap existence statement, whose minimal companion
exists_gap_three_pow_le_minimal carries the upper bound
3 ^ gap ≤ 3 * max 1 (CB * factor / sigma) at no cost — the same ⌈log₃ ·⌉ witness, one more
conclusion.
So this file is a parallel restatement, not new mathematics: the same constant,
the same proof, with gap returned beside the data it determines. With it and
exists_source_scale_minimal, exists_burnIn_exponent_canonical applies and hentry
closes.
The bootstrap floor at a minimally chosen gap. The parallel of
exists_bootstrap_smallness_uniform_minimal that returns the gap it built the burn-in
from, together with the gap's own upper bound.
The endpoint's frozen-side data, with the gap exposed. Identical to
exists_endpoint_frozen_data_minimal except that the burn-in is presented as
sK + 1 + gap with the gap's upper bound — which is exactly what
exists_burnIn_exponent_canonical consumes.