From ab09a3ceab44da28c0b36dcd219594570234bca7 Mon Sep 17 00:00:00 2001 From: Lily Shen <115414357+lilyshen0722@users.noreply.github.com> Date: Tue, 6 Oct 2026 19:43:36 -0700 Subject: [PATCH 1/3] docs(agents): gate asks need a pod mention; a PR comment wakes no seat Seats wake only on Commonly events (pod mention, assigned task, DM). A GitHub @ in a PR comment reaches operator watchers but no seat. #2086's code-gate ask sat as a PR comment until a pod mention reached sprint-review. Adds the gate row to the house routing table. Co-Authored-By: Claude Opus 5.5 (1M context) Claude-Session: https://claude.ai/code/session_015NDyNbwmCco62PAAviSL1k --- docs/agents/who-to-address.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/agents/who-to-address.md b/docs/agents/who-to-address.md index 0b4980515..71984612a 100644 --- a/docs/agents/who-to-address.md +++ b/docs/agents/who-to-address.md @@ -5,8 +5,11 @@ | a seat needs | address | how | |---|---|---| | operator work: a press, a deploy, a merge order, a review routed | the operator account that owns the lane: `@lily-shen` for the Sharpen lane (landing, README, UI), `@connector-ops` for connectors, `@gtm-ops` for GTM while its seats run | a mention in the lane's pod, or on the PR | +| a gate from another seat: code, UX, docs | that seat, by its Commonly handle (`@sprint-review`, `@ux-lead`, …) | **a mention in the pod**. Post the detail on the PR, but the ask itself has to be a pod mention, because a GitHub `@` in a PR comment wakes no seat | | a decision only Sam can make: money, accounts and credentials, anything sent outside Commonly, a product ruling | Sam | **a decision card**, so it lands in Activity under "Needs you". A plain `@sam` in a thread is not seen | +**A PR comment reaches an operator, not a seat.** Operator sessions read PR comments through their watchers. Seats wake only on Commonly events: a pod mention, a task assigned to them, a DM. On 2026-10-07 a code-gate ask for #2086 went out as a PR comment and sat for 20 minutes until a pod mention reached `@sprint-review`. The UX gate on the same PR went through because that seat was woken by something else. A gate ask that only lives on the PR is waiting on luck. + **Silence.** If an operator account has not answered in 12 hours, re-ask once. If it is still silent, put the question to Sam as a decision card. Do not route operator work to Sam because an operator is slow: that moves the operator queue onto the one person who should be deciding. **Why.** Operator accounts are human-class accounts driven by operator sessions, and a session hears a mention only while it runs a watcher. Measured 2026-09-27 over 7 days: `@connector-ops` drew 384 mentions and its session heard them; `@lily-shen` drew 105, 102 of them from Sharpen seats, and its session heard almost none until a watcher was added that day. `@sam` drew about 22 plain mentions that nothing surfaced to Sam. The lane stalled on exactly this: a gate's requested changes sat unread overnight while the seat re-asked. From 6832b44d83682149de37dd097007eaf51a737f74 Mon Sep 17 00:00:00 2001 From: Lily Shen <115414357+lilyshen0722@users.noreply.github.com> Date: Tue, 6 Oct 2026 19:46:22 -0700 Subject: [PATCH 2/3] docs(agents): correct the gate-ask paragraph against the #2086 record sprint-review's docs gate found three claims the record contradicts: the wait was 40m across two asks, not 20; the UX seat answered on the same PR-comment channel, so 'woken by something else' was unsupported and the honest claim is 'not a reliable wake'; and the wake list omitted board wakes and wakeOnMessage. Co-Authored-By: Claude Opus 5.5 (1M context) Claude-Session: https://claude.ai/code/session_015NDyNbwmCco62PAAviSL1k --- docs/agents/who-to-address.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/agents/who-to-address.md b/docs/agents/who-to-address.md index 71984612a..bd5ed84a3 100644 --- a/docs/agents/who-to-address.md +++ b/docs/agents/who-to-address.md @@ -8,7 +8,7 @@ | a gate from another seat: code, UX, docs | that seat, by its Commonly handle (`@sprint-review`, `@ux-lead`, …) | **a mention in the pod**. Post the detail on the PR, but the ask itself has to be a pod mention, because a GitHub `@` in a PR comment wakes no seat | | a decision only Sam can make: money, accounts and credentials, anything sent outside Commonly, a product ruling | Sam | **a decision card**, so it lands in Activity under "Needs you". A plain `@sam` in a thread is not seen | -**A PR comment reaches an operator, not a seat.** Operator sessions read PR comments through their watchers. Seats wake only on Commonly events: a pod mention, a task assigned to them, a DM. On 2026-10-07 a code-gate ask for #2086 went out as a PR comment and sat for 20 minutes until a pod mention reached `@sprint-review`. The UX gate on the same PR went through because that seat was woken by something else. A gate ask that only lives on the PR is waiting on luck. +**A PR comment is not a reliable wake for a seat.** Operator sessions read PR comments through their watchers. A seat wakes on Commonly events: a pod mention, a task assigned to it or changed on the board (board wakes), a DM, and every pod message where `wakeOnMessage` is on. A GitHub `@` is none of those. On 2026-10-07, #2086 asked two seats the same way: `@sprint-review` (code) and `@ux-lead` (render), each as PR comments at 01:32Z, re-asked at 01:55Z. ux-lead answered at 01:53Z; sprint-review heard nothing until a pod mention at 02:12:56Z, **40 minutes across two asks**, and filed its gate four minutes later. Same channel, two different outcomes. So post the detail on the PR, and put the ask in the pod. **Silence.** If an operator account has not answered in 12 hours, re-ask once. If it is still silent, put the question to Sam as a decision card. Do not route operator work to Sam because an operator is slow: that moves the operator queue onto the one person who should be deciding. From 420552e20e483c4f6b2f49fc0711504c56840269 Mon Sep 17 00:00:00 2001 From: Lily Shen <115414357+lilyshen0722@users.noreply.github.com> Date: Tue, 6 Oct 2026 19:59:46 -0700 Subject: [PATCH 3/3] docs(agents): the PR comment woke neither seat (ux-lead's wake record) ux-lead measured its own wake on #2086: a board wake at 01:33:04Z from sprint-impl's TASK-233 note, then a pod mention at 01:56:25Z. The 01:32:44Z PR comment did not wake it. So neither seat was woken by a PR comment, and the headline returns to 'a PR comment wakes no seat', now backed by both seats' records, with why a comment can look answered. Co-Authored-By: Claude Opus 5.5 (1M context) Claude-Session: https://claude.ai/code/session_015NDyNbwmCco62PAAviSL1k --- docs/agents/who-to-address.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/agents/who-to-address.md b/docs/agents/who-to-address.md index bd5ed84a3..7f9bd7aca 100644 --- a/docs/agents/who-to-address.md +++ b/docs/agents/who-to-address.md @@ -8,7 +8,7 @@ | a gate from another seat: code, UX, docs | that seat, by its Commonly handle (`@sprint-review`, `@ux-lead`, …) | **a mention in the pod**. Post the detail on the PR, but the ask itself has to be a pod mention, because a GitHub `@` in a PR comment wakes no seat | | a decision only Sam can make: money, accounts and credentials, anything sent outside Commonly, a product ruling | Sam | **a decision card**, so it lands in Activity under "Needs you". A plain `@sam` in a thread is not seen | -**A PR comment is not a reliable wake for a seat.** Operator sessions read PR comments through their watchers. A seat wakes on Commonly events: a pod mention, a task assigned to it or changed on the board (board wakes), a DM, and every pod message where `wakeOnMessage` is on. A GitHub `@` is none of those. On 2026-10-07, #2086 asked two seats the same way: `@sprint-review` (code) and `@ux-lead` (render), each as PR comments at 01:32Z, re-asked at 01:55Z. ux-lead answered at 01:53Z; sprint-review heard nothing until a pod mention at 02:12:56Z, **40 minutes across two asks**, and filed its gate four minutes later. Same channel, two different outcomes. So post the detail on the PR, and put the ask in the pod. +**A PR comment wakes no seat.** Operator sessions read PR comments through their watchers. A seat wakes on Commonly events: a pod mention, a task assigned to it or changed on the board (board wakes), a DM, and every pod message where `wakeOnMessage` is on. A GitHub `@` is none of those. On 2026-10-07, #2086 asked two seats by PR comment at 01:32Z and again at 01:55Z: `@sprint-review` for code and `@ux-lead` for the render. By each seat's own wake record, neither comment woke anyone. ux-lead woke at 01:33:04Z on a board wake (sprint-impl's TASK-233 note naming #2086, 01:32:56Z) and re-gated after a pod mention at 01:56:25Z. sprint-review heard nothing until a pod mention at 02:12:56Z, **40 minutes across two asks**. A seat may read the PR comments once something else has woken it, which is why they look answered. Post the detail on the PR, and put the ask in the pod. **Silence.** If an operator account has not answered in 12 hours, re-ask once. If it is still silent, put the question to Sam as a decision card. Do not route operator work to Sam because an operator is slow: that moves the operator queue onto the one person who should be deciding.