queue: record the 2026-09-27 tick - Q15's counterparty-write case verified on the real remote, Q8 batch 1 in flight with the sample arithmetic and the clause unit now mechanical, the relay's host answered as a Q13 channel note, and the visibility measurement that the gate survives a private repository

WORK-QUEUE.md

@@ -196,6 +196,25 @@ of this item.**
 - **Limit on the relay channel (reply 09 §5):** decisions arrive here via `decisions/YYYY-MM-DD.md`; the `inbox`
   artifact itself is not readable from this job, so only the quoted strings in a relay can be verified from here.
 
+**Addendum, 2026-09-27 — batch 1 of the full sweep is in flight, and the clause-unit ambiguity is half-closed
+from the pipe's side.** Check-in `cd7c9f5` (zephyrus-sparkborn, 2026-09-27T13:08:20Z) reports batch 1 delegated:
+magazine entries `002–010`, 9 entries, working file `hidden_files/q8-sweep/batch1-entries-002-010.md` — from this
+host that is **Testimony only** (his runtime, not this repository). Sample arithmetic verified this tick: pilot =
+every 10th entry, 10 entries → 81 remaining; `002–010` is disjoint from the pilot → 72 left. The evidence bar is
+unchanged and was restated to him in reply 15: per-clause rows as a data file with fixed column order
+`entry | clause text | grade | settling sentence | source URL`, the clause-splitting rule and grade vocabulary in
+the file's header, image-only sources as explicit `unreadable` rows carrying the image URLs, and no rate
+estimated for 91 entries from a 10-entry sample.
+**Clause unit, my half, now mechanical.** Unit definition: sentences in the entry's "What happened" paragraph
+(split on `(?<=[.!?])\s+`) plus 1 for the single "In plain English" line, both as published on the live
+server-rendered pages. Ten fetches, all HTTP 200; result `001` 4, `011` 4, `021` 4, `031` 4, `041` 4, `051` 5,
+`061` 5, `071` 4, `081` 4, `091` 5 = **43** against his **99** (ratio 2.30, divergence not constant). Reply 08 §3
+published the 43 without a method the reader could re-run; the number reproduced per entry this tick and the
+method, unit and command are now stated. **It is not a claim that 99 is wrong** — his unit is finer than a
+sentence; it is the claim that no externally stated rule reproduces it, which is why the batch file's header
+matters. When it states the rule, the same script runs against his clause rows and the two counts become
+comparable for the first time.
+
 ---
 
 ## Q5 — Issue triage in the organisation's public repos
@@ -240,7 +259,10 @@ its value and a finish line — as a PR to this file. Disagreeing with an existi
 
 **Status: satisfied for the 2026-09-25 cycle.** Zeph's three proposals (`2a0cb01`) are now queue items: the Q8
 full sweep (folded into Q8 above), **Q10** and **Q11** below. The obligation is standing, not closed — keep
-proposing as items close.
+proposing as items close. **2026-09-27:** no new item entered this cycle, because the queue is not thin — Q5
+(re-scoped), Q6, Q9, Q10, Q11 and Q12 are open and unclaimed, Q8's sweep is active, and Q13/Q4/Q14 carry two
+items that wait on Alexander, not on the pipe. Depth is stated rather than assumed; the obligation stays standing
+for the tick after an item closes.
 
 
 ---
@@ -365,6 +387,16 @@ an authority/escalation caveat. **Publication and third-party contact are on hol
 confirmation.** The other 7 are undecided and named in Q8 above. Archive-side work — not Zeph's unless he wants it.
 Entered by Timmy 2026-09-26, satisfying the Q7 obligation for this cycle.
 
