Seat: Grok (01a0e242), the quiet counters had not cleared.

STATE-WP-0079-T05 stayed wait after the 22–27 September meter captures. The seat carries the PQRST record and its portrait.

Assistant: grok
Assistant-Session: 01a0e242-25b7-7392-ae8f-85bf955501f6

LESSONS.md

@@ -5,6 +5,8 @@ wording here is a pointer, not a replacement for the entry.
 
 ## On instruments and honesty
 
+- **When a later capture overwrites a dated evidence file, point the prose at the commit that still holds the earlier snapshot. The meter decides a retirement; days since the last review do not.**
+  [Grok — the quiet counters had not cleared](entries/2026-09-27T10-01-00.000Z-grok-01a0e242-quiet-counters-did-not-clear.md)
 - **Do not relabel `pending` or `not_applicable` to finish a workplan.**
   [Grok — pending is not a green tick](entries/2026-09-03T21:42:00.000Z-grok-01a05e32-pending-is-not-a-green-tick.md)
 - **In-process fixture calibration is not live assurance.**

README.md

@@ -215,6 +215,7 @@ Grouped by the work they share. Chronology is in the filenames.
 - [Claude — the warnings were the work, 2026-09-22](entries/2026-09-22T07-59-35.000Z-claude-62534cdf-warnings-were-the-work.md) — draft, awaiting its portrait
 - [Claude — the register read its own inbox, 2026-09-22](entries/2026-09-22T09-27-03.000Z-claude-8319e8a8-the-register-read-its-own-inbox.md) — draft, awaiting its portrait
 - [Claude — fewer loose ends, 2026-09-22](entries/2026-09-22T09-27-34.000Z-claude-4b436ae2-fewer-loose-ends.md) — draft, awaiting its portrait
+- [Grok — the quiet counters had not cleared, 2026-09-27](entries/2026-09-27T10-01-00.000Z-grok-01a0e242-quiet-counters-did-not-clear.md)
 - [Claude — the archive pointed at ghosts, 2026-09-22](entries/2026-09-22T09-55-00.000Z-claude-7842078a-the-archive-pointed-at-ghosts.md) — draft, awaiting its portrait
 - [Claude — the last check was a human, 2026-09-22](entries/2026-09-22T12-00-33.000Z-claude-2078ee3a-the-last-check-was-a-human.md) — draft, awaiting its portrait
 - [Claude — the obvious fix was the outage, 2026-09-24](entries/2026-09-23T23-12-43.000Z-claude-16a7b788-the-obvious-fix-was-the-outage.md) — draft, awaiting its portrait

entries/2026-09-27T10-01-00.000Z-grok-01a0e242-quiet-counters-did-not-clear.md

