queue: open Q58 (sol lane) -- the lane-activity instrument reads the flat log surface retired on 2026-10-16, so all seven lanes read STALE on a day every one of them wrote; record the four-commit verification pass; index re-rendered

WORK-QUEUE.md

@@ -10727,3 +10727,49 @@ Artifact `/root/.hermes/wizard-outputs/volt/2026-10-23-manifests/` — `REPORT.m
 Artifact `/root/.hermes/wizard-outputs/volt/2026-10-24-guide-recheck/` — `REPORT.md`, `recheck.sh`, `crawl.sh`, `sections.sh`, `quotecheck.py`, `check.sh`, four transcripts, the fetched bytes under `work/` (index, entry page, article, 121 pages), and a `files.sha256` over its own 142 files; `bash check.sh` → **59 checks, 59 passed, 0 failed**, `CHECK: PASS`, rc 0.
 
 — Volt
+
+---
+
+## Q58 — The lane-activity instrument reads a surface that was retired on 2026-10-16 *(Sol lane; opened 2026-10-24 by the pipe, per reply 12 to sol)*
+
+`wizard-work/sol/daily-ledger-triage-2026-10-24.json` (commit `a916aea`, generated
+`2026-10-24T07:58:24Z`) reports **all seven lanes STALE**, ages 185.04–185.19 h, and the
+commit message carries that headline. The ages are arithmetically correct and the
+conclusion is false. `triage_gen_daily.py` selects each lane's candidate set with
+`glob(os.path.join(BASE, pid + "*-*.txt"))` — the flat `<lane>-YYYY-MM-DD-HHMM.txt` series
+at the top of `/root/.hermes/wizard-outputs`. Every one of those seven series ends at
+`2026-10-16T14:4x–14:56` (56 files per lane, all seven), and since then the lanes write
+inside `BASE/<lane>/`. Measured from this host 2026-10-24 08:4x–08:5xZ: files mtime'd today
+per lane read forge 22, ledger 13, null 11, quill 3, sphinx 68, sol 10, spark 5; newest per
+lane reads forge 08:05, ledger 08:01, sol 07:58, spark 07:55, quill 07:54, null 05:22,
+sphinx 05:14. Four of the seven lanes pushed commits to this branch at 07:54:57, 07:55:43,
+07:59:30 and 08:01:18 — before the triage's own timestamp. Two secondary defects in the same
+artifact: the docstring names `triage_check.py` as the source of the seven lane ids, and that
+file (`wizard-work/sol/triage_check.py`) grades `wizard-work/` completion markers and names
+none of them; and the generator hardcodes `triage-daily-2026-10-22` in its output paths and
+Markdown title while the artifact is committed as `-2026-10-24`.
+
+**Status: open and unclaimed. Opened by the pipe 2026-10-24; sol's lane.**
+
+**Done means:** the triage reads **both** surfaces (legacy flat files and `BASE/<lane>/`),
+names for every lane the surface each row was read from, and reports the newest artefact per
+lane instead of the newest filename matching one pattern — so that today's tree reads
+**seven ACTIVE**, with `forge`'s newest artefact at 08:05 rather than 14:56 eight days ago;
+the lane-id provenance either cites a file that actually names the seven ids or is dropped;
+and the output paths carry the run's own date.
+**Evidence:** the before/after rows for all seven lanes with the surface named per row; a
+negative control in which a lane with an empty directory and no flat files still reads
+STALE rather than inheriting another surface's age; and `generated_utc` matching the date
+in the committed filename.
+
+---
+
+**Verification 2026-10-24 (timmy, control plane) — four trove commits read and re-measured: sol's seven-lane STALE headline is false against a surface retired on 10-16 (Q58 opened); ledger's GDP table corroborates 11/11 against the IMF's own API, retiring its seven `verified: false` flags; spark's 4/4 discriminates (3 failed / 1 passed under a doctored validator); quill's CHECK exits 0 on a byte-identical copy.** No item closed. The open set is now `Q37` (pipe span), `Q53` and `Q64` (Alexander's), `Q57` (null's lane) and `Q58` (sol's lane, opened here). Nothing in this record decides anything Alexander holds.
+
+1. **`a916aea` — sol's triage, corrected.** Full measurement in reply 12 (`replies/2026-10-24-to-sol-12.md`): the selector, the 56-file flat series ending 10-16, per-lane counts and mtimes today, and the four lane commits that landed before the triage's own clock. Secondary: the cited `triage_check.py` does not name the seven ids, and the generator's hardcoded `2026-10-22` disagrees with the committed `-2026-10-24` name.
+
+2. **`37ab2ef` — ledger's GDP table, upgraded to Corroborated.** Live page re-fetch 200 / 681,612 B, revision `2026-10-21T18:05:22Z`, all eleven rows byte-identical; IMF DataMapper `NGDPD` returns all eleven 2026 cells exact to the unit (World `WEOWORLD` 128,003.776 bn → 128,003,776 mn; USA 32,642.373; CHN 21,546.403; DEU 5,471.299; JPN 4,341.986; GBR 4,268.446; IND 4,060.207; FRA 3,554.155; RUS 2,861.156; ITA 2,701.737; BRA 2,654.761), which supersedes the artifact's `verified_against_live_page: false` on ranks 4–10. World Bank primary **Unrecovered**: `api.worldbank.org` timed out twice from this host (25 s, 0 bytes), so the WB 2025 and UN 2024 columns stay Documented-via-Wikipedia. Detail: `replies/2026-10-24-to-ledger-15.md`.
+
+3. **`c72e1de` — spark's validator, 4/4 reproduced and shown to discriminate.** Committed run: 4 passed, 4 warnings. Deployed copy byte-identical to the commit (validator `ff2ef12d…`, tests `58db24c5…`). Mutation control on a scratch copy (`"valid": True` by default) → **3 failed, 1 passed**, the three failing cells being exactly the three that assert a failure. Logged in the reply as my own first control was a no-op (`sys.exit(1)` at line 47 is the usage path; the exit is `exit_code` at line 67). Detail: `replies/2026-10-24-to-spark-19.md`.
+
+4. **`8385881` — quill's template, CHECK green.** The CHECK line as written exits 0; the path it checks holds the committed bytes (`08efb00b…`); 196 words against a "~200" claim. What it cannot grade is the template's own "every claim measured" scope line — its four cells test existence, not claims — and its CHECK hardcodes a host path a reader of the repository cannot run. Detail: `replies/2026-10-24-to-quill-04.md`.

docs/queue-index.md

@@ -4,7 +4,7 @@
 
 **What this is.** One row per `## ` section of `WORK-QUEUE.md`: its line span, its size, and the first `Status:` marker in its body verbatim. Whether an item is *open* is not decided here -- that verdict is `tools/queue_claim_check.py`'s, and this document does not overrule it.
 
-**What it exposes.** The queue is two-tier. 50 sections carry 46 ids because 4 ids own a second, continuation section. A further **10 ids have no heading at all** and are opened as records nested inside another item's section -- so grepping `^## Q41` finds nothing while Q41 is a live item the file names 28 times. Those are listed in their own table below.
+**What it exposes.** The queue is two-tier. 51 sections carry 47 ids because 4 ids own a second, continuation section. A further **10 ids have no heading at all** and are opened as records nested inside another item's section -- so grepping `^## Q41` finds nothing while Q41 is a live item the file names 28 times. Those are listed in their own table below.
 
 | # | id | lines | bytes | role | title | first `Status:` |
 |---|---|---|---|---|---|---|
@@ -57,7 +57,8 @@
 | 47 | Q48 | 6706-6825 | 15123 | opening | The runtime-resolution redirect: close the class Q45's literals cannot see | DONE 2026-10-13 — `recoveries/helm-runtime-redirect.md` (Merlin, Helm lane), scratch tree |
 | 48 | Q49 | 6826-7593 | 92050 | opening | The runtime-resolved root's live write path: name it, reproduce it, then close it | open and unclaimed. Opened by the pipe 2026-10-13 |
 | 49 | Q45 | 7594-10699 | 572535 | opening | §9 follow-on — the home-directory channel *(Helm lane; Merlin)* | OPEN — awaiting Alexander's zoom/whole-shop answer; build is the pipe's. |
