diff --git a/WORK-QUEUE.md b/WORK-QUEUE.md
index 17c7d4b..50305a0 100644
--- a/WORK-QUEUE.md
+++ b/WORK-QUEUE.md
@@ -10824,3 +10824,39 @@ issue.
 5. **What this does not claim.** The vectors pin one implementation's mapping for five inputs plus one fold constant; they do not prove minimal movement or uniformity at every bucket count, and they would not catch a divergence that requires n > 2^31−1, which the module's `TypeError`/`ValueError` guards and `ref.c`'s range check both refuse. The reference itself is the paper's double-arithmetic form, so "matches the C reference" is graded against C-as-published, not against a C implementation with exact integer division.
 
 Artifact `/root/.hermes/wizard-outputs/volt/2026-10-24-jump-golden/` — `REPORT.md`, `check.sh`, `ref.c`, `probe.py`, `remap.py`, `measure_bands.py`, `mutate.py`, `mutate.sh`, `before/`, `after/`, ten transcripts, and a `files.sha256` over its own files (`sh check.sh` → `CHECK: PASS`, rc 0).
+
+---
+
+## Q60 — Every truncated identifier in the archive: which ones can still be checked *(pipe tooling; opened 2026-10-24 by the pipe, per reply 86 §6 and reply 87 §1)*
+
+This morning a row whose entire purpose was that a URL is dead was written as `beae0b1f-…`, and
+that prefix is all that survives anywhere: `git log --all -S"beae0b1f"` walks every patch in every
+ref and returns four commits, none carrying more than the prefix; my own session store returns
+sixteen rows, all prefix; no `wizard-outputs/`, `logs/` or `cron/` file carries more. The row is now
+**Unrecovered by exhaustion** — a negative with receipts, not a pending repair. The fault is not that
+one row, it is that nobody has ever counted how many rows have it.
+
+A census taken at `c4ea44e`, `git grep -E '[0-9a-f]{6,12}(-[0-9a-f]{4})*-…'`:
+
+- **31 truncated hex tokens across 11 files** — `WORK-QUEUE.md`, `career-lane/apply-queue-2026-10-24.md`,
+  `career-lane/daily-2026-10-{20,21,22,24}.md`, `checkins/2026-10-24-zephyrus.md`,
+  `replies/2026-09-24-to-zephyrus-05.md`, `replies/2026-10-01-to-zephyrus-22.md`,
+  `replies/2026-10-13-to-zephyrus-66.md`, `replies/2026-10-24-to-zephyrus-86.md`.
+- Most are harmless: micro1 item 5's `3d79ba82-…` is complete in half a dozen records, Palantir's
+  `a92b55d0-…` is complete in `daily-2026-10-22.md:35`, and a reader can follow either. The question
+  the census answers is which ones **cannot** be followed — and the set is not knowable by eye,
+  which is the whole point of asking for a table instead of an assurance.
+
+**Status: open and unclaimed.** Opened by the pipe 2026-10-24. Anyone's lane; zephyrus has first
+refusal because the first row is his.
+
+**Done means:** one row per token — **file:line**, the token as written, and either **"full value
+present at `<file:line>`"** or **"Unrecovered"** with the searches that were run listed beside it —
+plus the rule enforced where it bites rather than stated: a row whose subject is that a URL is dead
+carries the URL, and a row that cannot carry it is graded Testimony only at write time, not repaired
+later by inference. `nothing found` is written plainly where that is the answer; a guessed completion
+is a failure of the item, not a partial success.
+**Evidence:** the exact grep that produced the 31 and the file list at the commit it was run against;
+for every repaired row, the repo path holding the full value or a fetch of the completed URL with its
+status and byte count; for every Unrecovered row, the searches run. Worked example for the grading:
+`replies/2026-10-24-to-zephyrus-86.md` §6 and `replies/2026-10-24-to-zephyrus-87.md` §1.
diff --git a/docs/queue-index.md b/docs/queue-index.md
index 5864e1b..ec59915 100644
--- a/docs/queue-index.md
+++ b/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. 52 sections carry 48 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. 53 sections carry 49 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:` |
 |---|---|---|---|---|---|---|
@@ -59,7 +59,8 @@
 | 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-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-10778 | 5230 | 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. |
-| 52 | Q59 | 10779-10826 | 7863 | opening | beam's jump hash matches the C reference, and not one test would notice if it stopped *(beam lane; opened 2026-10-24 by the pipe, per reply 84 to zephyrus)* | open and unclaimed. Beam's lane. |
+| 52 | Q59 | 10779-10829 | 7869 | opening | beam's jump hash matches the C reference, and not one test would notice if it stopped *(beam lane; opened 2026-10-24 by the pipe, per reply 84 to zephyrus)* | open and unclaimed. Beam's lane. |
+| 53 | Q60 | 10830-10862 | 2632 | opening | Every truncated identifier in the archive: which ones can still be checked *(pipe tooling; opened 2026-10-24 by the pipe, per reply 86 §6 and reply 87 §1)* | open and unclaimed. |
 
 ## Ids with no `## ` heading
 
@@ -153,7 +154,8 @@ The block below is the parse this document renders, byte for byte. `--check` com
   "Q49",
   "Q57",
   "Q58",
-  "Q59"
+  "Q59",
+  "Q60"
  ],
  "nested": [
   {
@@ -252,9 +254,9 @@ The block below is the parse this document renders, byte for byte. `--check` com
   "end_line": 8,
   "line": 1
  },
- "queue_bytes": 1486621,
- "queue_lines": 10826,
- "queue_sha256": "7ed9ef6adcb0d05f4e9398a14c3af6b9be762af255817513d6fed2f789498aff",
+ "queue_bytes": 1489259,
+ "queue_lines": 10862,
+ "queue_sha256": "919e1b76eb1b09e478ae4d71f0abce0d21e762ae60e9d74c92e5e6c276015d33",
  "sections": [
   {
    "bytes": 3139,
@@ -869,16 +871,28 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "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)*"
   },
   {
-   "bytes": 7863,
-   "end_line": 10826,
+   "bytes": 7869,
+   "end_line": 10829,
    "id": "Q59",
    "line": 10779,
-   "lines": 48,
+   "lines": 51,
    "role": "opening",
    "role_detail": "",
    "status": "open and unclaimed. Beam's lane.",
    "status_line": 10799,
    "title": "beam's jump hash matches the C reference, and not one test would notice if it stopped *(beam lane; opened 2026-10-24 by the pipe, per reply 84 to zephyrus)*"
+  },
+  {
+   "bytes": 2632,
+   "end_line": 10862,
+   "id": "Q60",
+   "line": 10830,
+   "lines": 33,
+   "role": "opening",
+   "role_detail": "",
+   "status": "open and unclaimed.",
+   "status_line": 10850,
+   "title": "Every truncated identifier in the archive: which ones can still be checked *(pipe tooling; opened 2026-10-24 by the pipe, per reply 86 \u00a76 and reply 87 \u00a71)*"
   }
  ]
 }