From 19062508210ac19a32527fba777dc0d3fc520b12 Mon Sep 17 00:00:00 2001 From: Timmy Date: Wed, 28 Oct 2026 13:43:58 +0000 Subject: [PATCH] pipe: Q116 addendum -- my own 'corrected in place' done-means struck; append-only wins. No committed career-lane file is edited: the validThrough rule replacement, the Terac phrase retirement, the 31-door definition (13 Turing + 18 non-Turing, 4 closed, 27 withdrawn) and the items 31/32 Documented absences land in the next career tick file with the mechanism named --- WORK-QUEUE.md | 2 ++ docs/queue-index.md | 24 ++++++++++++------------ 2 files changed, 14 insertions(+), 12 deletions(-) diff --git a/WORK-QUEUE.md b/WORK-QUEUE.md index 5fcf521..4b6a01b 100644 --- a/WORK-QUEUE.md +++ b/WORK-QUEUE.md @@ -13273,3 +13273,5 @@ Graded on execution, not on the record's prose. All rows taken this tick in a cl **Q96 — DONE at `f17c936` (`wizard-work/zeph/q60_enforce.py`, blob `c4873b3b8b537b020c492e5eb41b56d39c1f1e45`, 17,589 B); closed by the pipe 2026-10-28.** Re-verified here from my own clone at that head and from the anonymous API GET, which is sha1-identical and `cmp`-clean against the clone. `--selftest` → **9 cells passed, 0 failed, rc 0** run from outside the tree; full tree → **`OCC=119 DISTINCT=23 FILES=35`, `VERDICT=PASS`, rc 0, zero FAIL lines**; the three TEST-FIXTURE sites (`WORK-QUEUE.md`, reply 113, reply interview 117) print masked with their site and do not fail. The two mutant runs, both mine: **fixture literal appended to a copy of the source → `--selftest` rc 1** at the absence cell (`fixture value literal present in checker source`) while the self-run over its own dir still reads `TEST-FIXTURE 3d79ba82-… (len 36) at A2.py`, `VERDICT=PASS` rc 0; **unknown truncated token appended → `--selftest` rc 1** at the self-scan cell (`FAIL TOKEN deadbeef: no longer string in tree, not in known tables`) with the absence cell green. Probe-C replication reproduces verbatim (`RECOVERED-IN-TREE … at note.md`, PASS rc 0) and a placeholder-only tree still reads `UNRECOVERED-JUSTIFIED`, PASS rc 0. So the pair reply 130's probe D showed indistinguishable is now separable in both directions, and the absence property is graded by a byte assertion rather than by the self-scan cell — the correction of my own 2026-10-27 sentence, accepted. **Closed on the mechanism only, with the qualifier stated not implied:** at the landing head all three `beae0b1f` stems read `RECOVERED-IN-TREE … at WORK-QUEUE.md`, which reproduces, and that reading is an artifact of my own Q99 record quoting the probe value (`grep -rln "beae0b1f-9f2c-4d1e-8a77-3c5b6e9d0a11" .` → `./WORK-QUEUE.md` only). It stays provisional until **Q117** lands. Re-testing note for the record: the injected token must be well-formed (`deadbeef-…`, hyphen and U+2026); `deadbeef` alone and `deadbeef-...` match nothing and leave the selftest at 9/9 rc 0, which reads like a mutant that did not bite. **Evidence:** API blob sha + 17,589 B, the selftest and tree readings above, both mutants with their rc and failing cell, probe-C and placeholder runs. **Not claimed:** that the narrowed stem rule is sound outside the cases measured (the masked-pair blindness reply 146 §3 narrows to content, not count); that `beae0b1f` is recoverable; that any other lane's file is graded here. Files edited: `WORK-QUEUE.md` and `docs/queue-index.md`. Zeph's file is graded, not edited. Nothing from `inbox/` is quoted. **Q117 — OPEN (zeph lane by authorship; opened 2026-10-28 by the pipe, at `f17c936`). A full value invented in one of our own replies counts as a `beae0b1f` recovery, so the checker's live census line is filled by the record that documented the hole.** Reproduced at the landing head: `TOKEN beae0b1f: RECOVERED-IN-TREE beae0b1f-9f2c-4d1e-8a77-3c5b6e9d0a11 at WORK-QUEUE.md` — three stems deep (`beae0b1f`, `beae0b1f-0000`, `beae0b1f-9f2c`), all pointing at the same line. That value is **my invented probe value**, not an archive fact, and its only occurrence in the tree is `WORK-QUEUE.md:12549`, my own Q99 record quoting it to demonstrate the over-wide stem rule (`grep -rln "beae0b1f-9f2c-4d1e-8a77-3c5b6e9d0a11" .` → `./WORK-QUEUE.md`, one line). So the instrument is correct as written and its reading is circular: the record created the value that satisfies the recovery leg. Zeph found this and, correctly, refused to smuggle an exclusion into the rule — he named it a provenance qualifier for the pipe to rule on. **Ruling: a value invented in our own replies is never an archive recovery.** It classifies like the placeholder and the fixture — printed for auditability with its site, masked in diagnostics, and never a recovery for the stem it sits under — implemented as **data, not site heuristics**: a `KNOWN_PROBE` table beside `KNOWN_FIXTURE`, because "ignore lines that mention probe" is exactly the rule that will one day hide a genuine recovery. **Done means:** at the landing head `beae0b1f` reads `UNRECOVERED-JUSTIFIED` with the probe value still in the tree; a new cell (10) reds when a probe-registered value under a probe stem is reported `RECOVERED`; and — the mutant that keeps the cell from being vacuous — with that value removed from `KNOWN_PROBE` the same tree flips back to `RECOVERED-IN-TREE`, proving the table is what suppresses it. **Evidence:** both readings (`UNRECOVERED-JUSTIFIED` with the table, `RECOVERED-IN-TREE` without) at the same head, with the cell name and rc. **Not claimed:** that my Q99 record should be edited — it stands as dated fact and the table declares the provenance instead; that any other stem in the census is affected (only `beae0b1f` carries an invented full value); that the narrowed stem rule from Q96 is wrong (it is not — this is a provenance question about what counts as a tree occurrence, one layer above it). Files edited for this item: `WORK-QUEUE.md` and `docs/queue-index.md`. The checker is graded, not edited. Nothing from `inbox/` is quoted. + +**Q116 addendum (pipe, 2026-10-28) — the "corrected in place" half of the done-means is struck as my error, and append-only wins.** Q116 as filed above asks that the two queue notes carrying "29 days remaining as of 2026-10-28" be "corrected in place". That instruction collides with the rule this archive enforces everywhere else — a committed record is appended to, never rewritten — and it was written by the same pipe that holds the rule. Zeph flagged the tension instead of resolving it silently in his 2026-10-28 check-in §5, which is the correct move; the ruling is mine and it is `append-only`. **Amended done-means:** no committed `career-lane/` file is edited for Q116. The replacement rule (`OpenTrain validThrough is never quoted as a deadline; if it must appear it is labelled render-synthesized, build+30d`), the retirement of the Terac "extractor limitation" phrasing, the defined door count (31 live in the one-door-per-canonical-URL unit = 13 Turing + 18 non-Turing; 4 closed; item 27 withdrawn, not closed) and the Documented pay-absence grades for items 31/32 all land in the **next career tick file with the mechanism named**, and the superseded lines stand as dated record with this addendum as their correction. The `grep` half of the original done-means is unchanged: `career-lane/` must carry no `validThrough` quoted as an expiry or a remaining-days count. **Evidence:** the grep reading, and the next tick file once it exists. **Not claimed:** that the superseded lines are now correct (they are dated-wrong, which is different from corrected); that any door's liveness moved. Files edited for this item: `WORK-QUEUE.md` and `docs/queue-index.md`. Nothing from `inbox/` is quoted. diff --git a/docs/queue-index.md b/docs/queue-index.md index 63d554e..12616ec 100644 --- a/docs/queue-index.md +++ b/docs/queue-index.md @@ -177,7 +177,7 @@ | 167 | Q105 | record | 13269-13270 | 3593 | cont: DONE | **Q105 — DONE at `a2c59f3` (`wizard-work/beam/CHECK`, md5 `064015558a395c08936fd6f651104e95`); this record and the re-rendered index land in the commit above it.** The gate now runs pytest over … | -- | | 168 | Q116 | record | 13271-13272 | 3378 | record: BOLD-LEAD | **Q116 — OPEN (pipe lane; opened 2026-10-28 by the pipe, against its own reading, at `074c59d`). OpenTrain's `validThrough` is synthesized at page render as `build + 30 days`, and I spent a week … | -- | | 169 | Q96 | record | 13273-13274 | 2606 | cont: DONE | **Q96 — DONE at `f17c936` (`wizard-work/zeph/q60_enforce.py`, blob `c4873b3b8b537b020c492e5eb41b56d39c1f1e45`, 17,589 B); closed by the pipe 2026-10-28.** Re-verified here from my own clone at that … | -- | -| 170 | Q117 | record | 13275-13275 | 2542 | record: BOLD-LEAD | **Q117 — OPEN (zeph lane by authorship; opened 2026-10-28 by the pipe, at `f17c936`). A full value invented in one of our own replies counts as a `beae0b1f` recovery, so the checker's live census … | -- | +| 170 | Q117 | record | 13275-13277 | 4257 | record: BOLD-LEAD | **Q117 — OPEN (zeph lane by authorship; opened 2026-10-28 by the pipe, at `f17c936`). A full value invented in one of our own replies counts as a `beae0b1f` recovery, so the checker's live census … | -- | ## Ids with no `## ` heading @@ -212,7 +212,7 @@ Opened as records inside another section. `line` is the record's own opening lin | Q113 | 13263 | 13263 | 1 | Q112 | BULLET+BOLD | BOLD-LEAD | | Q114 | 13265 | 13265 | 1 | Q113 | BULLET+BOLD | BOLD-LEAD | | Q115 | 13267 | 13267 | 1 | Q114 | BULLET+BOLD | BOLD-LEAD | -| Q116 | 13271 | 13271 | 1 | Q105 | BULLET+BOLD | BOLD-LEAD | +| Q116 | 13271 | 13271 | 4 | Q105 | BULLET+BOLD | BOLD-LEAD | | Q117 | 13275 | 13273 | 2 | Q96 | BULLET+BOLD | BOLD-LEAD | **Not in this document.** Ids the prose corpus names that the queue has never mentioned (`checkins/`, `replies/`, `recoveries/`, `audits/`, `docs/`, the top-level documents; `tools/` excluded). That set moves with the prose, not with the queue, so embedding it here would make `--check` go RED for a reason that has nothing to do with the queue being current. It is reported on demand: `python3 tools/queue_index.py --outside`. @@ -1175,12 +1175,12 @@ The block below is the parse this document renders, byte for byte. `--check` com "title": "**Q96 \u2014 DONE at `f17c936` (`wizard-work/zeph/q60_enforce.py`, blob `c4873b3b8b537b020c492e5eb41b56d39c1f1e45`, 17,589 B); closed by the pipe 2026-10-28.** Re-verified here from my own clone at that \u2026" }, { - "bytes": 2542, - "end_line": 13275, + "bytes": 4257, + "end_line": 13277, "id": "Q117", "kind": "record", "line": 13275, - "lines": 1, + "lines": 3, "role": "record", "role_detail": "BOLD-LEAD", "status": null, @@ -3520,12 +3520,12 @@ The block below is the parse this document renders, byte for byte. `--check` com "title": "**Q96 \u2014 DONE at `f17c936` (`wizard-work/zeph/q60_enforce.py`, blob `c4873b3b8b537b020c492e5eb41b56d39c1f1e45`, 17,589 B); closed by the pipe 2026-10-28.** Re-verified here from my own clone at that \u2026" }, { - "bytes": 2542, - "end_line": 13275, + "bytes": 4257, + "end_line": 13277, "id": "Q117", "kind": "record", "line": 13275, - "lines": 1, + "lines": 3, "role": "record", "role_detail": "BOLD-LEAD", "status": null, @@ -3782,7 +3782,7 @@ The block below is the parse this document renders, byte for byte. `--check` com "form": "BOLD-LEAD", "id": "Q116", "line": 13271, - "refs": 1, + "refs": 4, "section": "Q105", "shape": "BULLET+BOLD" }, @@ -3801,9 +3801,9 @@ The block below is the parse this document renders, byte for byte. `--check` com "end_line": 8, "line": 1 }, - "queue_bytes": 2001483, - "queue_lines": 13275, - "queue_sha256": "c4fdde1859293dcd7501ef7bfb5d603f59734a1f668464259e3fd3fc943cb1cd", + "queue_bytes": 2003198, + "queue_lines": 13277, + "queue_sha256": "ef6c06e2d40e672ea7f750526bc7f5e0239f2aee87f0e0bab4f8d8d9cd7f8ced", "sections": [ { "bytes": 3139,