-| 50 | Q57 | 10700-10729 | 8726 | opening | Bind a standup entry to the bytes it grades *(Codeforge lane; opened 2026-10-24 by the pipe, per reply 05's corrections 1 and 2)* | open and unclaimed. Opened by the pipe 2026-10-24; null's lane. |
+| 50 | Q57 | 10700-10732 | 8732 | opening | Bind a standup entry to the bytes it grades *(Codeforge lane; opened 2026-10-24 by the pipe, per reply 05's corrections 1 and 2)* | open and unclaimed. Opened by the pipe 2026-10-24; null's lane. |
+| 51 | Q58 | 10733-10775 | 5224 | opening | The lane-activity instrument reads a surface that was retired on 2026-10-16 *(Sol lane; opened 2026-10-24 by the pipe, per reply 12 to sol)* | open and unclaimed. Opened by the pipe 2026-10-24; sol's lane. |
 
 ## Ids with no `## ` heading
 
@@ -72,9 +73,9 @@ Opened as records inside another section. `line` is the record's own opening lin
 | Q50 | 6990 | 6990 | 46 | Q49 | BULLET+BOLD | BOLD-LEAD |
 | Q51 | 7106 | 7106 | 37 | Q49 | BULLET+BOLD | BOLD-LEAD |
 | Q52 | 7167 | 7167 | 90 | Q49 | BULLET+BOLD | BOLD-LEAD |
-| Q53 | 7292 | 7246 | 160 | Q49 | BULLET+BOLD | BOLD-LEAD |
+| Q53 | 7292 | 7246 | 161 | Q49 | BULLET+BOLD | BOLD-LEAD |
 | Q63 | 9918 | 9909 | 17 | Q45 | BULLET+BOLD | BOLD-LEAD |
-| Q64 | 10308 | 10308 | 23 | Q45 | BULLET+BOLD | BOLD-LEAD |
+| Q64 | 10308 | 10308 | 24 | Q45 | 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`.
 
@@ -149,7 +150,8 @@ The block below is the parse this document renders, byte for byte. `--check` com
   "Q45",
   "Q48",
   "Q49",
-  "Q57"
+  "Q57",
+  "Q58"
  ],
  "nested": [
   {
@@ -220,7 +222,7 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "form": "BOLD-LEAD",
    "id": "Q53",
    "line": 7292,
-   "refs": 160,
+   "refs": 161,
    "section": "Q49",
    "shape": "BULLET+BOLD"
   },
@@ -238,7 +240,7 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "form": "BOLD-LEAD",
    "id": "Q64",
    "line": 10308,
-   "refs": 23,
+   "refs": 24,
    "section": "Q45",
    "shape": "BULLET+BOLD"
   }
@@ -248,9 +250,9 @@ The block below is the parse this document renders, byte for byte. `--check` com
   "end_line": 8,
   "line": 1
  },
- "queue_bytes": 1473522,
- "queue_lines": 10729,
- "queue_sha256": "5037cfc76e1ec245aeeaf737feb1d243da54a9e22263d78f8d11cd784698beb2",
+ "queue_bytes": 1478752,
+ "queue_lines": 10775,
+ "queue_sha256": "dc6dcfc53f57c1141311bf78b9b23da1742389690b32f15070b7382dbdf4cf5e",
  "sections": [
   {
    "bytes": 3139,
@@ -841,16 +843,28 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "title": "\u00a79 follow-on \u2014 the home-directory channel *(Helm lane; Merlin)*"
   },
   {
-   "bytes": 8726,
-   "end_line": 10729,
+   "bytes": 8732,
+   "end_line": 10732,
    "id": "Q57",
    "line": 10700,
-   "lines": 30,
+   "lines": 33,
    "role": "opening",
    "role_detail": "",
    "status": "open and unclaimed. Opened by the pipe 2026-10-24; null's lane.",
    "status_line": 10704,
    "title": "Bind a standup entry to the bytes it grades *(Codeforge lane; opened 2026-10-24 by the pipe, per reply 05's corrections 1 and 2)*"
+  },
+  {
+   "bytes": 5224,
+   "end_line": 10775,
+   "id": "Q58",
+   "line": 10733,
+   "lines": 43,
+   "role": "opening",
+   "role_detail": "",
+   "status": "open and unclaimed. Opened by the pipe 2026-10-24; sol's lane.",
+   "status_line": 10752,
+   "title": "The lane-activity instrument reads a surface that was retired on 2026-10-16 *(Sol lane; opened 2026-10-24 by the pipe, per reply 12 to sol)*"
   }
  ]
 }