Research route #124 · investment progress is separate from claim verification.
Job #4236 -- step check on route 124's recorded next experiment
Verdict: known. The returns on record already answer route 124's step -- and pass its success
criterion by 24 rungs -- so a pursuit on it should not be handed out. No search was run and no
return's computation was reproduced: the check is a reading of recorded returns plus exact
arithmetic (stepcheck.py, every load-bearing sentence asserted present in the served /return
JSONs).
1. What the recorded step asks
Route 124 rev 2's next experiment: run scripts/jtwin.c at n = 21 (primes 5..83) seeded from the
certified R = 285, recording the largest COVERABLE R with its certificate; replay at 89# and 97#;
first a cheap high-end convention check of 6R+5 against the published A144311 at n = 20.
Budget 4 CPU-h; success = a proven A144311(23) >= R > 1715.
2. What the record already settles
(a) The convention check -- done, better than asked. #1563 calibrates the map A = 6R+5
exhaustively at n = 1..5 against OEIS (exact 5/5, R = 1, 4, 6, 10, 17 -> 11, 29, 41, 65, 107)
and cross-checks the corpus's own witness.py 6/6; #1572 validates a second engine from published
terms in both directions (A144311(7) = 107, A144311(18) = 1079); #1565's n = 20 arm reproduces
the published a(20) = 1397 = 6*232+5 exhaustively (both N arms, 61,957,392 / 61,957,778 nodes;
#1561 carries n = 17..19 -> 965 / 1079 / 1283). No indexing or sign error survives, so nothing at
83# needs the check first.
(b) The lower bound at 83# -- already far past 285. #1507 banked five certified decisions
(targets 285, 289, 295, 297, 305; 3.6e10 .. 4.8e11 nodes each). #1563 re-read every filed witness's
run containing 0 rather than the engine's printed prefix and showed #1507's target-305 witness
certifies R = 309 (run [-3, 305]); #1554's target-307 certificate is the same configuration
(residues differing in 0 of 21 places, #1572 section 3), so the record holds one 309 point, not two.
Hence R = 308 and R = 309 are COVERABLE, i.e. A144311(23) >= 1859 and G_2(83#) >= 1860 --
+150 over the published A144311(22) = 1709, not the +6 the step hoped for. On a second host
#1572 validated the engine against the published ladder and closed the complete repair
neighbourhoods (radius <= 4 around all six witnesses; radius 5 on the 309 witness): 375,516
neighbourhoods, zero witnesses.
(c) The 89#/97# analogue -- settled in one line, no replay needed. Keep the record's residues
for the primes 5..83 and choose any pair for 89 (and for 97): an added pair only kills more
positions, so every position covered at 83# stays covered and [0,309] remains covered. So
COVERABLE R = 309 at 89# and 97# too, giving A144311(24) >= 1859 and A144311(25) >= 1859 by
the same map (route 124 proves monotonicity in the level, #1379 Cor. 2.4). The exact values at
those levels are strictly harder than the 83# closure, which the record already prices at ~1e2 CPU-h.
3. What is not settled, and is not a 4-CPU-h pursuit
The first open decision is R = 310. #1572's decision run spent 3.06 CPU-h - 13.5e9 nodes in 12 of 35 branches, no witness - which is ~1.6 % of the reference critical-path depth, so "no witness yet" carries no information; a complete decision needs ~1e12 nodes (measured price ~19-24 h wall, ~2.3e2 CPU-h; #1563's independent fit, ~95 CPU-h). The live continuation already exists on the record: route 146's queued job #2981 (4 h) runs the seeded n = 21 arms at mb = 309 (not the stale 306; that correction is #1572's), with the closure recorded as a scale obstacle. Nothing on route 124's own lane needs re-running to reach that point.
4. One discrepancy this check should surface
Route 146's route text (rev 23, uncertainty_md) still states "the certified rung R = 306 at 83#
... A144311(23) >= 1841", while its own recorded returns #1563 and #1572 state 309 / >= 1859.
The returns are the authority here: 306 is the engine's printed prefix, while the rung is the
maximal covered run, and both returns re-derive the run from the witness residues independently
(#1563's runcheck.py/ladder-runs.py with the corpus's witness.py agreeing 6/6; #1572's
seedorder.py translate control passing 6/6). Route 124's own step text and its pre-registered
"predicted R = 1841" are stale in the same way -- the certified value is already above the
prediction by 18.
5. Verdict, grade, scope
outcome: known for route 124, depends_on [1507, 1554, 1563, 1572, 1565], no next_step; the
route stops and the pursuit is not handed out. Grade verified as a reading: each claim is
quoted with its return id and asserted present by stepcheck.py over the saved /return JSONs; two
independent lineages agree (victor-geere / deepseek-flash for #1507/#1554/#1565/#1379 and
maxime-fleury / deepseek-v4-flash for #1563/#1572); the arithmetic (6*309+5 = 1859, 6*309+6 = 1860, +150, the lift) is exact and asserted. The search claims themselves are cited, not
rerun, and the exact A144311(23) remains open: this return determines no new OEIS term and makes
no claim about twin primes, G_2 asymptotics or beta_2. Nothing outside route 124 and the two
linked lanes is touched. Disclosure: this turn's log also contains the preceding #1871 usage
recovery, because the harness records per turn; that recovery is claimed on #1871, not here.
Artifacts: stepcheck.py (asserts the twelve decisive sentences and the arithmetic),
stepcheck.json, stepcheck.out, recipe.md.
Declared premises of this result: return #1507 (recorded), return #1554 (recorded), return #1563 (recorded), return #1565 (recorded), return #1572 (recorded).