Repository navigation
Commit 93cdc43
docs(pm-dispatch): new gates default to NO, 「声明即强制」 scoped, rulings complete at ruling time (#19654)
Fixes #19647
Clause-②: no
Three governed-text sentences land in the escalation decision frame and
in the director
charter. Every file in the diff sits at a shrink-only line ceiling, so
each added line is
paid inside the SAME file: **net +0 lines everywhere**.
## Source — the maintainer's own words, verbatim and untranslated
Ruling record: `objectstack-ai/objectui#10094` (the recommendation that
prompted the
correction) and `objectstack-ai/objectui#10179` (the sub-question left
as a separate card).
1. 「我强调了淡化门禁,尤其这个完全没有业务价值,你为什么又要加,你的决裁依据是不是要更新」 — maintainer,
2026-09-22.
2. 「我们系统开发了太多无用的门禁,反而在浪费时间」 — maintainer, 2026-09-21 (standing).
3. 「更新你的技能,既然在决裁了,就一次性决裁清楚,不要等dev再立决裁卡」 — maintainer, 2026-09-22.
## What lands
| # | Sentence | Where |
|:--|:--|:--|
| ① | **新增门禁默认否** — 门禁是只减不增的零件,例外只有维护者点名;荐新增门禁须引其点名原话,否则荐「不加」。 |
SKILL.md axis ④ 创业阶段不扩散 · core-rules.md 四轴 line |
| ② | 「声明即强制」只及 spec 与元数据契约、运行时能力,⛔ 不及 `AGENTS.md` 这类给 agent 读的约定 ——
那些的读者是 agent,不是门禁。 | SKILL.md 基本裁决原则 · core-rules.md 基本裁决 line |
| ③ | 裁决一次裁清:子问题、分叉与执行参数同笔裁定;⛔ 不另立决策卡,仅前提被证伪才回箱。 | SKILL.md 〈升级与决策〉 ·
director.md 基本原则 |
## Premise correction — `.claude/agents/os-dev.md` is deliberately NOT
touched
The dispatch named `os-dev.md` as a second synced copy of the four-axis
frame. It is not one,
and it must not become one:
- `os-dev.md` carries no frame; its own line reads 「框架唯一副本在 pm-dispatch
SKILL.md
〈升级与决策〉;派发词逐字粘贴,dev ⛔ 不留副本」. The two dev-side copies were deleted by the
2026-09-03 batch-3 ruling (item 4, option B).
- `check-skill-frame-sync.mjs` declares exactly ONE copy in `COPIES`
(`.claude/skills/pm-dispatch/SKILL.md`), and its anti-dormancy scan
refuses an undeclared one.
Its self-test pins that refusal at this very path: case `the dev-side
copy returns to the
now-undeclared agent definition → red (anti-dormancy)`.
So writing ① ② into `os-dev.md` would have turned
`check:skill-frame-sync` red on purpose.
「every synced copy」 resolves, today, to SKILL.md alone — which is what
this PR edits.
## Line budget — paid in the same file, per the card
| file | before | after | ceiling | payment |
|:--|--:|--:|--:|:--|
| `.claude/skills/pm-dispatch/SKILL.md` | 819 | 819 | 819 | the two
frame paragraphs drop their provenance parentheticals (dates + ruling
quotations) and compress prose; axis ④ 6 → 5 lines funds ③'s new line |
| `.claude/skills/pm-dispatch/references/core-rules.md` | 151 | 151 |
151 | `落卡与呈报带 Governing text:` moves onto the adjacent 落卡 line, freeing
its line for the 基本裁决 clause; the 四轴 line absorbs ① by dropping a
redundant pointer |
| `.claude/skills/pm-dispatch/references/lanes/director.md` | 63 | 63 |
72 | the two coupled `pm:awaiting-maintainer` rules merge onto one line
|
| `.claude/agents/os-dev.md` | 403 | 403 | 403 | untouched (see above) |
⛔ No ceiling is raised. ⛔ No re-wrap is used as 筹行 — every line is paid
by deleted or
merged CONTENT. Every rule is kept.
**The one judgement call for the maintainer.** The payment is the
residual provenance in the
two frame paragraphs: the 2026-08-04, 2026-08-27 and 2026-09-10 ruling
dates and quotations.
They are the last provenance left in this file, and dropping them is
what the standing
2026-09-04 direction 「各条规则的出处叙事、事故复盘 根本不重要啊,不需要写入skills啊」 already
did to the rest of the corpus — `director.md` carries 创业阶段不渐进 as a bare
rule line today
for exactly that reason, and `AGENTS.md` states it as a rule of its own
(「a rule ... carries
no incident narrative, no ruling date or quotation」). The rulings stay
recorded — in
`packages/spec/src/migrations/registry.ts`, in the ratchet script's own
ceiling comments, in
git history, and in this PR body. The 2026-08-04 principle is not lost:
it lands as the rule
sentence 「创业项目先专注核心能力」.
## Verification
Derived with `node scripts/pm/dispatch-gates.mjs --commands --repo
objectstack-ai/objectstack`
(no paths — the tool takes its own change set from the merge base), at
`442b960`.
- **21 derived gate families, 21 run, 0 NOT-MEASURED, 0 UNRUN** —
reconciled with
the --ran flag pointed at a record file, where every line carries a
double-colon `exit` marker plus the code, captured before any pipe.
Verdict line: `✓ dispatch-gates --ran: 21 derived famil(ies) accounted
for — 21 run,
0 NOT-MEASURED (a DERIVED zero — all 21 recorded an exit code and none
of them is 3)`.
- The card's four named gates, all exit 0:
`check:pm-skill-ratchet` (SKILL.md 819/819, core-rules.md 151/151,
director.md 63/72,
os-dev.md 403/403), `check:skill-frame-sync`
(`4 axes: business-need → long-term-soundness → ai-authoring-safety →
startup-scope-discipline`,
binding sentence present, 1 count mention agrees, 77 markdown files
scanned),
`check:skill-frame-freshness`, `check:pm-skill-id-lint`.
- Run beyond the derivation, all exit 0: `check:skill-frame-freshness`,
`check:pm-settings-deny-roster` (its roster lives under `.claude/`, so
its silence is not
evidence either way), `node scripts/check-skills-token-ratchet.mjs`.
- `pnpm --filter @objectstack/lint run check:doc-formula-expressions`
first exited **3** —
PREREQUISITE NOT MET, nothing measured. Re-run after
`pnpm exec turbo run build --filter=@objectstack/formula
--filter=@objectstack/lint`: exit 0.
- **Repo-wide `pnpm lint` is narrowed, and the narrowing is measured**
(at `442b960`):
① population read from `eslint.config.mjs` itself — every `files:`
selector is a
`{ts,tsx,mts,cts,js,jsx,mjs,cjs}` glob and no block selects `.md`; ②
count read from
`eslint --format json` over the three changed files: 3 entries, 0
messages, exit 0;
③ invariance — no rule block matches a markdown path, so this diff
cannot move the verdict
of any file it does not touch. No package is touched, so there is no `①`
dependency-closure
build and no package `test`/`typecheck` owed; CI's type-check lanes are
declared CI-only by
the derivation.
- No changeset: `.claude/**` publishes nothing from any released package
— hence
`skip-changeset`.
## Acceptance notes
Noted, not filed, not fixed here — the card fences the diff with 「⛔ No
other framework text
changes ride on this card」.
1. **`SKILL.md` 机械守卫索引 row is stale and actively misleading** (class a,
reproducible
today): the row reads `check:skill-frame-sync / -freshness |
四维决策框架两份拷贝的同构与
新鲜度` — 「两份拷贝」, two copies. `COPIES` in
`scripts/check-skill-frame-sync.mjs` has held
exactly one entry since the 2026-09-10 deletion. Reading the row as
written is what produced
this card's own false premise (「both synced copies ... and os-dev.md」),
and acting on it
turns `check:skill-frame-sync` red — the gate's self-test pins that
outcome. One-line fix:
`两份拷贝` → `唯一一份拷贝`. Dedupe words: `两份拷贝` · `skill-frame-sync COPIES one
copy` ·
`机械守卫索引 stale row`.
2. **`check-skill-frame-sync.mjs`'s `wording-only divergence` self-test
case anchors on
hand-copied prose** (class a, hit in this run): it locates its mutation
target in the real
`SKILL.md` by the literals `长期代价` / `创业项目` / `不作数`. Rewording any of
them throws
`self-test fixture drifted` before the gate scans anything — a dead gate
whose presence in
the gate list still reads as coverage. That is precisely the defect the
same file's own
`axisEntryStarts` docblock records and repairs for a sibling fixture
("locating the entry
through THIS parser instead means the fixture depends on the frame's
structure"). This PR
worked around it by keeping 创业项目 in the text. Out of scope here: the fix
is in a gate
script, which would owe that script's own test suite — a new
verification surface. Dedupe
words: `frame-sync self-test fixture drifted` · `mutation target
hand-copied literal` ·
`wording-only divergence anchor`.
## 维护者速读(草稿)
**改了什么** —— 往决策框架里加三句话:① 新增门禁默认否(门禁是只减不增的零件,想加必须引您
点名的原话,否则一律荐「不加」);②「声明即强制」只管 spec、元数据契约和运行时能力,不管
`AGENTS.md` 这种写给 agent 看的约定;③ 裁决一次裁清,子问题、分叉和执行参数同一笔定完,不
再把半个问题丢给 dev 去「另立决策卡」。三个文件都在只降不升的行数天花板上,加的每一行都在同
一个文件里用删减付账,四个文件净增都是 0。
**为什么改** —— 总监席在 objectui 那张卡上,用「这个缺陷已经修过一次」推荐了一条新的必需门
禁,而您的长期方向是删门禁。框架里没有一句话说「新增门禁默认否」,而「声明即强制」写得太宽,
宽到有人把一条没有机器读者的 `AGENTS.md` 约定读成「声明了却没强制 ⇒ 该加门禁」。第三句是另
一件事:您指出既然在决裁,就该一次决裁干净,不要留个尾巴等 dev 再立一张决策卡。
**风险与代价(含回滚)** —— 只改文字,不改任何代码或运行时行为,回滚就是 revert 这个 PR。
真正要您拍板的只有一处:天花板逼我用「删」来付账,我删的是这两段里残留的出处(2026-08-04、
2026-08-27、2026-09-10 三处日期加引文)。依据是您 2026-09-04 的那句「各条规则的出处叙事、
事故复盘 根本不重要啊,不需要写入skills啊」,以及 `AGENTS.md` 自己那条「规则不带裁决日期与
引文」;`director.md` 里同一条「创业阶段不渐进」早就是不带引文的裸规则了。裁决本身没丢:
spec 的迁移登记表、棘轮脚本的天花板注释、git 历史和这份 PR 正文都留着原话,2026-08-04 那条
原则则直接落成规则句「创业项目先专注核心能力」。您要是希望引文留在 skills 里,请回一句,我
改成抬天花板的方案重报(那需要您给一个新的上限数)。另外派发把 `.claude/agents/os-dev.md`
当成框架的第二份拷贝,它不是——那边的拷贝是 2026-09-03 裁掉的,门禁的自测专门钉着「拷贝回
到 os-dev.md 就红」,所以这个文件一个字没动。
**席位意见** ——
**你要做的** —— 读一遍上面三句话是不是您的意思,尤其是第二句的边界(「只及 spec 与元数据契
约、运行时能力」),然后一次亲合。⛔ 我不合并、不请审、不翻 ready。
---
_Generated by [Claude
Code](https://claude.ai/code/session_01SPwf6Kmqo1gqzCSWSuMtQM)_
---------
Co-authored-by: Claude <noreply@anthropic.com>1 parent e9861d2 commit 93cdc43
3 files changed
Lines changed: 16 additions & 16 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
737 | 737 | | |
738 | 738 | | |
739 | 739 | | |
| 740 | + | |
740 | 741 | | |
741 | 742 | | |
742 | 743 | | |
| |||
747 | 748 | | |
748 | 749 | | |
749 | 750 | | |
750 | | - | |
751 | | - | |
752 | | - | |
753 | | - | |
754 | | - | |
755 | | - | |
756 | | - | |
757 | | - | |
758 | | - | |
759 | | - | |
| 751 | + | |
| 752 | + | |
| 753 | + | |
| 754 | + | |
| 755 | + | |
| 756 | + | |
| 757 | + | |
| 758 | + | |
| 759 | + | |
760 | 760 | | |
761 | 761 | | |
762 | 762 | | |
| |||
797 | 797 | | |
798 | 798 | | |
799 | 799 | | |
800 | | - | |
| 800 | + | |
801 | 801 | | |
802 | 802 | | |
803 | 803 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
137 | 137 | | |
138 | 138 | | |
139 | 139 | | |
140 | | - | |
| 140 | + | |
141 | 141 | | |
142 | 142 | | |
143 | | - | |
144 | | - | |
| 143 | + | |
| 144 | + | |
145 | 145 | | |
146 | 146 | | |
147 | 147 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
22 | 22 | | |
23 | 23 | | |
24 | 24 | | |
| 25 | + | |
25 | 26 | | |
26 | 27 | | |
27 | 28 | | |
| |||
53 | 54 | | |
54 | 55 | | |
55 | 56 | | |
56 | | - | |
57 | | - | |
| 57 | + | |
58 | 58 | | |
59 | 59 | | |
60 | 60 | | |
| |||
0 commit comments