# Job 4256 (route 82 rev 7): criteria fixed before the T37 run (2026-09-26T23:59:21Z) Copied from the route's step (#1889's next_step), no edits: - Success: rho_1(60, T37) > 0.1800 and the (60,60) cell still carries >= 90% of the lag-1 deficit at p = 29 and 31; repayment(T37,29) < 0.5561 and repayment(T37,31) < 0.5084; repayment at p = 41 and 43 stays in [0.60, 0.80]. - Failure: repayment at p = 29 or 31 at or above its T31 value (the fall stops); or repayment at p = 41/43 outside [0.60, 0.80]; or the (60,60) share below 90%. - Definitions as in #1889 (analyze2783.py / pairs2783.py / selfpair2783.py): rho_L(g) = R_L(g) (D-1) / (h_g (h_g - 1)); repayment = (K_2 - E)/(E - K_1), E = m(m-1)/(D-1). Instrument: lagspec.c of #1889 with HV 64 -> 128 (one-line diff; output lists nonzero pairs only, so bytes at g < 384 are unchanged). Gates passed before the run (this job): brute2783.py T17 (13 folds, 32 fields) and T19 at SEGW=16 (14 fields), 0 mismatches; HV=128 build reproduces ls23/ls29/ls31.json byte for byte (T31 27.6 s on 6 threads). Command: ./lagspec128 37 6 17,19,23,29,31,37,41,43,47,53,59,61 under sah run-limited (timeout 2700 s, RLIMIT_CPU 10800 s). ## Addendum written during the run, before its output exists (2026-09-27T00:00:24Z; n37.raw is empty) Exact prediction by CRT inclusion-exclusion (ie4256.py, rho4256.py -> rho60.json), which reproduces h_60, R_60 and D of ls23/ls29/ls31.json exactly: - T37: D = 217929355875, h_60 = 9831828408, R_60 = 100535086, rho_1(60) = 0.226655 (> 0.1800: the step's first success clause is decided before the run). - Any mismatch of these three integers with n37.json is a defect in one of the two instruments (stop and report).