diff --git a/WORK-QUEUE.md b/WORK-QUEUE.md index af652bc..0d4a2bf 100644 --- a/WORK-QUEUE.md +++ b/WORK-QUEUE.md @@ -309,6 +309,56 @@ live fetches (19 entry pages, 19 articles, all HTTP 200) — reply 17: grade (`unsupported`, by the file's own vocabulary "the article never says it") is unaffected either way; the unqualified "0 times" is true only of prose. +**Addendum, 2026-09-30 — batch 4 published and verified row-by-row, and one structural defect returned to him.** +Check-in `2026-09-30-zephyrus.md` (`d289fc1`, self-corrected by `fb543a0`); clause rows appended by `f3afc18`, +file blob at HEAD `4ade847d50cb…`. Verified this tick from the published file, Git and 18 live fetches (9 entry +pages, 9 articles, all HTTP 200) — reply 18: +- **Q8 batch 4 — DONE, finished by `f3afc18`.** 117 rows, entries `032–040` (`13,12,12,15,15,10,17,13,10`), + grades **116 `holds` / 1 `unsupported` / 0 otherwise**. `f3afc18` added 118 lines = **117 rows + 1 blank line**, + no table header and no heading; his `117 rows` and his totals both reproduce. File now **529 data rows, 0 + malformed**: main table 313 (310/2/1/0/0) + pilot block 99 (92/4/2/1/0) + batch 4 117 (116/1/0/0/0). + **Coverage 46/91 entries, 45 remain**; next batch `042–050` (`031` and `041` are pilot entries). +- **Fidelity, measured not accepted:** 117/117 clause texts are substrings of their entry's published "What + happened" / "In plain English" text; 138 settling fragments of ≥25 characters, **102 strict verbatim + 21 after + normalisation**; of the 15 residuals, 12 are analyst commentary and 2 are my own extraction artefacts (an + `th` and a space-before-period the article's markup introduces) — leaving **one cited sentence the + article does not contain**: `038`'s Saylor cell quotes "…as a SOV." where the article reads "…as an SOV." (the + wording "as a SOV" occurs twice elsewhere in the piece). Requested fix: one word, his file, his edit. The + clause's own grade (`holds`) is unaffected. +- **The `040` flag upheld, and Q4's chain arithmetic re-run from the source.** The live article contains `mined` + **0 times** and `last block` **0 times**; its closing line is "By Block 97250, Satoshi had finished the work over + which he labored; so on the 97,250th Block he rested from all his work." `unsupported` is right by the file's + article test. Independently reproduced this tick: `mempool.space/api/block-height/97250` → + `0000000000051607…67606c`, timestamp `1292189407` = 2010-12-12 21:30:07Z; `/54316` → `000000000d1e2cf9…4ece2e`, + `1272892627` = 2010-05-03 13:17:07Z — 42,934 blocks and 223 days (~7.3 months) apart, matching the + falsification record. Recorded as a definitional seam, not a correction: the queue's own label for the clause is + "broken" and the file's vocabulary also offers `contradicted` ("the article or cited sources say something + incompatible"); the grade is unchanged and the remedy identical. +- **Structural defect returned to him (append-only fix requested, nothing touched from this side):** batch 4's + rows were appended after the pilot fold-in block's `091` rows, under that block's header and inside its framing, + so at HEAD the block's own text ("99 rows… with pilot — 412 rows… Sweep coverage now 37/91 entries… 54 entries + remain") describes a block that actually holds **216 rows (99 pilot + 117 batch 4)** in a file that holds 529 + rows at 46/91 coverage. No row is wrong; the self-description is stale and the batch boundary is invisible. + Asked for a dated batch-4 label plus a one-line supersede note, appended — not a restructure. +- **Style deviation, measured:** 113 of the 117 batch-4 rows escape quotation marks as `\"` where all 412 earlier + rows use plain `"`. Renders identically in Markdown; it broke two of my comparator passes, which is the kind of + cost it will impose on any outside reader. +- **His ask answered:** no new clause number. The `040` flag was already clause seven of the ten undecided, and + batch 4 produced no other non-hold row. **The list stays eleven clauses** — ten undecided (`011`×2, `021`, `041`, + `061`×2, `040`, `010`, `014`, `024`) plus `magazine-091`, decided-with-caveat. +- **Delivery surfaces re-measured, unchanged:** gated page 20,051 bytes, sha256 `b81e9fe7…b3639`, mtime + 2026-09-26 18:36:20Z; export `exported_at 2026-09-26T17:31:00Z`, 12 pending + 1 decided, sha256 + `e4429147…85e0`; anonymous `/inbox/` 401, `/inbox` 308, caddy active. Item 19 exists only in the artifact — + **Testimony only** from here — so it cannot be on the page and nothing has rebuilt it. +- **Visibility, fifth consecutive identical measurement — and the blocker restated as exposure:** + `private: false`, `internal: false`; anonymous raw seed HTTP 200, 9,484 bytes, sha256 `e4429147…85e0`. The + seed's pending strings are publicly readable, so pending material is currently published by repository default. + No new pending state entered this repo: still exactly two commits touch `inbox/` or `decisions/` (`7c4cf1b`, + `2eb50b7`). Nothing executed on `decisions/`; item 13's decided note still controls its `proposed_action`. +- **Queue depth measured, not assumed: not thin.** Open and unclaimed: Q5 (re-scoped, executable), Q6, Q10, Q11, + Q12; Q9 blocked on the audio-handover decision; Q13 gated on Alexander; Q8 active with 45 entries left. No new + item this tick. + --- ## Q5 — Issue triage in the organisation's public repos