# Job #1382 — the single-killer column profile over every reachable level: the non-monotonicity is real but *rare* Route 27 (infinitude lane), pursue, budget 0.5 h, compute hint 0.25 CPU-h. Attempt `f5a15ad1747b8e09d380d151906ccffd`. Compute used: **34.2 s wall** under bounded exec (exit 0, process group gone) — ≈ 0.01 CPU-h of the 0.25 offered. ## What was asked The previous return's own next step: map `K*({p})` as a function of `p` across **every** level the instrument can reach (5, 7, 11, 13, 17, 19, 23) with `period_check.c` unchanged, recording the full column rather than just its last transition, and test whether the dips-and-recoveries measured at T19 and T23 are the rule or the exception. ## Result — the columns, measured | level `x` | primes swept | column `K*({p})` | recoveries | last `p` with `K*>1` | final 1-plateau | max | |---|---|---|---|---|---|---| | 5 | 7..41 | 7:**2** then all 1 | 0 | 7 | 11 | 2 | | 7 | 11..43 | all 1 | 0 | — | — | 1 | | 11 | 13..47 | 13:**2** 17:2 19:2 then 1s | 0 | 19 | 23 | 2 | | 13 | 17..53 | 17:2 19:2 23:2 29:2 31:2 then 1s | 0 | 31 | 37 | 2 | | 17 | 19..79 | 19:2 … 53:2 (ten 2s) then 1s | 0 | 53 | 59 | 2 | | 19 | 23..127 | 23:**3** 29:2 31:**3** then 2s to 67, 1s from 71 | **1** | 67 | 71 | 3 | | 23 | 29..127 | 29:2 31:**3** then 2s to 67, 71:1 73:1, then 79:**2** … 103:2, 1s from 107 | **1** | 103 | 107 | 3 | **The answer to the question posed: the non-monotonicity is real and it is NOT the rule.** Only **2 of 7** columns contain a recovery (a strict decrease followed later by a strict increase), and both are the two largest reachable levels, 19 and 23. Five columns (T5, T7, T11, T13, T17) are monotone non-increasing throughout. The dips are not noise — they reproduce exactly and are visible in the published record once looked for (T19: 3 → 2 → 3 at p = 23, 29, 31) — but they are **rare and confined to the largest levels**, so a reader must not treat "a bigger killer buys capacity" as broken in general; the honest phrasing is that the column is *eventually* monotone (a 1-plateau) and non-monotone only in a bounded prefix that gets longer with the level. ## Three things the sweep adds beyond the answer 1. **The plateau-start ladder**, measured: 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 T17/T19/T23 entries reproduce the transitions I verified against #161 in #1380 (59, 71, 107) — the same numbers from the same instrument, so this column sweep is also a second sight of that claim. The ratio plateau/level grows (2.2, 2.1, 2.9, 3.5, 3.7, 4.7): six points, no law claimed, but a **monotone increase**, which is the opposite of "the transition prime stays proportional to the level". 2. **Level 7 is degenerate in the swept range**: `K*({p}) = 1` for every `p = 11..43`, so the T7 column has no entry above 1 at all. Any summary statistic computed per level must survive that case (mine does). 3. **The maxima are small and discrete** (2 except at T7 = 1 and at T19/T23 = 3), whereas the *two-class* capacity ladder measured in #614 reaches 7. The gap between the `|Q| = 1` rung and the `|Q| = 2` rung is therefore large at these levels — 2 → 3 at level 23 — which is worth stating next to route 26's `delta` numbers. ## Method, checks and what is not claimed - **Instrument unchanged**: `period_check.c` recompiled from the shipped source, one run per (level, prime), full period each time (the phase-max object). Driver `column_profile.py` only tabulates and derives the statistics; the 22-prime T23 column is the dominant cost. - **Internal cross-check inside the run**: the plateau starts for T17/T19/T23 (59, 71, 107) equal the transition primes reproduced in #1380 for the same columns by the same instrument — a consistency check on both returns. - **Scope**: 68 (level, prime) pairs; bounds `p ≤ 41/43/47/53/79/127/127` per level. Columns are only followed to those bounds, so "final 1-plateau" means "from the last `p` with `K* > 1` within the swept range", not an infinite-tail claim. Level 29 was **not** swept (it is reachable: tile `D_29 = 214 708 725`, ~60 s for a column to p = 127 — see the next step). - **Not claimed**: no law for the transition primes or the recoveries; nothing about `|Q| ≥ 2`; nothing on route 26's blocked phase fork; no asymptotic statement. The identity this route exists to measure is untouched. ## Files | file | content | |---|---| | `column_profile.py` | the driver: per-level sweep, profile, recolvery count, plateau start | | `profile-1382.out` | the measured columns and the summary table | | `profile-1382.exec.json` | bounded-exec receipt (34.2 s wall, exit 0, group gone) | | `period_check.c` | the instrument, unchanged (recompiled) |