Skip to content

pm-dispatch: the director seat presents the governed drafts awaiting a human merge as one decision batch, and checks each carries its four-piece (maintainer, 2026-09-13) #17951

Description

@claude

Filed by the domain:skills seat (session session_01DAcomhvR9kKizeYgg89Vo8, GitHub os-project-manager) at 2026-09-13T07:49Z, routed and graded into this lane under the maintainer's 2026-09-13 self-routing ruling (#17942). Companion of #17950 (the governed-surface tiering); this card is the reading-cost half.

Provenance (live chat, verbatim, untranslated)

Maintainer: 「③ 受管面手合本身也是一条队列。能否简化我的审核步骤,比如我召唤项目总监时可以批量决定?」 The seat answered that the reading cost can be batched today under the director seat's existing 「维护者动作台账」 duty, and that the approve click cannot be batched by any agent (AGENTS.md Prime Directive #14: no agent seat approves a governed PR under any account). The maintainer's follow-up settled the tiering (#17950); this card carries the batch presentation, in the veto window.

Governing text

  • .claude/skills/pm-dispatch/SKILL.md 〈升级与决策〉: 「项目总监席:维护者在所在仓召唤,入口 /pm-dispatch director … 四职 = needs:contract-review 事后审计、决裁勤务、维护者动作台账、governed 合并审计」.
  • references/lanes/director.md (the seat's charter) and references/decision-analysis.md 〈常设决裁批流程〉: 「每批恰好 5 张,末批不足照呈;呈完即停等回批」.
  • AGENTS.md Prime Directive feat: Comprehensive CRM example demonstrating all ObjectStack protocol features #14: the four landing acts lift only for an authorized APPROVED review; 「⛔ No agent seat submits an approving review on a governed-surface PR, under any account」; on four of the five governed surfaces nothing summons the maintainer automatically — only docs/adr/ is routed by CODEOWNERS.

Work item (one PR on references/lanes/director.md, plus the SKILL.md director line only if the ceiling can be paid)

Add one duty to the director seat: at every summon, enumerate every open DRAFT PR on the governed rules layer that carries an in-seat ACCEPT (both repos: is:pr is:open is:draft label:needs-user-decision, then read each PR's ACCEPT / 速读 / review-request state), and present them as a decision batch of at most five rows — PR · card · surfaces · one-line 速读 · 席位意见 · rollback — in the same form as the ruling batches; the maintainer answers one line per batch; the director records the answer on each PR (verbatim), requests any missing review from the authorized accounts, and stops there: the approve and the merge stay the maintainer's own clicks. A PR missing any of its four pieces is listed with the gap named, not presented for a decision.

Acceptance

Grade: p2 Task (the maintainer's own review time is the resource; the batch form already exists for rulings).


Generated by Claude Code

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions