Skip to content

Commit baac8e1

Browse files
docs(pm-dispatch): decision-analysis writes the platform-first rule behind the app-repo recommendation special case (#24280)
Fixes #24256 Clause-②: no ## What changes One file, `.claude/skills/pm-dispatch/references/decision-analysis.md`, section 〈应用仓推荐序特例〉. The maintainer's standing word of 2026-10-18, 「平台相关的功能,应该尽量先改平台。」, becomes the general rule of the section, verbatim and dated; the existing blocked-card special case stays byte-identical as its application; the two corollaries the ruling batch used are added; provenance is written in the corpus register (comment ids and case names as plain words, no hash prefix). The section after the edit (L44 to L50): ```text ## 应用仓推荐序特例 - 「平台相关的功能,应该尽量先改平台。」(维护者 2026-10-18 逐字,裁决台账 6245607810,批 362) - 能力先建在平台(spec、objectstack 运行时、objectui 渲染器);应用仓(cloud、hotcrm)不自建替代。 - 阻塞源是平台缺陷 ⇒ 恒荐等待;⛔ 不荐绕行(形状容错、复刻平台规则)、不荐劈半落地。 - 过渡唯维护者明裁;应用仓临时扩展平台契约,仅当平台卡与移除卡同一裁决立出。 - 应用仓裁决立出的平台卡取被裁卡优先级,⛔ 不降档。推论出处:cloud 2932 A、cloud 2924 A。 ``` Where each item of the dispatch's deliverable lands: | item | line | carried as | |---|---|---| | 1. the dated rule, verbatim | L46 | the sentence byte-for-byte (fullwidth comma and full stop kept), then 「维护者 2026-10-18 逐字」 | | 1. gloss: platform scope, built there first | L47 | 「能力先建在平台(spec、objectstack 运行时、objectui 渲染器)」 | | 1. gloss: no local substitute in an app repo | L47 | 「应用仓(cloud、hotcrm)不自建替代」 | | 1. gloss: unless the maintainer rules the interim explicitly | L49 | 「过渡唯维护者明裁」 | | 2. the existing special case, as the rule's application | L48 | unchanged, byte-identical (the diff does not touch the line) | | 3. corollary (a) | L49 | 「应用仓临时扩展平台契约,仅当平台卡与移除卡同一裁决立出」 | | 4. corollary (b) | L50 | 「应用仓裁决立出的平台卡取被裁卡优先级,⛔ 不降档」 | | 5. provenance | L46, L50 | ledger comment 6245607810 and batch 362 in the rule's attribution; the cases cloud 2932 A and cloud 2924 A as the corollaries' source, after the operative sentence ends | ## Line budget: 50 before, 50 after, ceiling 50 (headroom 0, no raise) Five lines added in the section are paid by five lines removed at the head of the file, all by deleting content the file already carries elsewhere; nothing is re-wrapped. Each removed clause and where it survives: | removed (old line) | survives at | |---|---| | L3 「见 SKILL.md 〈升级与决策〉节的四轴框架」 | new L3 「四轴见 SKILL.md 〈升级与决策〉」, the same pointer | | L3 「本文只放适用面、批流程与两个固定形状」, a table of contents | the section headings themselves: 〈常设决裁批流程〉, 〈落卡分析模板〉, 〈四棱卡面块固定形状〉; 「适用面」 is now the clause on new L3 | | L5 heading 「## 适用面」 and its blank lines L6, L8 | the scope sentence now opens the file on L3, so the section has nothing left to hold | | L7 「只约束 `needs-user-decision` 卡与决策箱讨论的四维分析。」 | new L3, word for word, with its implicit subject 「本文」 spelled out | Measured before folding: `git grep -n "适用面" -- .claude scripts/pm` at the base answers three lines, all in this file (old L3, the old heading L5, and L17, the batch flow's own unrelated 「适用面 =」 term), so no reader greps the heading. Every line of the file is within 120 bytes (the ratchet's line scan: zero offenders, zero exemptions; L3 and L46 to L50 measure 118, 120, 118, 119, 109 and 116 bytes). ## Where this differs from the suggested route - The suggested section shape had the rule on one line. Measured: the verbatim sentence with its brackets is 57 bytes and the attribution 29, so the gloss (platform scope with the two repository names, the app-repo prohibition, the interim exception) cannot share the line within 120 bytes. The rule takes L46 and L47, and the interim exception rides L49 beside corollary (a), which is the form such an interim takes. - The suggested fold measured three freed lines, as the seat counted: the scope clause cannot join the old intro line within 120 bytes, so the intro would wrap to two. The fourth line comes from dropping the intro's table of contents, which the headings already carry, so the intro and the scope clause fit one line (118 bytes). - The provenance is split between the rule's attribution (ledger id and batch) and corollary (b)'s tail (the two cases, labelled as the corollaries' source), because no single line had room for all of it. ## Verification All on the final head `46a29bff` (the branch commit `e17629d8` plus a merge of `origin/main` `93b4acb5`, which touched only `scripts/pm/dispatch-gates*.mjs`). The gate list was derived from the merge base with `node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack`: 17 commands, the same 17 the seat derived. Each exit code was captured before any pipe: ```text node scripts/check-closing-keyword-parity.mjs :: exit 0 node scripts/check-closing-keyword-parity.mjs --self-test :: exit 0 node scripts/check-comment-mask-corpus.mjs :: exit 0 node scripts/pm/check-harness-current.mjs --self-test :: exit 0 pnpm --filter @objectstack/lint run check:doc-formula-expressions :: exit 0 pnpm check:agent-test-spelling :: exit 0 pnpm check:cross-package-test-inputs :: exit 0 pnpm check:doc-authoring :: exit 0 pnpm check:driver-memory-census :: exit 0 pnpm check:gitlink-declared :: exit 0 pnpm check:nul-bytes :: exit 0 pnpm check:pm-governed-merges :: exit 0 pnpm check:pm-skill-id-lint :: exit 0 pnpm check:pm-skill-ratchet :: exit 0 pnpm check:refd-timer-probe :: exit 0 pnpm check:skill-frame-sync :: exit 0 pnpm check:watch-hint-literal :: exit 0 pnpm check:skill-frame-freshness (local-only, outside the derivation) :: exit 0 ``` - `check:doc-formula-expressions` first answered exit 3 (PREREQUISITE NOT MET: `@objectstack/formula` and `@objectstack/lint` unbuilt in this worktree). It was built under the shared verify lock (VERDICT command-exit 0) and re-run to exit 0. The exit 3 measured nothing and is not a finding. - Key verdict lines: `check-skill-line-ratchet: .claude/skills/pm-dispatch/references/decision-analysis.md is 50 lines (ceiling 50; headroom 0)`; `check-skill-id-lint: 87 file(s) clean (pattern /#[0-9]{3,}/g)`; `check-skill-frame-sync: the one declared copy of the decision frame is internally coherent`; `check-skill-frame-freshness: the decision frame in this tree is current with origin/main`; `check-nul-bytes: OK`. - `--ran` reconciliation: `17 derived famil(ies) accounted for — 17 run, 0 NOT-MEASURED (a DERIVED zero — all 17 recorded an exit code and none of them is 3)`. - Control-byte self-scan of the changed file: no hits. - No ablation: the diff is agent-protocol prose and changes no tested behaviour. ## Acceptance notes - `.claude/**` is unpublished, so `skip-changeset` is declared with this PR's labels and there is no changeset. - Governed surface, Tier S (`.claude/**`): this PR stays draft for the seat's in-seat contract review. - The commit's trailer pair is the model-free one AGENTS.md prescribes. ## 维护者速读(草稿) - **改了什么:** 决策分析写法的〈应用仓推荐序特例〉一节,写入您 2026-10-18 的原话「平台相关的功能,应该尽量先改平台。」作为总则:属于平台的能力(spec、objectstack 运行时、objectui 渲染器)先在平台做,应用仓(cloud、hotcrm)不自己做替代品,临时过渡只由您明裁。原有「平台缺陷阻塞就等,不绕行、不劈半」一句原样保留,作为总则在被阻塞应用仓卡上的用法。另加两条推论:应用仓临时扩展平台契约,必须在同一次裁决里同时立平台卡与移除卡;从应用仓裁决拆出的平台卡沿用被裁卡的优先级,不降档。 - **为什么改:** 批 362 里几张应用仓卡都可以在应用仓里绕过平台缺口,您都裁为等平台或推动平台修;这句话此前只记在台账里,席位排推荐序时读不到。写进参考文件后,今后同类卡的推荐会默认指向平台,不会出现应用仓先做一个替代品、平台那半张卡却排在后面没人做的局面。 - **风险与代价(含回滚):** 只改一个内部席位读的参考文件,不发版、不影响客户;文件行数 50 → 50,未抬上限,所腾出的行来自文件开头的目录句与重复的适用面小节,内容无丢失。回滚 = 还原这一个提交。 - **席位意见:** - **你要做的:** 无需动作;席位内达档复核通过后由席位落地。如对两条推论的措辞有异议,在卡上一句话说明即可。 --- _Generated by [Claude Code](https://claude.ai/code/session_01QBcLjVCmcWbZEk6qhYMib2)_ Co-authored-by: Claude <noreply@anthropic.com>
1 parent 58a2faa commit baac8e1

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

‎.claude/skills/pm-dispatch/references/decision-analysis.md‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,6 @@
11
# 决策分析写法
22

3-
见 SKILL.md 〈升级与决策〉节的四轴框架;本文只放适用面、批流程与两个固定形状。
4-
5-
## 适用面
6-
7-
- 只约束 `needs-user-decision` 卡与决策箱讨论的四维分析。
3+
四轴见 SKILL.md 〈升级与决策〉;本文只约束 `needs-user-decision` 卡与决策箱讨论的四维分析。
84

95
## 常设决裁批流程
106

@@ -47,4 +43,8 @@
4743

4844
## 应用仓推荐序特例
4945

46+
- 「平台相关的功能,应该尽量先改平台。」(维护者 2026-10-18 逐字,裁决台账 6245607810,批 362)
47+
- 能力先建在平台(spec、objectstack 运行时、objectui 渲染器);应用仓(cloud、hotcrm)不自建替代。
5048
- 阻塞源是平台缺陷 ⇒ 恒荐等待;⛔ 不荐绕行(形状容错、复刻平台规则)、不荐劈半落地。
49+
- 过渡唯维护者明裁;应用仓临时扩展平台契约,仅当平台卡与移除卡同一裁决立出。
50+
- 应用仓裁决立出的平台卡取被裁卡优先级,⛔ 不降档。推论出处:cloud 2932 A、cloud 2924 A。

0 commit comments

Comments
 (0)