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

Library · hunts/below_seven_eighths/MISSION.md

MISSION: `below_seven_eighths`, pushing the zero-free half-plane under 7/8

1,624 words · 151 lines · source

Numbering note, 2026-10-30. In this hunt's files "#134" names seven_eighths_pin/, the 13/15 ceiling hunt, which was opened as #134 and is case-logged as hunt #139. On main, #134 is gauss_positivity/. The text below keeps the name it was written with.

Opened 2026-10-21. Hunt #136. The owner directed the laboratory on 2026-10-21 to attack RH. This hunt is the campaign's first track because a fixed zero-free half-plane is the RH-direct quantity the field is moving right now, and the only one whose argument consumes the Euler product at a named step. Nothing in this directory is a result until the case log in hunts/README.md says how it ended.

Renumbering: seven_eighths_pin/ takes #139 on main's case log (opened as #134 on claude/hunt-134-seven-eighths-pin); in-hunt references below still say #134.

Grades used here: cited (a line of a paper's LaTeX source, quoted), derived (algebra done here, checked in exact rational arithmetic by this hunt's tests), inferred (a reading of a paper's structure that no computation here checks), measured, hardened (independent routes agree, or ball enclosures carry every step) and kernel-checked (Lean, zero sorry, standard axioms). The reserved enclosure word belongs to zeta/rigor.py and appears nowhere in this directory.

The question

Can the zero-free half-plane for every Dirichlet L-function be pushed below the best public abscissa, 0.8748867? What is the smallest abscissa reachable (a) inside OpenAI's Part II assembly by strengthening its row-count inputs, whose ceiling hunt #134 places at 13/15, and (b) by a probe whose constants are not tied to the sextic pole?

Starting point

Scope

id: below_seven_eighths
question: Can the zero-free half-plane for every Dirichlet L-function be pushed below the best public abscissa 0.8748867, and what is the smallest abscissa reachable inside OpenAI's Part II assembly by strengthening its row-count inputs, or by a probe not tied to the sextic pole?
frontier: 7/8 (OpenAI 2026-09-30, formal statement kernel-checked here, argument unreviewed); public follow-ups 0.8749570194 (Guo), 0.874957 (Liu), 0.8748867 (Xu and Sang), 0.874887 for Hecke L-functions (Liu); hunt 134 places the geometry corner at M + l <= 1 and M - 2l >= 1/2, the re-optimized geometry at 0.8749417 and the perfect-row-count ceiling at 13/15
proposed_attack: price every row-count input of the final assembly by exact shadow prices, read the proofs of the binding inputs for slack, test any sharper count by exact enumeration, check the Euler-product step by exact local computation, and price alternative comparison systems under the paper's generic estimates
dead_routes:
  - substituting a smaller number for 7/8 in the final section without rederiving the row counts and the bootstrap it inherits (hunt 134)
  - re-choosing the Part II geometry with the paper's row counts held fixed, which gains at most 5.8e-5 (hunt 134)
  - reading the half-plane as information about real part 1/2 (docs/39)
  - treating a zero of a linear combination of L-functions as a counterexample to a statement about single L-functions (hunt 120)
required_oracles:
  - the paper's LaTeX source at the pinned commit, quoted by line number, with its SHA-256 checked
  - exact rational arithmetic reproducing every printed constant of the paper
  - exact small-case enumeration for any sharpened counting input
  - exact local computation of Euler factors and Gauss sums for the Euler-product step
  - the Lean kernel for any formal piece, with axioms printed
kill_conditions:
  - the symbolic assembly fails to reproduce 7/8, the margin 49/440640 or the re-optimized 0.8749417 at their stated parameters
  - a sharpened input fails exact enumeration at a small case or contradicts a step of the cited lemma's proof
  - a claimed improvement is matched or beaten by a public follow-up already on record
  - a claimed arithmetic step also holds for a function with a zero beyond the claimed abscissa, such as an Epstein zeta or a linear combination of L-functions
agents_may:
  - read and quote papers
  - derive
  - code exact arithmetic
  - attack derivations
  - formalize
  - build the pinned Lean closure locally, one build at a time
agents_may_not:
  - declare novelty
  - declare theorem status
  - claim any improvement to the half-plane as established
  - promote their own claim
  - push, publish or contact outside parties

Disposition draft, 2026-10-26 (resumed in place; the owner decides)

Added when the lane was resumed in place by the owner's decision of 2026-10-26. The text above is the mission as opened and is kept unchanged. This section is a draft: a hunt cannot promote or close itself, and allocation is the owner's call.

The bar has moved. The question names 0.8748867. On 2026-10-21 the lane recorded smaller public claims, down to 0.8748087 merged and 0.8747729897 in a draft (FOLLOWUPS.md section 1). On 2026-10-26 the smallest bound merged on QuasiRiemannTracker is 349843/400000 = 0.8746075 (PR 76, merged 2026-10-26T01:30:22Z), and the open PR 79 claims 4373037/5000000 = 0.8746074 (FOLLOWUPS.md section 14). None is refereed or replayed here. Every tracker entry from PR 63 to PR 78 keeps M + l = 1 and the h/6 signal in its Lean import closure (inferred from a source reading; not built). So the 13/15 floor model still frames that line, if its floor rows are still counted in full, which was not checked.

The kill condition, read honestly. "A claimed improvement is matched or beaten by a public follow-up already on record" needs a claimed improvement, and this hunt has none: every lane page says that no smaller half-plane is claimed. The condition is therefore not triggered. That is not a success. It only shows that the condition was written for a candidate the hunt never produced. Its intent was not to spend on what the public record already covers, and that intent now applies with more force. Part (a) would have to land between 13/15 and 0.8746075, a window 0.0079408 wide (X22). The public line works on the same row-count and moment inputs (section 5 of FOLLOWUPS.md: I1, I3, I5, I6) and moved 2.0e-4 in five days. This hunt's row-count lane found no recount that gains at the paper's inputs.

Dispositions (ALIGNMENT.md section 5), proposed:

Grades: the bar and the PR states are cited from the tracker's API; the floor-model reading of each PR is inferred; the gaps are derived (pinned by test_followups_identities.py).