/teal-sea
teal-sea / zeta-labstate of record · compiled 28 Sep 2026 · revision e4945c4 · source

Library · hunts/r_a7c12f/RESULTS.md

R-A7C12F: `637/1000` survives at depth 1; the table row compares two different ranges

1,856 words · 220 lines · source

2026-08-23. Run e09a7f8a. Reads: hunts/frontier_math/K2-TWO-SPECIES.md section 2, two_species.py, Zeta23Ext/EForm3/FarField.lean, Zeta23Ext/EForm3/Counting.lean. Instruments: probe.py here, hunts/r_a97060/ball_field.py (Arb at 96 bits). Nothing here is evidence for or against RH (docs/08).

Verdict

The claim is withdrawn. 637/1000 does survive at depth 1 on the range it is asserted on, with 0.82% to spare, and the ball pass says so at enclosure-carrying grade. The 0.6636 is real as a number and wrong as a refutation: it is a supremum taken over s in [8, 400], while 637/1000 is only ever claimed for s >= 37.0135. The two starred rows of that table both sit under the constant that actually applies where they are attained.

There is a genuine defect underneath the false one, and it is the one a k >= 3 pass will meet. It is not the constant. It is the derivation route.

The four questions the one sentence had merged

1. Wt_tail_le has no depth in it

Counting.lean:93 reads, in full:

lemma Wt_tail_le {w : ℝ} (hw : 1368 ≤ w) : Wt w ≤ (637/1000)/w

with Wt w = (5/8)/w + (611/50)/w^2 + (6711/100)/w^3 + (2583/25)/w^4 (FarField.lean:35). That is an inequality between two explicit rational functions of one variable. No y occurs in the statement, in the hypothesis, or in the proof, which is nlinarith on a quartic. It cannot fail at depth 1 because it cannot see depth at all.

The lemma that does carry the depth is Qim_far_sq / Qim_far_sq_abs (FarField.lean:227, 232):

theorem Qim_far_sq {y s : ℝ} (hy0 : 0 ≤ y) (hy : y ≤ 1/2) (hs : 28/5 ≤ s) :
    Qim y s ^ 2 ≤ y^2 * Wt (s^2 - 2)

hy : y ≤ 1/2 is the hypothesis at issue. K2-TWO-SPECIES.md named the wrong lemma, and naming the wrong lemma is what made a range mismatch look like a crossed constant.

2. The sup is attained ~8.7x below the threshold

w = s^2 - 2 >= 1368 is s >= 37.0135. two_species.far_constant scans [8, 400]. Where the sups actually sit:

depthfar constant on [8,400]argmax sw at argmaxw >= 1368?proved envelope Wt(w)*w there
1/20.621996812.7150159.67no0.70419
10.663591712.6250157.39no0.70538

Both rows are attained near s ~ 12.7, in the second window, nowhere near the tail regime. And at their own argument the proved envelope is 0.705, so neither 0.6220 nor 0.6636 was ever in conflict with anything proved. The depth-1/2 row's parenthetical "(proved <= 0.637)" is the same mismatch, and it happened to flatter rather than alarm.

Wt(w)*w falls from 0.840 at s = 8 to 0.634 at the threshold and to 5/8 = 0.625 as s -> inf. 637/1000 is the value of that envelope at w = 1368 rounded up, which is why it is stated there and not earlier.

3. On its own range, the constant holds at depth 1: enclosure-carrying

Arb at 96 bits through ball_field.D_enclosure, over s in [37.0135, 400], adaptive cells bisected wherever the running bound exceeds 0.50, floor 1e-4. Dam <= max(0, D_upper) and y^2 >= y_lo^2, so every cell bound is outward.

depthball upper boundfloat scan supenclosure costclosed-form asymptotevs 637/1000margin
0.250.58443950.58440801.0000540.5809884holds+0.0526
0.500.59370780.59367671.0000520.5901137holds+0.0433
0.750.60936870.60933731.0000520.6055774holds+0.0276
1.000.63177350.63174081.0000520.6277706holds+0.0052

The enclosure costs a factor 1.00005, so the verdict is not an artifact of interval width. 45,030 cells and 18,885 bisections at depth 1; whole probe 96.6 s.

Depth as a genuine interval, which is what D_enclosure takes:

depth intervalball upper bound(y_hi/y_lo)^2 inflationvs 637/1000
[0.99, 1.0]0.64503881.02030fails
[0.995, 1.0]0.63835421.01008fails
[0.999, 1.0]0.63308151.00200holds

That is arithmetic about the normalisation, not about the field: dividing by the cell's smallest y inflates by the square of the cell's relative width, and the true margin at depth 1 is 0.82%, so cells wider than ~0.4% cannot close however tight the enclosure is. Anyone wanting a depth-interval statement over [1/2, 1] needs ~174 geometric cells, not a coarse grid.

4. Where the constant does break, and what actually breaks first

On the asserted range, sup Dam*(s^2-2)/y^2 first exceeds 637/1000 at depth 1.0494 (float scan; asymptotic break depth 1.0855). Depth 1 sits inside that with room; depth 2y for y <= 1/2 sits exactly on its edge, which is the case k >= 3 needs.

What breaks before the constant is the lemma that delivers it. Qim^2 <= y^2 Wt(s^2-2) measured as a ratio:

depthmax Qim^2 / (y^2 Wt(s^2-2))argmax sholds?
0.500.9441368395.836yes
0.750.9688757395.836yes
0.950.9963791395.836yes
0.970.9995243395.836yes
1.001.0043806395.836no
1.251.0515569395.835no

The ratio grows with s, so this is asymptotic and not an edge effect. To leading order Im ghat(y+is) = -2 sinh(y/2) cos(1/sqrt2) cos(s/2)/s + O(1/s^2), so the normalised quantity has limsup

4 sinh(y/2)^2 cos(1/sqrt2)^2 / y^2

and Wt(w)*w -> 5/8, so Qim_far_sq holds asymptotically iff that limsup is at most 5/8, i.e. iff y <= 0.972659. The closed form is checked, not asserted: it predicts 0.6277706 at depth 1 and 0.5901137 at depth 1/2, against float sups of 0.6278055 and 0.5901440 on [400, 4000], agreeing to five digits. It also predicts the ratio 0.6277706/0.625 = 1.004433 against the measured 1.0043806.

So the correction a depth-1 argument must carry is real, and it is this: the y <= 1/2 hypothesis of Qim_far_sq is load-bearing and fails just below depth 1. The value 637/1000 is fine. The route to it is not.

What this changes for k >= 3 (R-B9552D's declared dependency)

The dependency edge said a constant in K2-TWO-SPECIES.md being wrong is an input to the two-species centre-gas split. The edge holds, with the content replaced:

Honest scope

Grade: the depth ladder over s in [37.0135, 400] is enclosure-carrying (Arb, 96 bits, outward, cross-checked against an independent float scan at 1.00005). Everything else here is measured: the break depths, the Qim_far_sq ratios, the asymptotic constant, and the argmax locations are double-precision scans. Nothing compiles to Lean.

What is not closed, precisely:

Ledger

harness/departments/review_ledger.py now carries k2-far-constant-depth1 as a ClaimUnderReview with this run's AttackOutcome (white-box) appended. harness.review.standing_reasons reports the claim as not standing, because no blind attack has run, which is the true state, not a formality. This hunt's task came from the thread roster (threads.json R-A7C12F), not from a harness generator: it was in no generator's output before this commit and could not be removed from one. See notes_for_operator in HANDBACK.json.

Loose threads