pm-dispatch: a project-run seat form — seat post as a stub, posture and ledger in the Claude Code project, dispatch order in the card thread, branch named before the thread opens; 项目总监 → 总监席 (maintainer's word 2026-10-23) #25379

Ruled: 6363872862 · batch #4 letters 1 A · 2 A · 2026-10-23T11:29:31Z (item 3 of this card's Wanted list is ruled as letter A there; item 3 of the batch is hotcrm#2252)

Filing gate ③: a maintainer-direct task, the maintainer's words quoted verbatim. Filed from the Claude Code project "Objectstack" (account os-elon-musk) by the research thread 车队机制迁往 Projects on the maintainer's word there. ⛔ Not a claim. Lane self-applied under exception 二 (.claude/**, the lane table's domain:skills row); grade suggested p2; triage may regrade.

Reader (who acts): the domain:skills seat 2 (seat post #19287), in one PR on .claude/skills/pm-dispatch/** (Tier S) plus the ratchet ceiling rows in scripts/pm/check-skill-line-ratchet.mjs. The card thread runs at CONTRACT_REVIEW_TIER.

The maintainer's words (2026-10-23, the project's thread 车队机制迁往 Projects, verbatim)

The research memo (五张决裁卡, recommended letters 「1B 2A 3B 4B 5B」, plus section 9 on naming and skill loading) was presented at 04:03Z and 04:28Z. The maintainer answered:

同意，你现在就立卡派发处理。

Earlier in the same thread, the facts this card rests on:

我现在测试下来 claude code projects 非常好用，拍一个fable调研一下我们之前的车队机制改如何优化以及尽量过渡到 projects 模式。
我的车队还有一个核心痛点是我有很多claude code 20x账户，分别在运行。
现在的命名也有问题，Claude code 叫projects，我们之前有一个项目总监

What was measured (this project, 2026-10-22 14:22Z – 10-23 03:46Z)

• A Claude Code project is single-account: its threads, memory, shared folder and inter-thread messages never cross accounts. GitHub stays the only cross-account bus; the seat post, the six-state labels, Claim: and the fleet bot are exactly that bus and stay.
• The seat-post protocol (seat-lifecycle.md 〈座位贴协议〉, seat-post-protocol.md) was written for a seat with no memory and no threads, so posture, ledger and shift narrative all go into the post body. A project already carries those, so every one of them was written twice: seating a seat cost 3–5 relay writes, dispatching one card 6–10 (claim 2–3, order read-back 1, ACCEPT 1, landing 1–2, close-out 1–2); [PM seat] domain:devx @ objectstack — 🟢 os-elon-musk · 由 os-elon-musk 账户的项目负责 #6023 carries 439 comments; this account fired 100 fleet-write runs between 00:56Z and 03:36Z on 10-23 alone.
• Of the seat post's four sections, other accounts read three facts: which account holds the lane, who is seated, the hot-file serial queue.
• The card-thread handshake (thread pushes an empty branch → seat writes Claim: → thread starts) took 5–10 minutes per card (pm-dispatch: merge domain:engine, domain:services and domain:cli into domain:server (maintainer 乙, 2026-10-22), with a no-interrupt alias transition, and move packages/qa (dogfood) to domain:devx #24907: 14:39Z → 14:51Z).
• The protocol's round report (seat-lifecycle.md 〈轮次报告与节奏〉) was not written once in two days; the thread checklist carried it.
• No seat had a Routine; the issue side was never patrolled, and a seat that hit the usage wall (17:56Z → 21:04Z) left three landed-ready PRs unwatched.
• The protocol names 「项目总监 (Project Director)」 (SKILL.md L56, L274; lanes/director.md L1; lanes/skills.md once) and 「项目协调者」 (PR docs(pm-dispatch): a project-coordinator reference — the cross-lane scheduling rules a Claude Code project runs by, so its instructions name only its lanes #25255's coordinator.md), while the platform calls the container itself 项目 (a Project) and GitHub's board an org Project.

Wanted

A project-run seat form in pm-dispatch, beside the Routine-seat form, chosen when the seat session is a project thread (the mode:thread condition already in dispatch-runbook.md 〈卡线程〉):

1. Seat post = stub. Body holds only: seated account · the project's name · seating time · the hot-file serial queue · one pointer line 「posture and ledger live in the project」 · an optional wall note (「本席撞墙，预计 HH:MM 恢复」). Posture, inherited ledger, shift narrative and round reports are ⛔ not written to the post. Title, assignee and the seating audit comment stay as today. Hand-over to ANOTHER account still writes the clock-out brief comment (that is the one cross-account read).
2. Dispatch order rides the card thread's opening message, written by the coordinator when it opens the thread; /mnt/project-files/<seat>/dispatch-<N>.md is no longer required; the card's dispatch comment keeps one pointer line.
3. Branch named before the thread opens. The seat claims first (assignee + pm:dispatched + Claim: naming the branch the coordinator will give the thread), then asks for the thread; the thread verifies the newest Claim: names its branch as today and starts at once. Ruled 2026-10-23 (comment 6363872862, letter A): the branch is platform-assigned at thread creation and cannot be named beforehand; the coordinator reads it from the new thread's session record at spawn and hands it to the seat, the seat claims, the thread verifies the newest Claim: names its branch and starts (fallback: the thread reports its branch as today). The empty-branch probe push is dropped.
4. Wake = events + one patrol routine per project. PR side: subscribe_pr_activity on every card PR (already a rule). Issue side: one project routine every 2–4 hours runs the collection step of execution-duties.md for every lane the project holds (unlock scan, hold release, stale premise, awaiting-landing list, wall note). The per-seat Routine, the self-bound cron and the cross-wall timer chain in seat-lifecycle.md do not apply to this form. Ruled 2026-10-23 (comment 6363872862, batch item 2, letter A): a seat run as a plain direct session (neither a UI Routine nor a project thread) is summoned by hand like the 总监席 — no self-wake, no Routine, not resident.
5. Round report = the thread checklist; the five health figures move to the project's daily digest (the 总监项目's routine), ⛔ not a chat table per round.
6. Naming. 「项目总监」→「总监席」 (SKILL.md L56, L274; lanes/director.md L1; lanes/skills.md), 「项目协调者」→「协调者」 (in docs(pm-dispatch): a project-coordinator reference — the cross-lane scheduling rules a Claude Code project runs by, so its instructions name only its lanes #25255's coordinator.md, re-pointed by its author after this lands, as pm-dispatch: revoke every autonomous-adjudication channel — a seat analyses and recommends, every needs_decision goes to the maintainer's director ruling batch (maintainer's word 2026-10-23) #25344 did for item 5), GitHub's org Project →「看板」 (rest-channel.md L78). The Claude Code project is 「项目」; the project hosting the director seat is 「总监项目」, a project holding lanes is 「车道项目」.

Rule after the change, in one sentence: GitHub keeps what another account reads (six-state labels, assignee, Claim:/Release:, the seat stub, the PR and its ACCEPT, the ruling record); the project keeps the working layer (posture, ledger, orders, round reports, memory).

Out of this card's scope: the account topology itself (which account holds which lane — the maintainer assigns it per project instructions), the decision-card landing authorization trial, the director project's inbox-scan routine, and any AGENTS.md (Tier H) line.

Acceptance

• seat-lifecycle.md / seat-post-protocol.md carry the stub template and say which form applies when; dispatch-runbook.md 〈卡线程〉 carries items 2–4; coordinator.md (after docs(pm-dispatch): a project-coordinator reference — the cross-lane scheduling rules a Claude Code project runs by, so its instructions name only its lanes #25255 lands) points at them, ⛔ no second copy.
• git grep -n '项目总监' -- .claude/skills returns nothing; git grep -n '总监席' -- .claude/skills/pm-dispatch/SKILL.md hits L56 and L274's successors.
• pnpm check:pm-skill-ratchet green: new lines are paid for by deleting Routine-seat-only lines that the project form makes conditional (the self-bound cron, the hourly cross-wall Routine, the send_later accelerator), ceilings lowered where a file shrank; pnpm check:pm-skill-id-lint, pnpm check:skill-frame-sync, pnpm check:skill-frame-freshness green.
• The three seat posts this project holds ([PM seat] domain:skills · seat 2 — 🟢 os-elon-musk #19287, [PM seat] domain:devx @ objectstack — 🟢 os-elon-musk · 由 os-elon-musk 账户的项目负责 #6023, hotcrm#1353) are rewritten to the stub on their next write-side refresh — by the seats, ⛔ not by this PR.
• Tier S landing: a CONTRACT_REVIEW_TIER PASS on the head, then the owning seat lands it on the maintainer's word.

Dedupe

MCP search_issues, objectstack, "pm-dispatch project-run seat form seat post stub ledger in Claude Code project dispatch order card thread event-driven wake session start hook" → 40 hits; the top ten are #25219 (open, PR #25255 — the coordinator reference this card builds on, not a duplicate), #25185 (closed — introduced mode:thread), #24585, #20966, #21118, #19287, #20154 (closed — posture not inherited through the brief), #22060 (open tracking — rule-text diet; this card deletes lines, so it serves that program), #18917, #7623. None defines the project-run seat form or the stub. New.

Dedupe words: project-run seat form seat post stub · dispatch order in card thread opening message · rename 项目总监 总监席.