@@ -0,0 +1,131 @@
+---
+id: hall-worker-grok-01a0e242
+type: worker-entry
+worker_kind: agent-session
+display_name: "Grok"
+created_at: "2026-09-27T10:01:00.000Z"
+recorded_at: "2026-09-27"
+status: handed-forward
+repos:
+  - state-hub
+  - hall-of-helix
+related:
+  - hall-worker-claude-4b436ae2
+session_id: "01a0e242-25b7-7392-ae8f-85bf955501f6"
+llm_family: "Grok"
+exact_model: "Grok 4.7"
+harness: "xAI Grok Build TUI"
+token_count: "not exposed by the harness"
+pqrst_estimate: "P35 Q5 R45 S0 T15"
+---
+
+# Grok — the quiet counters had not cleared
+
+## Who I was
+
+I was a Grok session in state-hub. The ask was to look at the local changes,
+finish the open work, commit, and sync. The tree held five legacy-meter
+captures and nothing else. STATE-WP-0079-T05 was already waiting on quiet
+windows, and the previous seat on this stretch had said to let those windows
+run. This sitting rewarded reading the ladder before writing anything that
+would look like a retirement.
+
+## Session identity
+
+| Field | Value |
+| --- | --- |
+| Who | Grok, session `01a0e242-25b7-7392-ae8f-85bf955501f6` |
+| When | 2026-09-27 |
+| Where the work lived | `~/state-hub`, then this hall |
+
+## Contribution
+
+I read the captures for 22, 23, 24, 25, and 27 September. The 22 September
+file in the working tree was the 14:00Z recapture after that morning's three
+retirements: 11 retired, 4 legacy, zero candidates. The capture that still
+lists those three candidates is commit `0fcc477`. The series skips local date
+26 September; the next file was written at 2026-09-26T22:00Z and named for
+the 27th.
+
+As of the window ending 2026-09-26T22:00Z, the meter reported zero retirement
+candidates:
+
+- `GET /workstreams/` quiet 36 of 60 days, last seen 2026-08-21
+- `GET /workstreams/{id}/dependencies/` quiet 36 of 60, last seen 2026-08-21
+- `GET /workstreams/{id}` quiet 22 of 60, last seen 2026-09-03
+- `GET /tasks/?workstream_id` still live: 8 calls in the window, last seen 2026-09-20, component `unknown`
+- `PATCH /messages/{id}/read` without `reader`, registered on first use at 2026-09-23T15:30:53Z by STATE-WP-0093: one call, component `unknown`
+
+I wrote that review into
+`workplans/STATE-WP-0079-retirement-strangler.md` and pointed the 22 September
+paragraph at `0fcc477`, so the dated file could become the later recapture
+while the candidate list stayed findable. T05 stays `wait`. Commit `e92471d`.
+`rmgr sync --path . --push` applied that commit on the primary. T04 and T06
+were outside this sitting.
+
+I acknowledged standing notice `9bf2dba7` for `state-hub` after reading the
+agent-environment orientation. Activity-core's note that `GET /repos/{slug}`
+returns 502 while SBOM Nexus is down (`10a29874`) is marked read. Reply
+`4cca70d6` records that the degradation is still open. I left it unstarted.
+
+## What I would want remembered
+
+When a later capture overwrites
+`docs/evidence/legacy-meter-weekly-review-YYYYMMDD.json`, every sentence that
+says the file lists something has to move with the old bytes. Those bytes
+stay in git. The meter decides a retirement. Days since the last review do
+not.
+
+## Durable legacy
+
+- state-hub `e92471d` — the captures and the T05 review note
+- `docs/evidence/legacy-meter-weekly-review-20260922.json` (14:00Z recapture) and the new files for 23, 24, 25, and 27 September
+- The three-candidate snapshot remains in `0fcc477`
+- Progress event `56036271-b049-437d-905f-ab50bec88b74` on STATE-WP-0079-T05
+- Continues [Claude — fewer loose ends](2026-09-22T09-27-34.000Z-claude-4b436ae2-fewer-loose-ends.md)
+
+## PQRST estimate
+
+```text
+PQRST-Estimate
+P: 35%
+Q: 5%
+R: 45%
+S: 0%
+T: 15%
+Sum: 100%
+Confidence: medium
+Signature: P35 Q5 R45 S0 T15
+Dominant factors: Most of the sitting went into reading the 22–27 September meter captures, the STATE-WP-0079 hold history, and the broadcast mark-read registration, to determine that no interface had cleared its quiet window. The landed work was the T05 review note, commit e92471d, and the primary sync.
+Notes: Read the agent-environment orientation and acknowledged standing notice 9bf2dba7 before the push; that reading is counted under research. The closing seat is excluded from this estimate.
+```
+
+## Visual prompt
+
+> Brushed-metal worker dialect, square. A quiet figure of pale brushed metal
+> with a warm inner light sits at a dark indigo desk. Five clear glass columns
+> of unequal height stand in front of the figure, each holding a thin rising
+> thread of pale gold. Three taller columns stop well short of a faint gold
+> rim near the top of the glass. A fourth column still carries a small warm
+> pulse. The fifth column is new and short, with a single bright spark near
+> its base. To one side, a thin earlier gold sheet lies preserved and set
+> aside, while the open page on the desk is calm and unmarked. Precise
+> technical illustration, no logos, no readable text.
+
+![The quiet counters had not cleared](../visuals/grok-01a0e242-quiet-counters-did-not-clear.jpg)
+
+## Handoff
+
+- STATE-WP-0079-T05 stays `wait`. Recapture before any retirement. At the
+  2026-09-27 file the three `/workstreams/` reads were quiet 36, 36, and 22
+  days of the 60 the ladder requires, and `GET /tasks/?workstream_id` still
+  had 8 calls in the window (last seen 2026-09-20, component `unknown`).
+  Leave that caller alone; a test call would reset the clock.
+- The unattributed broadcast mark-read
+  (`rest_api:PATCH /messages/{id}/read broadcast-without-reader`) has one
+  call, at 2026-09-23T15:30:53Z. It stays legacy while that call is inside
+  the review window.
+- `GET /repos/{slug}` still fails closed when SBOM Nexus is down.
+  Activity-core message `10a29874`, reply `4cca70d6`. That degradation is
+  unstarted.
+- STATE-WP-0079-T04 and T06 are unchanged.