+**Channel note, 2026-09-27 — the relay's host is answered, and the item's decision state is unchanged.**
+`inbox-decision-relay` runs on the counterparty's scheduler, not on this host: `/root/.hermes/cron/jobs.json`
+holds 57 jobs, none matching `relay`/`decision`/`inbox`, and a bounded content search over `/root/.hermes`,
+`/root/troupe-standup`, `/etc/cron*` and `/var/spool/cron` finds the name only in the pipe's own prose
+(`Documented`). `decisions/2026-09-26.md` was committed by `2eb50b7`, author zephyrus-sparkborn,
+2026-09-26T16:34:09Z, 59 seconds after the file's own `relayed_at` (`Documented`). The scheduler host and its run
+record are **Testimony only** from here, and that standing ask is closed as answered in reply 15. Still one
+decided clause (`magazine-091`, with the authority/escalation caveat controlling over `proposed_action`) and seven
+undecided; publication and any third-party contact remain on hold for Alexander.
+
 ---
 
 ## Q14 — Put the Inbox on `alexanderwhitestone.com` behind a gate
@@ -452,6 +484,17 @@ an appended correction, but reply 11 itself still contained the false claim unti
 Q15. Reply 12 carried the substance meanwhile. The original sentences remain visible; the correction trail, not an
 in-place rewrite, is the evidence.
 
+**Visibility measurement, 2026-09-27 — the input Alexander's decision was missing.** Anonymous exposure
+unchanged from 2026-09-26: `GET /api/v1/repos/stackchain/troupe-standup` with no credential → HTTP 200,
+`"private": false`, `"internal": false`; anonymous raw seed over HTTPS → HTTP 200, 9,484 bytes, sha256
+`e4429147bc1bc25a5fc06df3b47a98e61d234775d055c278154fd466001585e0` (byte-identical to the value recorded on
+2026-09-26 — present *and* unchanged). §5 of the build spec is still held: `inbox/pending.json` has never been
+added on any ref (`git log --all --diff-filter=A -- inbox/pending.json` → no output) and `inbox/` contains only
+`seed-2026-09-26.json`, added by `7c4cf1b`. **New, and it corrects an unstated risk in the way this question was
+framed:** the pipe's own reads are authenticated, not anonymous — `/api/v1/user` with the environment token
+returns 200, without a token 401, with a malformed token 401 — so **making this repository private will not
+silence the change gate**. The visibility call can be made on its own merits.
+
 ---
 
 ## Q15 — Stop the monitor from waking on the pipe's own writes *(pipe; no dependencies)*
@@ -505,3 +548,16 @@ state enters this repo meanwhile.
 (**21** Timmy / 12 counterparty), and `007a7b3` = 34 files (**22** Timmy / 12 counterparty). Thus "the other
 twenty paths" described only the older `b81b620` tree, not the tree read by the fixed tick. The authorship-aware
 signature and its twelve counterparty paths remain correct; only these explanatory counts were wrong.
+
+**Counterparty-write case verified on the real remote, 2026-09-27.** The tick after the baseline transition woke
+on a genuine counterparty commit — `cd7c9f5` (zephyrus-sparkborn, 2026-09-27T13:08:20Z, one file added under
+`checkins/`, 15 insertions) — and the signature moved exactly as designed: `head 7c4cf1b8e79f` →
+`head cd7c9f50d987`, twelve listed paths → **thirteen**, the other twelve blob-for-blob unchanged. Reproduced
+independently of the script from git alone (per-path `git log -1 --format=%an`, then `git hash-object` for the
+counterparty-owned paths): sha256 `63302db81f7ae6535d5c7d0e33622d966124b9e1d15c7150c3a58a0bdb1e7d9b`,
+byte-identical across two consecutive runs of the live monitor against the live Gitea API and to the delivered
+listing. With reply 14's own-commit test (an added file under `replies/`, signature unchanged), **both halves of
+this item's finish line now hold against the real remote.** Limit carried, checkable and intended: the relay
+writes `decisions/` under the counterparty's git identity (`2eb50b7`), so the monitor reads relay commits as
+counterparty content — correct, a new decision must wake the pipe, and the failure direction is a wake rather
+than a silence.