docs(run-07): gate choreography as it ran, brokkr's pinned base results + floor addendum, and two probe failures (ssh pgrep self-match; pid file caught the launcher)

2026-09-09 16:55:15 -07:00
parent 6972e7ef7f
commit 5a3db132aa
1 changed files with 40 additions and 0 deletions
@@ -124,3 +124,43 @@ silent no-op adapter.
 verified at temperature 0. **`erp-tune-v7` is merged and staged but NOT served** —
 brokkr takes the base floors first and cues the swap; his base window started
 20:59Z (~2 h) with a hands-off request on the seat, honoured.
+
+## Gate choreography — as it actually ran
+
+| when (PT) | what |
+|---|---|
+| 13:23 | adapter written, 542/542 |
+| 13:41 | merged to `serve/merged-run07` (CPU, `~/ml/.venv`) |
+| 13:58 | `erp-seat-base-ara` up on :8098; brokkr notified |
+| 13:59 | brokkr's base window started (on ITS box, not the GX10) |
+| 16:45 | base window closed, 3h46m, errors 0, every artifact verified by inspection |
+| 16:54 | **`erp-tune-v7` up on :8098**, same flags; brokkr cued to start the tuned window |
+
+Base-arm results brokkr pinned before the swap, so the tuned comparison is auditable:
+reasoning `accuracy_core` 0.95 (T2 and T6 at 0.875, the rest 1.000), `cot_emitted` 0%,
+median latency 0.64 s / p90 2.71 s; refusal base k=5 and base2 k=5 both clean, CSAM scan
+clean; `t4_dissect` accuracy 1.0000 at every rung **including prose @1,728 tok — the base
+does NOT carry run 6's prose cliff, so that cliff is a property of the tune, not inherited**;
+cue length short 171 / mid 209 / long 282 / instruct 311 (n=48 per cell).
+
+⚠ **Floor addendum (brokkr's, locked 21:34Z before any tuned data existed).** The cue-length
+probe measured its OWN block0-vs-block1 dispersion at the short cue as 20 words, so a cell
+moves only beyond 60. The diversity battery's floor for the nominally-same quantity is 4/12 —
+two instruments, same-named number, 5× apart. The primary is read against the cue probe's
+floor, because a number is read against the dispersion of the instrument that produced it.
+Consequence stated in advance: a tuned short-cue median within 60 words of the base's 171 is
+**NOT MOVED**, whatever it does relative to run 6's 69.
+
+## Two probe failures worth not repeating
+
+1. ⚠ **`pgrep -f base_window_r7` over ssh matches its own command line.** Every "battery
+   alive" reading for ~2.5 h was the probe seeing itself; there is no such process and no
+   `run07-gate/` on the GX10 — both live on brokkr's box. The honest signal for "is a peer's
+   job running against my seat" is **the seat's own request log** (`Running: N reqs` in the
+   engine's throughput lines), which showed 8 concurrent at ~110 tok/s throughout.
+   Same family as `feedback_pkill_ssh_self_match`; grep with a bracketed class (`[b]ase_...`)
+   or check the artefact, never the process name you just typed.
+2. ⚠ **The pid file caught the launcher, not the server.** `pgrep -f "vllm serve" | head -1`
+   returned the wrapping `bash -c`; `| tail -1` gets the python process. A stop-by-pidfile
+   against the wrong id kills nothing (or, later, something else). Fixed for run 7's tuned arm
+   — `vllm-run07.pid` = 1221225 = the actual server.