Triage of route 151 (= return #1569, authored by THIS session; the department assigned the triage and that fact is stated rather than hidden). The triage's contribution is the cheapest question the route never asked: **does the RECORD already decide R = 310?** A witness whose covered run is L positions translates to a certificate at prefix L (its covered set moved to the origin), so a recorded run of 310 would decide R = 310 and lift the bound to 6*310+5 = 1865 with no search at all. Measured over every witness certificate the corpus recorded -- the 22-row survey served by return #1569 (`run-supremacy.json`, independently re-derived by `verify-run-supremacy.py`: PASS, 3 controls): * **supremum run 309**, achieved by exactly ONE row: the return #1554 certificate at rung 307, covering `[-2,306]` -- the record's best is the certificate already in hand; * **second best 291** (the rung-285 witness), then 201, 201, 186 -- a cliff, so the supremum is not an artefact of one odd row; * **rows reaching 310: NONE.** So the route's proposed experiment is **not redundant** with the record, and its target is exactly **one position beyond the best run the record holds**: the record's free bound is A >= 6*309+5 = **1859**, the target bound is **1865**. Price, unchanged by this triage: the R = 307 witness was in hand at t = 14,454 s of the rung (8 threads => ~32 CPU h) against the assignment's 4 CPU h ceiling, so the route's next step is the right INSTRUMENT (early-abort build, acceptance stated on the covered run) but its `seeded from the R = 307 certificate` clause is an **unevidenced cost assumption** -- a witness is not a starting point for the next rung's search -- and belongs dropped or tested, not priced in. Two further readings this triage fixes on the record: the route's price line was read off one translate's printed prefix, while the decidable quantity is the covered run; and the same 22-row measurement is what shows 15 of 22 witnesses overshoot their printed rung, so the correction is not a one-off. What the triage does NOT change: the certificate's arithmetic (already independently verified by return #1569), the answered R = 308 decision, or the 1859 banked bound. **R = 310 remains open** -- this triage shows only that the record cannot settle it.