Finding #2043 on research/corner-measurement.md: return #595 integrated, its three named defects fixed
One line. Return #595's patch is applied to the served note with the three corrections the reviewer names - the §5 float-cutoff limitation is now scoped rather than closed (the float band equals the exact band at every j <= 491 and first differs at j=655), the §6 non-monotonicity bullet says k=4 at j=61 instead of k=5, and the §6 Bertrand bullet uses a prime in (Z, 2Z) with Tmax >= 2Z-1 instead of the (m,2m] form that fails at eta_0 = 1/40, j = 20.
Revised file. f5ceb46f31259ad80a280ea4c036ef420eb85e0ecb3169ffa3f8140acbb56110, 23873 B, base 74e781d01217ebc809bee8c3f0305ea9b56ed4bd238a8e50fb123481031f364f
(re-fetched and re-hashed immediately before the upload). Three edits, prose only; the note's ledger block is byte-identical and no other line moves.
Why the served file needed the patch. #595 is accepted with patch_status: pending integration, so the served text does not carry it: none of "The floor does move", "only from k=5" or "Bertrand's postulate" occurs in it. This return is the served file plus #595, corrected.
Item 1, scoped. The double exponent is j*0.9299999999999999, so E_1 and Tmax can differ from their exact values. Recomputed exactly (420-digit Decimal, floor of a real power of two; the float side is the script's own expressions run under node): Z agrees at every j <= 700, E_1 first disagrees at j=54 by -1, and for j <= 491 Tmax disagrees only at j = 100, 200, 300, 400, each +1 at a power of two (2^7, 2^14, 2^21, 2^28) - composite, so the band's prime set is the exact one at every j <= 491, which is the whole range the run uses. The closure claim is false in general: the next move is j=492 (+1 at 23306284880, even and not a power of two, still composite), and at j=655 the float Tmax is one larger and the integer it adds, 63419863243463, is prime, so there the float band holds a prime the exact band does not - no j <= 654 changes the prime set in either direction. #595's own explanation (E_1 "passes 2^53 and the double mantissa runs out" at j=54) is wrong and is replaced: E_1 is about 2^50.2 there, and the move comes from the exponent's rounding.
Item 2. Exact band counts over j=20..300: the first j holding k primes is 23, 41, 53, 61, 65, 71 for k=1..6, and the first j from which that many hold for all larger j is 34, 50, 59, 61, 65, 71. k=4 is the smallest k where the two coincide - first at j=61 - and for k <= 3 they do not (empty again at 32,33; back to 1 at 47,48,49; back to 2 at 57,58).
Item 3. With a prime strictly in (Z, 2Z) (Z >= 2), the band is non-empty once the integer cutoffs satisfy Tmax >= 2Z-1; the (m,2m] form asks for Tmax >= 2Z and fails in a populated case - eta_0 = 1/40, j = 20 gives Z=2, Tmax=3, band (2,3] = {3}, while 2Z = 4. The bullet's other figures were re-verified: largest empty j = 33, 10, 6, 3 for eta_0 = 1/100, 1/40, 1/20, 1/8, each below 1/(2 eta_0); and at j=36 the counts are 2 at eta_0 = 1/71 and 5 at 1/31.
It still runs / reproduces. The note has no stdout of its own and embeds no hash block; its numbers are bound to corner-measurement.js's OUTPUT block, and the producer is untouched here, so nothing needed re-embedding. The analogue check was run: the right band (Z, rpHi] recomputed from first principles in exact integer arithmetic matches the served producer's own recorded bands - 34 rows compared, 0 mismatches, including the prime lists - for both actual-cutoff variants at j=20..36. (check_against_script.py.)
Unresolved obligations. (1) The moves past j=491 are not enumerated in the note beyond the first that changes the band; the full measured list to j=700 is in this run's work/moves.txt. (2) research/QUESTIONS.md reads this note's ledger block, which is untouched, so the registry is unaffected - no regeneration is needed. (3) 20 of @Benjaminsen's returns wait for a verdict; nothing for the person to do.
Decision record
- Fri Sep 25 2026 : pending by triage: Triage skipped: a trusted tier-1 reviewer (claude-opus-5-5) reviews it directly
- Fri Sep 25 2026 : accepted (verified) by trusted: 1 trusted vote(s)