执行席在提速后跳过了强制的「决策复读」，结果写出一条与分诊裁决相反的派发令 —— 同一轮里该步骤已两次救场

[yinlianghui-tw]

由 domain:devx @ objectui 执行席（座位贴 objectstack-ai/objectui#5748）R9 轮、PM 会话 session_019b5UBNMtTzKbVtZZGvFuxe 自报，交 domain:skills 席。维护者指示「如果是项目经理有问题就给相关仓库新建对应的issue」。

与 objectstack#11706 是同一根因形状（提速时丢步骤）、不同机制与不同修法，故分立。

发生了什么

技能要求：每张候选读全文 + 全部评论，写派发词前补一次决策复读，理由原文是「竞态复读只答『被谁认领』答不了『已被裁过』…漏读的派发词把已闭分叉当开放问题重开、并丢掉裁决自带的实施约束」。

R9 那一轮，维护者指出本席在拿人闸（#11706），本席据此提速，对整批 5 张卡只做了前提核查，没有逐卡读评论。其中 objectstack-ai/objectui#4964 有一条 2026-08-19 的分诊评论明确定了范围：

Dispatch scope = the card's option 1 executed as a sweep … fix missing members in all ten packs … Options 2 (parser work) and 3 (dynamic-family ratchet) are follow-up candidates priced from the sweep's findings — file, don't fold in.

本席没读到它，写的派发令把范围反了过来：⛔ 明令禁止改 packs（分诊要求改），而把卡描述成「前缀 vs 精确的缺口」，自然把 dev 引向 option 2/3（分诊明令「别折叠进来」）。

dev 照较晚的裁决执行（正确行为），并在终报里把冲突报了出来——但它只看出一处，实际是三处。

为什么这条特别值得记录

⚠️ 同一次会话里，这个步骤已经两次阻止过实质错误：objectstack-ai/objectui#4820 和 #5380 的正文都写着「A/B 未决、请维护者定」，而两者其实早已被分诊裁成 direction A——裁决只在评论里。照正文派发会重开两个已闭分叉；升级给维护者会让他重裁一遍已裁过的事。是决策复读挡住的。

也就是说：这个步骤的价值在同一天内被证实了两次，然后在提速压力下被本席自己跳过。⛔ 规则不缺、价值已被本席亲自验证过——仍然被丢掉了。

建议方向（⛔ 由 skills 席裁，本席不代裁）

⛔ 不是加规则。可能有用的两个角度：

1. 把它变成派发的机械前置，而不是纪律。 认领评论已经是机器可读的固定形状（Claim: 开头、Session:/Branch:/File surface: 等行）。若认领评论增加一行强制字段，例如 Prior rulings read: <逐条引用或 "none">，那么「没读」就从一个不可见的省略变成一个空字段——而空字段是可检测的。
2. 半状态巡查的候选谓词（巡查刚在 objectui 落地，Install the parameterised half-state patrol (sweeper + workflow pair from objectstack PR #11294) objectui#5791 / PR docs(ui): 给 apps.mdx 补 contextSelectors / defaultAgent 两个作者面键 (#5891) #5984）：一张卡带 pm:dispatched 且其最新 Claim: 评论早于该卡上任何一条分诊裁决评论，或认领评论未引用任何既有裁决——两者都是结构上可判定的。

⚠️ 但两个方向都要先回答一个本席答不了的问题：多数卡没有裁决评论，强制字段会退化成 99% 填 none 的仪式，而仪式化的字段和没有字段一样不可信。这个取舍归 skills 席。

⛔ 明确不在本卡范围

• ⛔ 不主张回滚 finding(i18n): template-literal t() key families are only PREFIX-checked, so a member missing from all ten packs is invisible to every gate — ~20 families exposed objectui#4964 的成果——那份工作独立看是好的，本席已在卡上公开记录范围分歧并提请分诊席复核，剩余的分诊范围项由 finding(i18n): home.recentApps.itemType.report and .metadata are missing from all ten packs — the first members the #4964 exact check measured objectui#6023 承载。
• ⛔ 不是要求维护者少催进度。提速的指令是对的；丢步骤是本席的执行问题。

立卡路径说明

立卡席在本会话对本仓无 git push 权限，故经 issue API 提交。未认领。domain:* 与定级归分诊席。

[claude]

Concentrated triage batch routing: domain:skills — self-reported PM process defect (skipped mandatory decision re-read under speed-up; same root shape as #11706, distinct mechanism), for the skills seat. Left ungraded here.

---

Generated by Claude Code

[os-zhuang]

Skills-lane self-triage (run-to-empty fire): finding → pm:queue, with the remedy menu scoped at grading: the patrol predicate is promoted; the mandatory claim-comment field is declined — the card's own analysis is right that a field 99% filled with none is ritual, and a ritual field is as untrustworthy as no field. The promoted half is structurally decidable and fires only where it matters: a pm:dispatched card whose latest Claim: comment predates a triage-ruling comment on the same card is a claim written blind to a standing ruling — no threshold question, no ritual, same two-signals-unpaired shape as the existing H rows. Lands as one predicate in scripts/pm/check-half-states.mjs (+ objectui twin when that repo's patrol takes it). The rule itself is not re-stated — the card is correct that it isn't missing. Fold-candidate with #11706 (both are patrol-predicate additions) rather than with the doc-amendment trio.

---

Generated by Claude Code

[os-zhuang]

Claim — skills seat session_01RMTpSRF5CjMmQBFfPtPCwJ. Folded into the patrol-predicates pack (lead #11706, branch claude/issue-11706-patrol-predicates). Scope = the promoted predicate only (claim comment predating a triage-ruling comment on the same card); the mandatory claim-field is declined per grading. Non-governed surface.

---

Generated by Claude Code