Skip to content

pm-dispatch: codify the Class-1 (autonomous-adjudication) qualification into the 代裁通道 — three criteria, per-card recorded basis, batch digest for maintainer 追认 #13066

Description

@os-elon

⚖️ RULED at filing — 2026-08-29, maintainer, live director session (session session_016SG9S6V15MqeAgkehDcTwk), verbatim and untranslated:

把「一类」判据写进代裁通道(skills 席立卡固化)

Issued immediately after the same session's 58-card retrospective, in which the maintainer was presented the three-tier classification below and ordered this codification. This card is the skills-lane execution vehicle: the protocol text change is the deliverable. Filed pm:queue (already ruled — no further adjudication needed before implementation).

What the skill text gains

The 代裁通道 (delegated-adjudication channel) gains a Class-1 qualification gate: during a summons, the director seat may SELF-RULE a decision card without presenting it live, when and only when ALL THREE criteria hold:

  1. 既有裁定/先例/成文纪律机械适用 — an existing maintainer ruling, recorded class rule, or written repo discipline decides the direction; the seat invents no direction, it only applies one. The per-card ruling comment MUST name the specific authority applied (the standing ruling's date/quote, the class rule, or the discipline's home).
  2. 失败方向响亮且可逆 — a wrong call surfaces loudly (refusal, diagnostic, red gate — never silent behaviour drift) and one revert recovers it.
  3. 四类人工地板零移动 — the card moves NONE of: 安全/权限边界 · 已发布契约语义(含 wire 形与产品面方向)· 产品能力取舍 · 门禁强度。 Any touch of these four ⇒ live presentation, whatever criteria 1–2 say.

Mechanics that ship with it (all three are part of the ruling's shape as presented and accepted):

  • Per-card record: every Class-1 self-ruling lands as a ruling comment on the card citing this channel + the authority from criterion 1, then the card transitions per the state machine exactly as a live-ruled card would (the seat-boundary rule stands: 录裁 + 转 pm:queue, ⛔ 不派发).
  • Batch digest for 追认: at the end of each summons, the director presents the maintainer one digest table of all Class-1 self-rulings (card · applied authority · direction), for retroactive confirmation; the maintainer may overturn any line, and an overturn is executed as a fresh ruling comment + state transition on that card.
  • Class-2 (borderline) and Class-3 (floor) stay live: borderline cards (a reportable point attached — e.g. widening a published face additively, adding a gate, a cost unmeasured) and floor cards are presented in batches exactly as today.

Unchanged, restated as hard constraints: the 降档保险丝 governs — below CONTRACT_REVIEW_TIER the channel is skipped entirely and cards wait (existing rule, untouched); the four manual floors are exclusions, not weights; 每批 ≤5 呈报纪律 and the detailed write-up discipline apply to everything still presented live.

Evidence base (recorded here; ⛔ no issue ids go into the skill text — check:pm-skill-id-lint)

The 2026-08-29 director session ruled 58 cards across 12 batches; the maintainer accepted the seat's recommendation unchanged on every card retrospectively classified Class-1 (38 of 58, 66%). The counter-example proving the floors are correctly drawn: one published-contract card (the JSON-authorable function-keys question) is precisely where the maintainer's own input materially improved the ruling (the server-hooks lowering pattern) — floor categories exist because maintainer input changes outcomes there.

Landing notes for the skills lane

  • Single-source discipline: the 代裁通道's 硬门/置信门/人工地板 live in the main file (分诊座位职责 section) per references/lanes/director.md's own pointer (「⛔ 不另抄」) — the Class-1 gate is added THERE; director.md gains at most a pointer word, never a copy.
  • Zero-headroom ratchet: the skills seat prices the lines; the ceiling-raise precedent (maintainer-ruled raises quoted verbatim in the PR, per the gate's own remedy text) applies if needed, citing this card's ruling.
  • Governed surface (.claude/skills/**) ⇒ draft PR, maintainer pinned approval per PD feat: Comprehensive CRM example demonstrating all ObjectStack protocol features #14's amended landing paths.
  • Criteria are written id-free in skill text; the classification evidence stays on this card as the git-history record.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions