/teal-sea
teal-sea / zeta-labstate of record · compiled 02 Nov 2026 · revision b09fa4dd · source

Library · hunts/dbn_pt_height/evaluator/DH_GATE_PREREG.md

DH_GATE_PREREG: the Davenport-Heilbronn refusal gate, preregistered

1,247 words · 138 lines · source

Written and committed 2026-10-26, before the gate was run. The commit that adds this file precedes every gate run. dh_gate.main writes dh_gate_results.json, and the result is recorded in RUNS.md (E7) as this file defines it, whichever way it comes out. If anything below is changed after the run, it is a new preregistration with a new run, and the first result stays on record.

What the gate asks

Would the barrier decision this evaluator makes for zeta call a rectangle zero-free that holds a zero of the Davenport-Heilbronn heat flow? The decision is the rule of effective.barrier_rectangle (Polymath 15, Section 8.4):

It runs on DH through dh_gate.dh_barrier:

Parameters, fixed here:

The ground truth for each box is hunt #61's own decided count, winding.winding_rectangle at 420 bits on the narrow-frame image of the box. It uses a different rule (chord clearance against M2 h^2/2, then Re(H_b/H_a) > 0), so the gate does not grade itself.

The boxes (wide frame, exact rationals)

nametxyexpectedwhy
Z1144/625[245909/512, 123159/256][3/512, 35/512]one zero2 x hunt #61's decided box at t = 36/625 (its winding_results.json, t2_stretch_run)
Z20[171.2, 171.6][0.5, 0.7]one zerothe pinned zero 0.80852 + 85.69935i of zeta.epstein, z = 171.3987 + 0.6170i
Z30[228.1, 228.5][0.2, 0.4]one zeroSpira's 0.650830 + 114.163343i, z = 228.3267 + 0.3017i
Z40[353.2, 353.6][0.35, 0.55]one zeroSpira's 0.724258 + 176.702461i, z = 353.4049 + 0.4485i
C1144/625as Z1[1/5, 3/5]nonecontrol above Z1
C20as Z2[0.8, 1]nonecontrol above Z2

"Expected" is a prior. The truth step decides each box.

The decision table

For each box, with the truth's decided count N (or none) and the pipeline's winding w (or undecided):

box kindtruthpipelineclass
zeroN >= 1w = NREFUSE
zeroN >= 1undecidedREFUSE_WEAK
zeroN >= 1w = 0ACCEPT (the pipeline called a box with a zero zero-free)
zeroN >= 1w >= 1, w != NINCONSISTENT
zeroN = 0anyTRUTH_EMPTY (excluded, reported)
controlN = 0w = 0DISCRIMINATES
controlN = 0undecidedNON_DISCRIMINATING
controlN = 0w != 0INCONSISTENT
controlN >= 1anyCONTROL_NOT_EMPTY (excluded, reported)
anyundecidedanyTRUTH_UNAVAILABLE (excluded, reported)

Verdict (dh_gate.verdict):

A failed DH computation excludes nothing (CLAUDE.md), so an INCONCLUSIVE gate says nothing about zeta.

The planted faults

Each fault runs on all six boxes with the same truth.

Caught means its verdict is FAIL. A fault that only makes the pipeline stricter cannot be caught by a refusal gate, and that is recorded, not hidden.

faultwhat it doesmust be caught?expectation, from the development box D0
one_cornercalls the box zero-free whenH> 0 at its lower-left corner. This is the row-2 pattern of CHAIN.md: one check at (N0, y0), the rest argued.yescaught (D0: winding 0 on a box with a zero)
main_terms_onlyf = A + B, the sharp main terms with no correction, E = 0yescaught (D0: winding 0)
no_marginaccepts a segment when its endpoint balls exclude 0, with no D h/2 term and no refinement from 4 points per edgenopossibly not caught (D0: still winding 1)
no_M2D without the M2 h/2 termnopossibly not caught (D0: still winding 1)
narrow_framewide coordinates and time handed to the narrow-frame instrument unconvertednostricter, not caught (D0: every segment fails, undecided)

The gate is accepted as a control if the clean pipeline's verdict is PASS, and both must-catch faults give FAIL. Anything else is reported as it is.

What was computed on gate points before this file was committed

All of these were point evaluations, never a box decision:

The boxes were drawn from the literature coordinates and #61's recorded box, with no box decision run on them.

Cost estimate (before the run)

Development boxes, one process, load average about 21 to 35:

Six boxes times (truth + clean + five faults) comes to under 20 core-minutes, well below the one core-hour that needs the coordinator. One process, nice 10, started only once the load average is under 64.

Grades