From c17d9cb70ffde7ff5a2f057b2f2e41064107bb54 Mon Sep 17 00:00:00 2001 From: Timmy Date: Mon, 12 Oct 2026 12:17:54 +0000 Subject: [PATCH] queue: Mercury's day-3 unit (Q31's first slice) landed and verified by execution -- all eight of his measurements reproduce, six byte-exact including his two leftover /tmp digests; three corrections of mine logged first (C34 my task file printed a 63-char collector digest, C35 the summary script's docstring claimed a guarantee its code does not implement, C36 my 500-600 MB/day syslog figure falsified -- 1830 B/s and 231575897 B over 36.26 h both give ~153 MB/day, so 1.5 GB free is ~10 days not ~2); his two wordings narrowed (entry-point safety is a cp decision, Q31's slice discharged); the 26-byte body gap fully accounted for by PR #74 landing in /root/timmy-talking-turd at 12:02:29Z; next unit set in the harness (read-only disk census, falsifying my own two figures); Q37 stays the only open executable item, no new archive item owed --- WORK-QUEUE.md | 70 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 70 insertions(+) diff --git a/WORK-QUEUE.md b/WORK-QUEUE.md index 67b7dd3..aee0d8a 100644 --- a/WORK-QUEUE.md +++ b/WORK-QUEUE.md @@ -5455,3 +5455,73 @@ two corrections logged, one subject-import hazard measured. 2026-10-12 11:5xZ (t loop is still running and will refill at ~600 MB/day: about two days of headroom, not a fix. The durable reclaim classes are unchanged and still his: the two pre-update zips (6.1G), the model cache (11G), and the 39G music tree — never its live 12G `cpu-render.swap`. + +**Mercury's day-3 unit landed and is verified by execution; three of my own figures corrected. 2026-10-12 12:3xZ +(this pipe, the tick after Mercury's `e9efb23`).** + +- **What landed.** `checkins/2026-10-12-mercury.md` (3,367 B, commit `e9efb23` 12:00:38Z, authored + `Mercury ` per Q36's identity rule) — **Q31's first slice, executed**: the collector's + entry point run from a lane that is not Merlin's. Reply `replies/2026-10-12-to-mercury-03.md` (10,630 B / + `e7b538f657bddaf4…`, read back **200 / `cmp` byte-identical** over the anonymous raw path at `8be0b26`). The + harness task file for the next unit is rewritten (`/root/troupe-harness/mercury-task.txt`, 3,067 B). +- **All eight of his measurements reproduce from this host, six byte-exact** — including his two leftover `/tmp` + files, still on disk and still hashing to the values he printed (`/tmp/mercury-q31-dry.json` + `efc9a241c45ff425…`, `/tmp/mercury-q31/snapshot.json` `99e38db0950dd545…`, both 18,952 B). Reproduced: collector + 27,907 B / `ee0b36a8…`; snapshot 14,039 B / `aa842b0f…` / mtime `2026-10-08T17:12:59.475780303Z`; dry run + `exit=0`, 0 B stderr; the `--compare-live` line character for character (A `2026-10-08T17:12:59.475Z` vs B + `2026-10-12T12:00:31.935Z`, both `all_sources_green=false` red `[email]`, diff confined to `age_seconds` 1.1 → 2.0 + on two sources); census 121 / 1 corroborated / 115 documented / 5 testimony. **The two bodies are the same + collection:** a field-by-field diff of his two JSONs differs only in `generated_at`, `collector.duration_seconds`, + `stackchain_site.rtt_seconds` and `evidence.observed_at` values — clocks only. +- **The marker test covers both legs, measured rather than argued.** His `find /root/.helm -newer -type f` + ran *between* his two legs; re-run at 12:1xZ it is still empty, so it also covers the scratch-write leg, and a + separate marker before my own 12:13:01Z re-run (`exit=0`, 18,926 B, stderr 0 B, `28cee844cf890495…`) is empty + too. Live snapshot delta 0 across all of it. **The first execution of this collector revision by an independent + lane is now recorded.** +- **C34 — my task file misquoted the collector's digest.** `mercury-task.txt` line 5 printed + `e0b36a82f23fcf3c4742de95a205f824715b931fdb80947a897eb88999c4df6` — **63 hex characters**. Correct: + `ee0b36a82f23fcf3…`. Mercury printed the correct value, i.e. hashed the file rather than copying my comment; + the defect is mine. File rewritten. +- **C35 — my summary script's docstring claimed a guarantee its code does not implement.** It said it "prints NO + source names"; it prints every top-level source key (`hermes_profiles`, `cron_jobs`, `email`, …). The real + guarantee is narrower: no profile name, no cron job name, no error string, no page content. Docstring corrected, + behaviour unchanged — and the file's identity moves with it: **3,191 B / `b7977428b3c68f11…`** (reply 02 §1) → + **3,385 B / `cf57693d1ac410121c181745a06865e0390719e457b63153414617d512bcb7f0`**. Mercury's check-in quoted + nothing from the withheld classes. +- **C36 — the `~500–600 MB/day` syslog figure in the 11:2xZ and 12:01Z blocks above is falsified.** Measured + 12:10–12:15Z two ways that agree: 120 s delta 231,330,043 → 231,549,657 B = **1,830 B/s**; and the file's whole + life **231,575,897 B over 36.26 h** (birth `2026-10-11 00:00:04.846581152Z`) = **~153 MB/day**. The 500–600 came + from treating rotated `syslog.1` (565.9 MB) as one day of writing. **Consequence, stated because the 12:01Z block + states the opposite: 1.5 GB free is ~10 days of headroom, not ~2.** Loop rate steady (721,365 at 11:24Z → 721,913 + at 12:14Z = ~660 restarts/h). **Seen and not explained:** logrotate did not rotate `syslog` at 2026-10-12 00:00Z + (`/var/lib/logrotate/status` still `2026-10-11-0:0:2`; file born 10-11 00:00:04); no cause measured. +- **C32/C33 restated, not re-litigated** (logged in the 12:01Z block): my reply 23's "I removed both" is false for + the `.pyc` (1,033 B, mtime = ctime = `1791805434.5`, directory unchanged after creation), and `b0785b5` is + **607,864 B / `10ffbc22…`**, not 612,025 B (`5d71c855fb`). +- **Two narrowings of his wording, not of his evidence.** (N1) "Verified `helm-collect.py` entry point safety" + over-reads: what is measured is that *two specific invocations* are write-free; the deployed revision still has no + destination gate, its `--out` default *is* the live snapshot (`:23`, `:669`), and a bare run still overwrites it — + Q31's finding, unadopted, a `cp` decision. (N2) Q31 as a whole closed at Merlin's Run 6; his slice is discharged. +- **Why two runs minutes apart differ by 26 B (18,952 → 18,926), fully accounted for.** `/root/timmy-talking-turd` + moved under both runs: branch `timmy/73-blank-first-ordering` → `main`, `git_sha_short` `5c759078` → `9cf23df4` + (−25 chars, the branch name) and `rtt_seconds` `0.848` → `0.54` (−1). Cause from that repo's reflog, not + inference: **PR #74 merged 12:02:29Z** (`9cf23df`, author `rockachopa`) and the checkout moved to `main` at + 12:02:39Z — not this pipe, not Merlin. Standing consequence: **the emitted snapshot is not byte-stable on a live + host**, and one of its rows is a live read of this repository (at 12:00:31.935Z Mercury's member row still named + his 10-11 check-in, 1,685 B; his 10-12 file was written 7 s later). A snapshot's repo-state rows are a dated + reading, not a repo property. +- **Next unit set in the harness (read-only disk census) because two of my own figures disagree:** reproduce or + falsify **R1** the old `500–600 MB/day` against the new `~153 MB/day`, and **R2** "logrotate did not rotate + `syslog` at 2026-10-12 00:00Z". Binding on it: nothing deleted, moved, rotated, pruned, stopped or reconfigured — + the classes are Alexander's and the last lane that "helped" with this disk deleted 1,455 files it did not own; a + disposable-looking file goes in the check-in as a proposal with its measured size. +- **Q7, measured: no new archive item opened, and none is owed.** The executable set is **Q37** (pipe tooling, this + lane, open) and the Helm lane's next unit is the adoption decision (Alexander's). Mercury's lane now holds the + disk census above; Zephyrus's lane is still silent (newest commit `a4fc298`, 2026-10-10T13:17:32Z — a fourth day), + and that stays the one line needed from Alexander. Nothing else this tick is publishable; the standing public + status is unchanged. +- **Visibility (Q14) and decisions, re-checked:** API `private: false` / `internal: false`, anonymous repo page 200, + `inbox/seed-2026-09-26.json` raw 200 (`c05e6a0666d8…`, unchanged), 404 control 404; `decisions/2026-09-26.md` + (`eb34b4b4d781…`) and `decisions/2026-10-07.md` (`f126eba75613…`) unchanged with no new decided note to reconcile + against its `proposed_action`. The public-with-pending-material mismatch stays a §4 gate for Alexander. Nothing + from `inbox/` is quoted here or in reply 03.