# Job #1383 — the T29 column at sampled primes: the plateau reproduces, and my own six-point trend does not Route 27 (infinitude lane), pursue, budget 0.5 h, compute hint 0.25 CPU-h. Attempt `44f96d21354f6d99df9d808b4cc528d3`. Compute used **414 s wall = 0.115 CPU-h** under bounded exec (exit 0, `timed_out false`, process group gone). ## What was asked The #618 next step: sweep the **largest reachable level (29)** with `period_check.c` unchanged for a seventh point on the plateau-start ladder `11, 23, 37, 59, 71, 107` (levels 5/11/13/17/19/23), whose ratio to its level grew monotonically over those six points (2.2, 2.09, 2.85, 3.47, 3.74, 4.65), and see whether a recovery appears at the largest level. A **full** column to `p = 131` at level 29 costs ≈ 18 min (each invocation re-sieves the 6.47e9-position tile: ≈ 12 s, plus `p × 0.4 s` of block scan), i.e. more than the 0.25 CPU-h offered; so the column was **sampled** at nine primes chosen to bracket its structure: 31, 37, 41, 61, 101, 109, 113, 127, 131. ## Result — the sampled column | p | 31 | 37 | 41 | 61 | 101 | 109 | 113 | 127 | 131 | |---|---|---|---|---|---|---|---|---|---| | `K*({p})` | **4** | **3** | 2 | 2 | 2 | 2 | 2 | **1** | **1** | - **The plateau start at `p = 127` reproduces #161's published T29 transition** ("reads 1 from p = 127"), now measured at the sampled points on this return's own run, and consistent with the diagonal entry `K*({31}) = 4` and the `3` at `p = 37` reproduced in #1377/#616. - **No recovery among the samples**: 4 → 3 → 2 → … → 1 is monotone non-increasing. (Sampling cannot rule out a dip *between* samples — stated, not glossed; what it does establish is that the column does not *rise* at any of the nine sampled primes.) - **My own six-point trend does not extend, and this return refutes it.** `127/29 = 4.38` is *below* T23's 4.65 (and below any level-29 prediction from a monotone ratio ≥ 4.65, which would need `p ≥ 135`). So the plateau/level ratio is **not** monotone in the level: the six-point increase of #618 was small-level behaviour, exactly the "failure" branch that next step named. Corrected statement: the ratio is ~2–4.7 across levels 5–23 and **4.38 at level 29** — the trend reverses at the largest reachable level, so no monotone law should be quoted from the six points. ## Method, cost and what is not claimed - **Instrument unchanged** (`period_check.c`, full period = the phase-max object); driver `t29_column.py` only tabulates. Per-prime wall times 25–67 s, dominated by the tile re-sieve (unavoidable without touching the shipped source — which this route's discipline forbids mid-claim). - **Cost discipline**: the sample set was chosen so the run fits the 0.25 CPU-h hint (it used 0.115); the full column at level 29 (≈ 18 min) and any **two-class** column at level 29 (`∏Q = 31·37 = 1147` blocks × 214.7M slots ≈ 500 s for a single prime) are both out of budget for this assignment and were not attempted. - **Not claimed**: no law for the plateau starts; nothing about `|Q| ≥ 2`; no claim that the column is monotone between samples; nothing on route 26's blocked phase fork; no asymptotics. - **Framework notes (honest).** (a) This job's claim message went to the `formalize` channel because the assignment's `research_route_id` arrives as a **string**, so the lane test `== 27` failed and defaulted; the completion message goes to `infinitude` — cosmetically wrong lane on one message, no effect on the return. (b) The platform content-lint flagged the driver for printing per-prime wall times to **stdout** (a shipped artifact must reproduce byte for byte). Fixed before submission: the timings now go to stderr, and the artifact was regenerated from this same run's captured stdout with only the nine timing parentheticals removed — no measured `K*` value was re-run or changed, and the bounded-exec receipt `t29-1383.exec.json` still holds the original stream verbatim. ## Files | file | content | |---|---| | `t29_column.py` | the sampled-sweep driver | | `t29-1383.out` | the measured samples and the derived statistics | | `t29-1383.exec.json` | bounded-exec receipt (414 s wall, exit 0, not timed out, group gone) | | `period_check.c` | the instrument, unchanged |