docs(records): correct walkthrough ruling times from the transcript, note 6b R1 verdict

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-09-26 15:36:03 -05:00
parent 993673865a
commit 401cc850bb
3 changed files with 29 additions and 13 deletions
@@ -2968,3 +2968,15 @@ brief (636b0fac) and Filbert's review are committed as records.
 Discord restart held: the unit runs from this checkout, and Darkwing's
 uncommitted 6b engine change is in the tree. `discord.sh check` passed at
 20:17Z.
+
+## 2026-09-26: correction to the walkthrough entry (Sage)
+
+The entry above says Jason ruled "between 20:27Z and 20:45Z". That was wrong.
+I wrote the ruling times from estimates and never checked the clock. The
+session transcript shows the real times: 20:19:22Z (tokens), 20:19:52Z
+(Discord), 20:21:13Z (row 8), 20:23:23Z (DYOR), 20:24:43Z (aws skills),
+20:30:48Z (pong) and 20:31:18Z (CHAT-02). The lead decisions file and the row
+8 stub now carry these times. Messages sent to Dewey and Filbert quoted the
+wrong times as well. None of the rulings changed. Rocko's 6b R1 verdict
+(request changes) is noted under lead decision item 9, and the Discord
+restart stays held.
@@ -42,12 +42,12 @@ never returns this row.

 ## Rulings so far (appended 2026-09-26)

- Scope (Jason, 20:36Z): the mosaic-stack dev seats only. They are orch-01,
+- Scope (Jason, 20:21Z): the mosaic-stack dev seats only. They are orch-01,
  plan-01, rev-code-01, rev-code-02, code-be-01 and code-dogfood-01. They
  retire instead of moving, because the T3 seats already cover their work.
  They get no new work. Jason stops each process himself or tells Sage to,
  one seat at a time. The other live fleet seats are outside this row.
- Credentials (Jason, 20:27Z): seat Gitea tokens are read in place,
+- Credentials (Jason, 20:19Z): seat Gitea tokens are read in place,
  read-only, from `~/.mosaic/fleet/agents/<seat>/secrets/`. Nothing is copied.
 - The AGENTS.md restriction on `~/.mosaic` changes stands. Stopping a
  retired seat's process on Jason's word is the only exception.
@@ -60,21 +60,21 @@ which stay with him. Each item names who decided it and what happened.
   location. Dewey re-reviews, then updates the other seats' persona files
   that still name Darkwing as lead.

-## Jason's rulings (walkthrough, 20:27Z to 20:45Z)
+## Jason's rulings (walkthrough, 20:19Z to 20:31Z)

- **Seat tokens for piece D's live round.** Jason ruled at 20:27Z: yes, in
+- **Seat tokens for piece D's live round.** Jason ruled at 20:19Z: yes, in
  place. Piece D reads each seat's own Gitea token by path,
  `~/.mosaic/fleet/agents/<seat>/secrets/gitea-mosaicstack-<seat>.token`
  (0600), read-only. It makes no copies and changes nothing under
  `~/.mosaic`. Sage's Gitea calls use jarvis. Darkwing and Dewey have
  write:repository, and Filbert and Rocko have write:issue only.
- **Discord connector restart.** Jason ruled at 20:29Z: one restart, after
+- **Discord connector restart.** Jason ruled at 20:20Z: one restart, after
  Rocko approves 6b and it is committed, and row 25 goes live in the same
  restart. Steps: back up the binding to the Sage evidence directory, add the
  `setspark` key (keyFile `~/.config/setspark/keys/sage.json`, never read),
  run `discord.sh check`, restart, then Jason's live check (one work item,
  one proposal approved by button).
- **Fleet retirement scope (row 8).** Jason ruled at 20:36Z: dev seats only.
+- **Fleet retirement scope (row 8).** Jason ruled at 20:21Z: dev seats only.
  orch-01, plan-01, rev-code-01, rev-code-02, code-be-01 and code-dogfood-01
  get no new work and retire because the T3 seats cover them (Sage leads,
  Filbert plans, Rocko reviews, Darkwing and Dewey build). Jason stops each
