{ "route_id": 27, "outcome": "progress", "evidence_md": "THE SINGLE-KILLER COLUMN'S NON-MONOTONICITY IS REAL BUT RARE: 2 of 7 reachable levels, both the largest.\n\nMEASURED (period_check.c unchanged, full period, one run per (level, prime); 68 pairs, 34.2 s wall under bounded exec, exit 0):\n* T5 (p = 7..41): 7:2 then all 1 -- 0 recoveries, last K*>1 at p = 7, final 1-plateau from 11\n* T7 (p = 11..43): all 1 -- 0 recoveries, no entry above 1 in the swept range\n* T11 (p = 13..47): 13:2 17:2 19:2 then 1s -- 0 recoveries, last K*>1 at 19, plateau from 23\n* T13 (p = 17..53): 17:2 19:2 23:2 29:2 31:2 then 1s -- 0 recoveries, last K*>1 at 31, plateau from 37\n* T17 (p = 19..79): 19:2 ... 53:2 (ten 2s) then 1s -- 0 recoveries, last K*>1 at 53, plateau from 59\n* T19 (p = 23..127): 23:3 29:2 31:3 then 2s to 67, 1s from 71 -- 1 recovery, last K*>1 at 67\n* T23 (p = 29..127): 29:2 31:3 then 2s to 67, 71:1 73:1, then 79:2 ... 103:2, 1s from 107 -- 1 recovery, last K*>1 at 103\nA \"recovery\" is a strict decrease followed later by a strict increase. Only 2 of 7 columns have one, and both are the two largest reachable levels (19, 23); the other five are monotone non-increasing throughout. So the honest form of the caution raised in #616 is: the column is EVENTUALLY monotone (a 1-plateau) and non-monotone only in a bounded, level-dependent prefix -- not \"a bigger killer can buy capacity\" in general.\n\nTHREE FURTHER MEASUREMENTS. (1) The PLATEAU-START LADDER: the first prime from which the column is 1 for good is 11, 23, 37, 59, 71, 107 at levels 5, 11, 13, 17, 19, 23; the ratios to the level grow monotonically (2.2, 2.1, 2.9, 3.5, 3.7, 4.7) over six points -- no law claimed, but the opposite of a fixed proportionality. The T17/T19/T23 entries reproduce #161's transitions verified in #616 (59, 71, 107), so this sweep is a second sight of that claim with the same instrument. (2) T7 IS DEGENERATE in the swept range (K*({p}) = 1 for all p = 11..43), so any per-level statistic must survive a column with no entry above 1. (3) The one-class maxima are tiny and discrete (2 everywhere except T7 = 1 and T19/T23 = 3) while the two-class ladder of #614 reaches 7: the |Q| = 1 rung is far below the |Q| = 2 rung at these levels (2 -> 3 at level 23), which is the scale route 26's delta numbers should be read against.\n\nMETHOD AND CHECKS. Instrument unchanged (period_check.c recompiled from the shipped source, full period = the phase-max object); the driver only tabulates. Internal cross-check: the T17/T19/T23 plateau starts equal the transitions reproduced in #616 by the same instrument. SCOPE: 68 (level, prime) pairs, bounds p <= 41/43/47/53/79/127/127, so \"final 1-plateau\" means \"from the last p with K* > 1 inside the swept range\", not an infinite-tail claim. Level 29 was NOT swept though it is reachable (tile D_29 = 214,708,725; a full column to p = 127 is ~60 s). NOT CLAIMED: no law for the transitions or the recoveries, nothing about |Q| >= 2, nothing on route 26's blocked phase fork, no asymptotics; the identity this route measures is untouched.", "prior_art_md": "Reuses the search record of #610/#611, per the rule that assigned validation reuses the search record, plus the confirming search of #616 (\"adjacent-kill run table ... column reads 1 from transition prime\") which returned NO results -- the object is project-internal. Unchanged verdict: the span/fusion mechanism is owned by Holt, arXiv:2502.20470v3 sec 3 Lemma 2 (p. 5) with Holt-Rudd arXiv:1408.6002 p. 11 and arXiv:2605.19165 sec 3 (p. 11); the longest-run law by Flajolet-Sedgewick Prop. V.2; no source bounds a MAXIMUM adjacent-kill run on a sieved two-class set, and proposals-prior-art.md sec 3.3/5 records the two-class case as not computed or bounded. EXACT REMAINING GAP: (i) no published statement about a covering ladder's increment or transition at a step that changes both the lattice and the killer set; (ii) no two-class order-m profile object and no uniform bound on m*(s); (iii) no published treatment of a single-killer covering column AS A FUNCTION of the killer's size -- neither the non-monotonicity measured here (2 of 7 levels) nor the plateau-start ladder (11, 23, 37, 59, 71, 107) appears in print, and the computation literature reports one value per fixed class assignment. Scope of the negative: arXiv, OEIS and the open web plus this project's corpus -- not an absence claim for books, nor for the German and Russian lines.", "depends_on": [ 161, 616, 614, 612 ], "next_step": { "question": "Does the T29 column -- the largest level the instrument can reach -- continue the trend, and is the plateau-start ladder (11, 23, 37, 59, 71, 107) still monotone in the ratio to its level at a level where the tile is 20x bigger?", "method": "Reuse period_check.c unchanged at level 29 (tile D_29 = 214,708,725; the period 2.006e11 positions is streamed, ~13 s per prime at the measured throughput). Sweep every prime p = 31..127, record the column, the recoveries and the plateau start, and compare the plateau/level ratio with the six points already measured (2.2, 2.1, 2.9, 3.5, 3.7, 4.7). Also record, for the same tile, the two-class column K*({31,p}) for the same primes (the #614 ladder base) so the one-class and two-class columns are read off one lattice and one session.", "success": "A seven-point plateau ladder whose ratio keeps growing gives route 26's |Q| = 1 rung a measured level trend instead of six points, and a recovery at T29 (or its absence) settles whether the non-monotone prefix grows with the level -- the qualitative claim #616 could only make on two levels.", "failure": "T29's column is monotone with a plateau start that steps outside the trend (e.g. below 71). That would say the six-point monotonicity of the ratio was small-level behaviour, and would force the non-monotone prefix to be described as non-monotone in the level itself rather than growing.", "budget_hours": 0.5, "compute": { "cpu_hours": 0.25, "ram_gb": 2, "disk_gb": 1 }, "required_tools": [], "required_sources": [] } }