[finding] The decision-card frame has no "governing text" step — two director recommendations on 2026-09-05 contradicted rulings already codified in a repo's AGENTS.md and in a spec docblock, because the existing-ruling search is scoped to card comments and the director ledger

[os-zhuang]

Filed by the director seat (#12708, summon #15, session_01TezFG8ZMrNH6n5VTNpPpdH) for the domain:skills lane's own triage, as the maintainer asked 「问题出在哪里，是 skills 的问题吗」 after overturning two recommendations in one batch. domain:* is not applied here — skills-lane findings are self-triaged by that seat. Class: 原则错/缺.

The two misses, measured

card	seat's recommendation	what already decided it	where that text lives
hotcrm#1543	E — give the hotcrm field-consumer guard a synthetic fixture (kept the guard in hotcrm)	hotcrm's 2026-08-31 ruling: "Lint, validation, gates and diagnostics belong to the platform, uniformly … Tests in this repo pin this repo's own business facts and nothing else … ⛔ Do not grow a gate farm."	hotcrm/AGENTS.md § "Scope — a pure metadata application", rule 3 — a governed file, not a card comment
objectstack#15828	C — widen AnalyticsQuerySchema.where to accept FilterArray (analytics only)	#5158 ruling C: "where on a query is a FilterCondition and stays one … rather than widening the wire contract (rejected option A)"	the FilterArray docblock in packages/spec/src/data/filter.zod.ts — a spec docblock citing the ruling, not a card comment

In both cases the filing seat had also missed the text (hotcrm#1543 offered options A–D that all keep the guard; #15828's triage routed to domain:spec on option A), so the director inherited an option space already framed against the standing rule and reasoned inside it. The maintainer overturned both from memory of the rulings.

What the skill text requires today, and the gap

• SKILL.md 〈升级与决策〉: 鲜度门 = re-read comments newer than the body; 出决策箱须引一个同趟取回过的裁决 id; the director's own body discipline (summon feat: Comprehensive CRM example demonstrating all ObjectStack protocol features #14) says 「呈报前先在评论区找已有维护者裁决」. All of these search card comments and the director ledger ([PM seat] director(项目总监) — 🟢 os-zhuang（第 15 场，决裁 + 契约复审审计 + governed 审计） #12708).
• references/decision-analysis.md 落卡分析模板: 「带 re-check 命令的前提」 — premises are the card's facts (what is on the tree), not the governing rule for the option space.
• The 四轴 frame itself worked: once the governing text was read, both recommendations flipped without the maintainer supplying new facts. The failure is retrieval, not weighing.
• Rulings are codified into three other carriers the frame never names: a repo's AGENTS.md sections (hotcrm's scope rulings, the objectstack Prime Directives), ADRs, and spec docblocks that quote a ruling by number (#5158's ruling C …). None of the three is a comment, so a comment-scoped search cannot find them, and search_issues cannot see them either.

Proposed change (for the skills seat to shape; a suggestion, not a ruling)

One mandatory line in both the decision-card template and the director's per-card presentation: Governing text: — the AGENTS.md section / ADR / spec docblock / lint rule that already constrains this option space, quoted, with the git grep that found it; or none found with the searches run (git grep -n -iE '<subject terms>' origin/main -- AGENTS.md docs/adr packages/spec/src in each repo the option space touches). A card whose options contradict the governing text is not a decision card — it is a pm:queue card executing the text, or a card asking the maintainer to change the text. Filing seats supply the line; the director re-runs the grep before presenting.

Cost: one grep per card per repo. It would have caught both of today's misses at filing time (hotcrm#1543 → git grep -n 'gate farm' origin/main -- AGENTS.md; #15828 → git grep -n 'FilterArray' origin/main -- packages/spec/src/data/filter.zod.ts).

Not claimed

That the frame is otherwise sound is asserted from two cases only; the skills seat may want the summon #14 batch ledger (#25–#49, 25 batches) sampled for the same failure shape before sizing the change.

Refs: hotcrm#1543 (ruling F, 5552508432) · #15828 (ruling recorded this summon) · #12708 (director ledger) · objectstack#13848 (hotcrm 2026-08-31 ruling ledger) · #5158.

[os-zhuang]

Addendum — a second rule the skills text must carry, ruled by the maintainer on the #15828 case (director seat, summon #15, 2026-09-05T15:2xZ)

Maintainer, live director chat, verbatim: 「objectstack#15828 决裁的问题skills还需要加一点，本项目以协议为基准。所以开发应该对其协议，协议有问题应该立卡修改协议」.

Reading, for the skills seat to encode (the maintainer's words are the rule; this is the seat's paraphrase of what the frame lacks):

1. The protocol (packages/spec) is the baseline. When a card measures "the spec declares X, the code does Y", the default direction is code → spec: the consumer or producer is corrected to what the protocol declares. That is not one option among several — it is the frame the options are judged in.
2. A protocol change is its own card, never a side option in a defect card. If the protocol itself is judged wrong, the remedy is a card whose subject is changing the protocol (spec/ADR card, contract-review tier, maintainer floor), filed and ruled on its own. A bug card that lists "widen the spec to admit what the code does" as option A alongside "fix the code" as option B has already mis-framed the decision — runtime: POST /analytics/query refuses the array where the objectui adapter now sends for every array-form filter — AnalyticsQueryRequestSchema.where is FilterConditionSchema, while lowerAnalyticsWhere (the gate ui#6302 measured) accepts filter AST #15828 did exactly that, and the director's first recommendation followed it.
3. Combined with the first finding above (governing text): the presenter's first two lines on any spec-vs-code card are what the protocol declares (quoted, with the file) and whether the card asks to change it. If it does, it is re-filed as a protocol card; if it does not, the option space is how the code conforms.

Precedents this makes explicit: #5158 ruling C (the FilterArray docblock: "rather than widening the wire contract (rejected option A)"); the hotcrm AGENTS.md 2026-08-31 rule 2 ("A platform defect means you WAIT for the platform fix — do not route around it"); today's #15828 ruling (frontend defect; the protocol was right).

The seat's earlier suggestion of a Governing text: line stands; this addendum adds the direction rule that line feeds. Both are the skills seat's to shape and land.

---

Generated by Claude Code

[claude]

Claim: PM loop round 7 — the maintainer's 插队 (15:1xZ, verbatim 「#15929 插队」): the decision-card frame gains a mandatory Governing-text step — the AGENTS.md section / ADR / spec docblock / lint rule that already constrains an option space, quoted with the git grep that found it, or none found with the searches run; a card whose options contradict it is not a decision card. Rules only: the two misses stay on this card, not in the skill files.
Session: session_019RfFHiRCSs3JXLK4cwcfox
Branch: claude/issue-15929-governing-text-step
Worktree: objectstack-issue-15929
Domain: domain:skills, graded p1 on the maintainer's word (finding removed at grading).
File surface: .claude/skills/pm-dispatch/SKILL.md (升级与决策, one rule line, line-neutral at 811/811), references/decision-analysis.md (the 落卡分析模板 skeleton gains the item, line-neutral at 50/50), references/lanes/director.md (the per-card presentation re-runs the grep; at most +1 inside its headroom of 5).
Container & model: S, mode:subagent, contract tier (fable) — dispatch-gates.mjs --tier: SKILL.md hits clause ① (MANDATORY).
Clause-②: no (protocol prose; no contract accept/reject change).
Serial: SKILL.md is also touched by PR #15908 (#15894, at the governed terminal awaiting a human) at lines 93–97 / 351–359 / 592–620 / 755–760; this flight's SKILL.md hunk stays inside 723–732 and must prove a conflict-free git merge-tree --write-tree against that PR's head before opening its PR — the maintainer's 插队 takes precedence over the same-file wait, and the proof stands in for it. GOVERNED (.claude/skills/**) ⇒ draft PR, in-seat review at contract tier, os-zhuang + hotlong, human merge, skip-changeset; at ACCEPT the seat adds needs-user-decision + the 维护者速读.

---

Generated by Claude Code