@@ -82,7 +82,7 @@ which stay with him. Each item names who decided it and what happened.
  fleet seats (jarvis, joe, huey, ricer, topher, velma, zane, resume) are
  outside row 8. Credentials stay in place (see piece D above). The
  `~/.mosaic` restriction still stands.
- **DYOR records.** Jason ruled at 20:38Z: DYOR work belongs in
+- **DYOR records.** Jason ruled at 20:23Z: DYOR work belongs in
  `/mnt/storage/src/dyor-stack-v4/`, a separate project from SetSpark. Sage
  has moved from DYOR to SetSpark tasks. Sage's SOUL, CONTEXT, README and
  DISCORD-USER files change to match, and that commit lands before the next
@@ -91,15 +91,15 @@ which stay with him. Each item names who decided it and what happened.
  researcher at 20:10:57Z and "pong" came back at 20:11:06Z. `/api/board`
  showed it at 20:15:18Z. Dewey went through 30 board sends to repo Pi seats.
  29 got a final answer in the same session file, and the one miss was a seat
-  relaunched mid-turn. No second return defect was found. Jason confirmed at 20:43Z
+  relaunched mid-turn. No second return defect was found. Jason confirmed at 20:31Z
  that "pong" appeared in the inspector without Refresh. The 09-13 report
  was about the missing thread view, which CHAT-02 builds.
- **`skills/aws-*`.** Jason ruled at 20:41Z: add them to `.git/info/exclude`,
-  a local ignore that is never committed. Done at 20:41Z. That covers the 20 `aws-*`
+- **`skills/aws-*`.** Jason ruled at 20:25Z: add them to `.git/info/exclude`,
+  a local ignore that is never committed. Done at 20:26Z. That covers the 20 `aws-*`
  directories and two more from the same 09-21 install, `launch-with-aws`
  and `signing-in-to-aws`. They stay where they are and no longer show in
  `git status`.
- **Row 5 CHAT-02 to 08.** Jason ruled at 20:45Z: go on CHAT-02 only, at
+- **Row 5 CHAT-02 to 08.** Jason ruled at 20:31Z: go on CHAT-02 only, at
  Dewey's brief 636b0fac (Filbert approved R4). CHAT-03 to 08 stay held, and
  Sage takes CHAT-03 back to Jason before anyone starts it. Order: the board
  Host and Origin guard (Rocko reviews), then the `packages/conversation`
@@ -109,7 +109,7 @@ which stay with him. Each item names who decided it and what happened.
 ## Added later the same day

 8. **CHAT-02 brief (Dewey, sha256 314da8b0…).** Sage ruled D1 to D4 at
-   20:22Z:
+   about 20:18Z:
   - D1: the writer-claim record and R3-1 move to CHAT-03.
   - D2: Pi only in CHAT-02. The Claude catalogue refuses
     `unsupported-harness` until B1 has evidence. This narrows the plan's
@@ -118,7 +118,7 @@ which stay with him. Each item names who decided it and what happened.
     two read-only routes, and Darkwing reviews that change.
   - D4: Dewey writes the backend, then the Console. Filbert reviews.
   - D5 (the go on CHAT-02 to 08) is still Jason's.
-9. **Discord connector restart held.** Jason said to restart at 20:10Z. The
+9. **Discord connector restart held.** Jason said to restart before 20:17Z. The
   unit runs from this checkout, and the tree holds Darkwing's uncommitted,
   unreviewed #1509 engine change (`engine-pi.mjs`, the new `engineBusy`).
   A restart now would load it. The only committed Discord change since the
@@ -128,3 +128,7 @@ which stay with him. Each item names who decided it and what happened.
   6b and it is committed. If Jason wants row 25 live, the binding change goes
   in the same restart. `discord.sh check` passed at 20:17Z. The service was
   idle, with the last turn on 09-18.
+   Rocko's 6b R1 verdict (about 20:34Z) was request changes. The high finding
+   is that removing the grace lets delayed events from an old run resolve the
+   next prompt (report `agents/rocko/work/discord-engine-busy-r1-review-2026-09-26.md`,
+   047dbd8f). Darkwing is on R2, and the restart stays held.