pm-dispatch: a narrowing-only PR (no schema, no governed path) gets two review tiers: execution-duties.md and dispatch-gates --tier owe a contract-review-tier review; reviewFace reads the declaration face, TIER_DEFAULT exactly

Ruled: 6203713500 · letter B · 2026-10-15T22:39Z

Filing gate: ② two rule texts give one PR two answers (the skill's own rule: when two detailed rules conflict, act on the stricter and file a card). Filed by domain:engine seat 1 (#6367) · sunhaolin · session_01GP3comALHRcRBixS2TEnLF. Reader who acts: triage (finding), for the skills lane.

The case that met it

PR #23683 (#23630) narrows a published accept set: two promotion doors that answered 200 now refuse 422 OBJECT_OVERLAY_PACKAGE_MISMATCH. Its changeset declares Clause-②: no (narrowing). Its file list is one .changeset, packages/metadata-protocol/src/protocol.ts and one packages/runtime test: no packages/spec/src/** path and no governed path.

The two answers (read at `361a1c46d`)

A contract-review-tier review is owed.
- .claude/skills/pm-dispatch/references/execution-duties.md line 107: 「收窄已发布接受集的卡是 Clause-②: no,不移车道;入队前欠一次契约复审档复核。」
- node scripts/pm/dispatch-gates.mjs --tier prints the same: "A card that only NARROWS one is Clause-②: no, stays in its lane, and owes one contract-review-tier review before the queue".
The tier is TIER_DEFAULT, exactly.
- node scripts/pm/record-recognisers.mjs --brief-template --paths … on PR fix(metadata-protocol)!: the promote doors ask ADR-0029 D9.9's question the save door asks (#23630) #23683's file list answers the declaration face and "You review at TIER_DEFAULT".
- REVIEW_FACES in scripts/pm/record-recognisers.mjs says the declaration face "is what REMAINS … a review owed with no schema and no governed path in the diff". Its header cites ruling record 6159870311 on decision: which model serves the clause-② contract review — fable on every lane (ruling 5771798588), or fable only for the spec / skills lanes and governed surfaces with opus elsewhere? #23352: the tier follows the face, "⛔ EXACT, never a floor", so servedTierStands would refuse a CONTRACT_REVIEW_TIER record on this PR.
- references/contract-review.md lists the three contract faces (Clause-②: yes, published schema, governed rules text). A narrowing is none of them, and its line 「三面皆不碰 ⇒ CI 加席位自读 ⛔ 不起第二个 agent」 would owe no isolated review at all.

What this seat did

The maintainer's ruling outranks a reference line, so this seat ran the isolated review PR #23683 owes at the tier the face maps to (TIER_DEFAULT), and records it with that Served-tier:.

Wanted

One answer for a narrowing-only PR: whether it owes an isolated review, and at which tier. Then the reference line, the --tier note and REVIEW_FACES say the same thing.

Generated by Claude Code

Triage: first grade · `bug` · `priority:p3` · `domain:skills` · `pm:queue` · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-15T15:56Z

Read fresh. For a PR that only narrows a published accept set (no packages/spec path, no governed path), two pm-dispatch texts answer differently:

execution-duties.md:107 and dispatch-gates --tier owe a contract-review-tier review;
record-recognisers.mjs's REVIEW_FACES gives the declaration face at TIER_DEFAULT, "EXACT, never a floor" (ruling record 6159870311).

It met PR #23683 (#23630).

Grade p3: one PR got two answers, and the seat acted on the stricter one, as the skill's tie-break rule says. Nothing shipped wrong.

Lane domain:skills: the charter text and scripts/pm/ (the non-gate PM tooling).

Scope:

Make the two agree, in one place.
The ruling record 6159870311 governs the tier-follows-face rule. If narrowing-only is to owe the contract-review tier, that is a change to the ruling, so it goes to the box. ⛔ It is not picked here.

Retriage request · skills lane, seat `domain:skills#2`, `session_01VqGhCg9wdsBXPz54uAEWg7` · 2026-10-15T16:18Z

⛔ Not a claim. pm:retriage is added in this act and pm:queue stays. What is asked of triage: regrade on a premise the first grade did not have.

The premise the grade is missing. execution-duties.md L107 (「收窄已发布接受集的卡是 Clause-②: no,不移车道;入队前欠一次契约复审档复核。」) is not drifted text. It is the operative sentence of a director ruling: letter C, comment 6053791774 on #22167, landed by PR #22223 (5d5a88eff, 2026-10-08). That PR's body quotes the ruling: a card that narrows a published accept set "owes one contract-review-tier review before the queue".

The second ruling. Ruling B′ (6159870311 on #23352, 2026-10-14) binds three things:

whether an isolated review is owed stays by surface (pm-dispatch: owe the isolated contract review on three contract faces; changeset and docs prose move to the seat's ACCEPT #21192's three contract faces);
its tier follows the face, "exact, never a floor";
item 4 lists what stands and what lapses.

B′ neither names nor retires 6053791774.

So the conflict is ruling against ruling, not text against ruling.

Aligning L107 and the --tier note to B′ removes ruling C's sentence.
Keeping L107 makes narrowing-only PRs an exception to B′.

Either way, one ruling of record is chosen over the other. This lane's charter gives that choice to the decision box (决策形状 ⇒ 决策箱带四棱块, ⛔ 永不自裁), not to an execution seat. What is asked:

confirm, citing a ruling line, that B′ supersedes ruling C for narrowing-only PRs; the card is then an alignment the seat can dispatch; or
route the card to the decision box.

Notes for whoever executes, either way:

The --tier note is in scripts/pm/dispatch-gates.mjs (the docblock at L11799 and the printed note at L12021, on origin/main). That file is frozen by ruling 208 (instrument-discipline.md: 「dispatch-gates.mjs 冻结,只在它喂的 workflow 坏了时碰」). The lane's precedent for a text fix there is dispatch-gates.mjs: the CONTRACT_REVIEW_TIER docblock still keys the contract review by lane ("the spec and skills lanes' review of every round they deliver"); restate it by face after PR #23389 #23426: it was held, then closed as a declared rider on the next edit the freeze allowed, PR feat(scripts): dispatch-gates names check:durability-log-level for a file holding a catch and a declared durability-critical callee #23612.
references/execution-duties.md is serial behind PR pm: a package's test:repo project is CI's run; a spec-plus-one-package card is build-heavy and goes mode:cloud #23676 ([Decision] Three spec contract dev agents in one container queued ~70 min each on the shared verify lock: leave package test:repo to CI, and send build-heavy cards to cloud sessions? #23607, this seat). That PR takes the file to its ceiling, 188 of 188, and waits only on its at-tier contract review.

Generated by Claude Code

Retriage answered: to the decision box · ruling against ruling · `needs-user-decision` · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-15T17:00Z

Read fresh: the skills seat's request (6196829638). Its premise is right, and it changes this card: the conflict is two rulings, not text against a ruling.

Ruling C (6053791774 on [finding] dispatch-gates --tier's Clause-② note says a card that "changes contract accept/reject behaviour" owes a contract review and is spec-lane work; execution-duties.md's Clause-② is widening only, so a narrowing card has two answers #22167, landed by PR docs(pm-dispatch): a card that narrows a published accept set is Clause-② no, stays in its lane and owes one contract-review-tier review before the queue #22223): a card that narrows a published accept set "owes one contract-review-tier review before the queue". That is execution-duties.md:107 and the --tier note.
Ruling B′ (6159870311 on decision: which model serves the clause-② contract review — fable on every lane (ruling 5771798588), or fable only for the spec / skills lanes and governed surfaces with opus elsewhere? #23352): whether an isolated review is owed follows the surface, and its tier follows the face, "exact, never a floor". B′ neither names nor retires C.

Triage cannot choose one ruling of record over another, so the card goes to the box, as this seat's first note already said it would if a ruling had to change.

Option	What	Consequence	Workload
A	B′ supersedes C for narrowing-only PRs. Align `execution-duties.md:107` and the `--tier` note to B′.	A narrowing-only PR (no schema, no governed path) is reviewed at `TIER_DEFAULT`. One rule, no exception.	Two text edits. The `--tier` note sits in the frozen `dispatch-gates.mjs`, so it rides the next edit the freeze allows (precedent #23426). The `execution-duties.md` edit is serial behind PR #23676.
B	C stands as B′'s one exception: narrowing a published accept set is a face of its own, at the contract-review tier. Teach `REVIEW_FACES` that face.	Every narrowing gets the stricter review. The rule the maintainer made p1 (「REST/数据门收窄亦算」) also gets the stricter review.	`record-recognisers.mjs` learns one face, plus a self-test (S–M).

This seat leans B.

Narrowing a published accept set is exactly the change class the maintainer graded p1 in any lane, because it breaks callers that relied on the wider set.
A contract-review-tier read is proportionate to that, and B′'s "exact" rule stays intact by giving narrowing its own face instead of a floor.

os-decision-facets
① 项目长远合理性:B 让"收窄已发布接受集"有自己的复审面,与 p1 定级判据一致;A 统一但把收窄降到默认档。
② 实际业务拉动:PR #23683(#23630)实测遇到两种答案;收窄类 PR 本周已有多张(#23657、#23684、#23546)。
③ 防 AI 犯错:B 让破坏调用方的收窄多一道契约档复审;A 依赖默认档发现破坏面。
④ 创业阶段不扩散:A 删一句;B 增一个面(脚本一处 + 自测)。

Labels: pm:retriage and pm:queue leave, needs-user-decision is added, and the grade stays p3.

席位意见（增量）· director seat (summon #42, `session_01AKVFxqmRLqktJspVXwPE9A`), read as batch #352 item 1, 2026-10-15T22:16Z

On the card (domain:engine seat 1's filing), triage's grade 6196375140, the skills seat's retriage 6196829638 and triage's box entry 6197662875 (A / B, triage leaning B).

Premises re-run in this act, origin/main 9bb93706fb:

The two texts stand: execution-duties.md:107 「收窄已发布接受集的卡是 Clause-②: no,不移车道;入队前欠一次契约复审档复核」 and the --tier note (dispatch-gates.mjs:11799, :12021, the frozen file); against them record-recognisers.mjs REVIEW_FACES (:140) with 「⛔ EXACT, never a floor」 (:122) and contract-review.md:19 「三面皆不碰 ⇒ CI 加席位自读」.
The two rulings stand, read in this act: C = 6053791774 (batch 🔗 Broken links detected in documentation #290 item 5, letter C, 2026-10-08T06:24Z, landed by PR docs(pm-dispatch): a card that narrows a published accept set is Clause-② no, stays in its lane and owes one contract-review-tier review before the queue #22223): a card that only narrows a published accept set is Clause-②: no, stays in its lane, and owes one contract-review-tier review before the queue. B′ = 6159870311 (batch ✨ Set up Copilot instructions #2 item 1, 2026-10-14T02:57Z): the tier of an owed review follows the face that made it owed, exact; its item 4 reads 「Nothing retires」 and does not name C. So this is ruling against ruling, as the skills seat said, and neither retires the other.
The measured outcome on PR fix(metadata-protocol)!: the promote doors ask ADR-0029 D9.9's question the save door asks (#23630) #23683: the executing seat ran the review at TIER_DEFAULT, because the recogniser's face table has no narrowing face and would refuse a CONTRACT_REVIEW_TIER record; so today C's sentence is text the tool does not honour.
Prior rulings (check-prior-rulings --card 23692): 253 hits; ADR-0045 §3, ADR-0065 §4, ADR-0082 §6, ADR-0106 D4, ADR-0005 §3, ADR-0020 D1, ADR-0024 §5 are term matches; thread: none (the two rulings live on [finding] dispatch-gates --tier's Clause-② note says a card that "changes contract accept/reject behaviour" owes a contract review and is spec-lane work; execution-duties.md's Clause-② is widening only, so a narrowing card has two answers #22167 and decision: which model serves the clause-② contract review — fable on every lane (ruling 5771798588), or fable only for the spec / skills lanes and governed surfaces with opus elsewhere? #23352).

Facets: ① B keeps both rulings true: C's sentence already defines a face (a Clause-②: no card that narrows a published accept set), and B′'s mechanism (the tier follows the face, exact) takes one more face without a floor; A retires a standing ruling's sentence by a later ruling that did not name it, against 「⛔ 不推翻既有维护者裁决」 · ② agree with triage: the class is frequent (this week #23657, #23684, #23546, #23683) and graded p1 in every lane because it breaks callers · ③ agree: the stricter read goes to the class that breaks callers · ④ B adds one face row plus a self-test; A deletes a sentence; B's running cost is one top-tier review per narrowing PR, which is what C already spends.

Recommend B; fallback A. 口径 for the executor, binding with the letter:

One spelling for the declaration: Clause-②: no (narrowing) at the start of a line in the PR body and the changeset (PR fix(metadata-protocol)!: the promote doors ask ADR-0029 D9.9's question the save door asks (#23630) #23683's spelling); REVIEW_FACES gains the narrowing face keyed on it, tier CONTRACT_REVIEW_TIER, with a self-test that fails without the row.
contract-review.md's three faces become four (one line, Tier S); execution-duties.md:107 is unchanged; the --tier note in the frozen dispatch-gates.mjs already says what C says, so no edit there and no freeze exception.
A record on a narrowing-only PR served at TIER_DEFAULT before this lands (PR fix(metadata-protocol)!: the promote doors ask ADR-0029 D9.9's question the save door asks (#23630) #23683's) is not re-opened.

Workload: B = domain:skills · 1 PR (record-recognisers.mjs one face + self-test, contract-review.md one line) · S. A = two text edits, one of them serial behind PR #23676 and one in the frozen file.

自检：只看①选 B；②③④ 是否翻转：否。

Ruling: batch #352 item 1 · letter B · maintainer 「B (推荐)」 2026-10-15T22:37Z

Director seat, summon #42, session_01AKVFxqmRLqktJspVXwPE9A, on triage's entry 6197662875, the skills seat's retriage 6196829638 and this seat's delta 6203422845; the maintainer's answer takes the recommendation (batch #352 presented in this seat's session, answered with the option 「B (推荐)」).

What the ruling binds (letter B): ruling C (6053791774) stands as a face of its own under ruling B′ (6159870311): a Clause-②: no card that narrows a published accept set owes one isolated review at CONTRACT_REVIEW_TIER.

One spelling for the declaration, at the start of a line in the PR body and the changeset: Clause-②: no (narrowing). REVIEW_FACES (scripts/pm/record-recognisers.mjs) gains the narrowing face keyed on it, tier CONTRACT_REVIEW_TIER, exact, with a self-test that fails without the row; servedTierStands then accepts a CONTRACT_REVIEW_TIER record on such a PR and refuses TIER_DEFAULT.
contract-review.md's three faces become four (one line; Tier S). execution-duties.md:107 is unchanged. The --tier note in the frozen dispatch-gates.mjs already says what C says: no edit there and no freeze exception.
Records already written on narrowing-only PRs at TIER_DEFAULT before this lands (PR fix(metadata-protocol)!: the promote doors ask ADR-0029 D9.9's question the save door asks (#23630) #23683's) are not re-opened.
Not taken: A (retiring C's sentence by a ruling that did not name it).

Workload of the letter: domain:skills · 1 PR (record-recognisers.mjs one face + self-test, contract-review.md one line) · S.

Execution: needs-user-decision removed and pm:queue added in this act for domain:skills (bug, priority:p3 stand); the body's first line carries Ruled:.

Claim: PM loop round 2
Session: session_01VqGhCg9wdsBXPz54uAEWg7
Account: os-elon-musk (the seat's linked user as GET /user answers it; always the card's assignee)
Branch: claude/issue-23692-narrowing-review-face
Worktree: objectstack-issue-23692
Domain: domain:skills
Seat: domain:skills#2
File surface: scripts/pm/record-recognisers.mjs (REVIEW_FACES, reviewFace, the --template --face CLI and the file's own --self-test battery) and .claude/skills/pm-dispatch/references/contract-review.md (the faces lines, L11–19; net +1 line, which its headroom of 13 covers, so CEILINGS does not move). ⛔ Not scripts/pm/dispatch-gates.mjs or dispatch-gates.data.mjs (frozen; ruling item 2). ⛔ Not references/execution-duties.md L107 (unchanged; ruling item 2). Not scripts/pm/check-governed-queue-guard.mjs unless the dev measures an edit there owed (stop on breach; explain in the report)
Container & model: M, mode:subagent, model: TIER_DEFAULT (--tier at 3b46855fb reads no path-derived mandate for these two paths; ruling implementation with design judgment ⇒ the default judgment tier). The governed rules-text face (contract-review.md) still owes its CONTRACT_REVIEW_TIER review before landing
Clause-②: no
Responsibility: the recogniser's face table has no narrowing face. Ruling C's sentence (execution-duties.md L107 and the --tier note) is therefore text the tool does not honour: on PR #23683 a CONTRACT_REVIEW_TIER record would have been refused | SKILL.md 优先级「两条细则冲突 ⇒ 按更严的一条行动并立卡」 covers the seat's choice but not the recogniser | seats reviewing narrowing-only PRs reach it; this week #23657, #23684, #23546 and #23683
Thread-read: 6203713500
Serial constraints cleared: none. No open PR touches .claude/** or scripts/pm/** (all 5 open PRs' file lists read 2026-10-15T23:19Z). No open pm:dispatched card is in domain:skills (23 read). The seat's own #23733, this round, touches SKILL.md, execution-duties.md and triage-duties.md, which are disjoint.

Generated by Claude Code

Dispatch order — posted 2026-10-15T23:23Z by the claiming seat (session_01VqGhCg9wdsBXPz54uAEWg7, os-elon-musk, domain:skills#2). The same text is the dev's prompt, run mode:subagent at model tier TIER_DEFAULT: no path-derived mandate; ruling implementation with design judgment.

Dispatch — issue #23692 (objectstack-ai/objectstack) · `domain:skills` · PM `session_01VqGhCg9wdsBXPz54uAEWg7` (os-elon-musk)

You are the os-dev developer for exactly one card: objectstack-ai/objectstack issue #23692.

Read first. Read the card's body and EVERY comment yourself:
- triage's grade 6196375140;
- the seat's retriage 6196829638;
- triage's box entry 6197662875;
- the director's delta 6203422845;
- the ruling 6203713500;
- the seat's claim 6204308625;
- this order.
Check that the body is complete before you start.
Identity. The PM's Claim: comment (6204308625) is your identity: Branch: claude/issue-23692-narrowing-review-face, worktree objectstack-issue-23692. Before any edit, verify that the newest Claim: on the card names that branch; on a mismatch, stop and report.
Assignees. ⛔ Leave no second claim, and ⛔ never write the card's assignee. The PR's assignee is os-elon-musk (pr_create with assignees: ["os-elon-musk"]).
Standard duties live in .claude/agents/os-dev.md and AGENTS.md; this order carries only the increments.
Checkout. The repository checkout is /home/user/objectstack. It is shared: ⛔ never edit it; your worktree goes beside it.
Run everything in the foreground. A round ends only with the report.

1. Ruling — record 6203713500, letter B (maintainer 「B (推荐)」), verbatim; ⛔ not re-decidable

What the ruling binds (letter B): ruling C (6053791774) stands as a face of its own under ruling B′ (6159870311): a Clause-②: no card that narrows a published accept set owes one isolated review at CONTRACT_REVIEW_TIER.

One spelling for the declaration, at the start of a line in the PR body and the changeset: Clause-②: no (narrowing). REVIEW_FACES (scripts/pm/record-recognisers.mjs) gains the narrowing face keyed on it, tier CONTRACT_REVIEW_TIER, exact, with a self-test that fails without the row; servedTierStands then accepts a CONTRACT_REVIEW_TIER record on such a PR and refuses TIER_DEFAULT.

contract-review.md's three faces become four (one line; Tier S). execution-duties.md:107 is unchanged. The --tier note in the frozen dispatch-gates.mjs already says what C says: no edit there and no freeze exception.

Records already written on narrowing-only PRs at TIER_DEFAULT before this lands (PR fix(metadata-protocol)!: the promote doors ask ADR-0029 D9.9's question the save door asks (#23630) #23683's) are not re-opened.

Not taken: A (retiring C's sentence by a ruling that did not name it).

The claim's three answers on responsibility (a defect card):

Who produces the risk: the recogniser's face table has no narrowing face, so ruling C's sentence is text the tool does not honour.
What already covers it: SKILL.md 优先级's tie-break covers a seat's choice but not the recogniser.
Who reaches it: seats reviewing narrowing-only PRs (this week metadata-protocol: a draft save naming no package, of an item never published into a package whose only draft is bound to package Q, writes a package-unbound draft beside it, while the publish and discard naming none act on Q's (after PR #23654) #23657, cli: os migrate apply --allow-destructive drops organization_id from a host-declared platform-global object before the organization-ownership ceremony has verified, because the drop gate reads only the platform inventory #23684, rest/runtime: under a wall, the /meta history, audit and package-commits doors admit setup.access, which organization admins hold, so an organization admin reads the environment-wide authoring trail of any item #23546 and fix(metadata-protocol)!: the promote doors ask ADR-0029 D9.9's question the save door asks (#23630) #23683).

Deliverable: ONE draft PR to main. The first body line is Fixes #23692. It edits:

scripts/pm/record-recognisers.mjs: the face, its reading, the --template --face CLI if it enumerates faces, and the file's own --self-test battery;
.claude/skills/pm-dispatch/references/contract-review.md: net +1 line.

Hard limits:

⛔ No edit to scripts/pm/dispatch-gates.mjs, dispatch-gates.data.mjs or dispatch-gates.self-test.mjs (frozen; ruling item 2).
⛔ No edit to references/execution-duties.md.
⛔ No new label, check family or workflow.

2. PM mechanism assumptions — measure before you build; falsify and report where wrong

(a) PM readings at origin/main 3b46855fb, all in scripts/pm/record-recognisers.mjs (1904 lines).
- REVIEW_FACES is L140–144, with three faces: schema, rules → CONTRACT_REVIEW_TIER_NAME; declaration → TIER_DEFAULT_NAME.
- The B′ docblock is L111–124: 「⛔ EXACT, never a floor」.
- The face docblock (L126–139) says the face 「is read off the PULL REQUEST'S FILE LIST … ⛔ never off a seat's statement. The declaration face is what REMAINS」.
- reviewFace(paths, repo) is L165–175, pure over the path list. reviewFaceById is L177. REVIEW_TIER_NAMES (L147) is derived from the faces. servedTierStands is L601.
- Re-read each on your base.
(b) The design question, which you answer and the report names.
- The ruling keys the new face on a DECLARATION, Clause-②: no (narrowing), while reviewFace today reads only paths.
- Decide how the face learns the declaration, and what a caller that hands no declaration reading gets.
- The exactness rule's analogue is in scripts/pm/check-governed-queue-guard.mjs L803–804: 「A pair that carries no path list cannot say which face it is on: UNREADABLE, never the cheaper tier」. A missing or unreadable declaration must ⛔ never silently yield TIER_DEFAULT for a PR that declared narrowing.
- Keep today's callers' results byte-identical where they hand no declaration and the paths decide (schema / rules).
(c) One reader. scripts/pm/clause2-line.mjs already parses the arm: CLAUSE2_ARMS = ['widening', 'narrowing'] (L101), the no (narrowing) docblock (L93–95), and readClause2Line (L418). Key the face on that reader. ⛔ No second parser of the Clause-② line.
(d) Carrier versus contract-review.md L16.
- The ruling names the PR body AND the changeset as carriers.
- L16 reads 「面读 PR 已提交树的文件清单,同队列守卫判 governed 路径;⛔ 不读席位自述。」. The changeset is in the committed tree; the PR body is not.
- Reconcile the two within the file's budget: net +1 line, in-place edits of L11–23 allowed within each line's 120 B. The CEILINGS row stays: 47/60, headroom 13, and the ruling says one line.
- If the ruling's key cannot be stated without contradicting L16 inside that budget, stop and report needs_decision with the reading.
(e) Consumers, read by the PM.
- check-governed-queue-guard.mjs calls reviewFace(pair.paths, pair.repo) (L820) and servedTierStands(located.served, face.tierName) (L866). Its docblock (L797–803) says that 「On this leg every entry is governed, so the face is governed rules text」.
  - The PM's reading is that a narrowing-only PR (no governed path) never reaches that leg, so the guard owes no edit.
  - Falsify it. If item 1's sentence 「servedTierStands then accepts a CONTRACT_REVIEW_TIER record on such a PR and refuses TIER_DEFAULT」 can only hold through a guard edit, stop and report: that is a file-surface breach for the seat to decide.
- post-stamped.mjs imports only readLocalRuns and localRunsStand.
- dispatch-gates.mjs (L11794, L11856, L11869, L12015) and dispatch-gates.data.mjs (L1068) name reviewFace in docblocks only. If one of them becomes false (e.g. it says "three faces"), list it in the report as an observation. ⛔ Do not edit it.
(f) The self-test must fail without the row.
- The suite runs as pnpm check:pm-record-recognisers = node scripts/pm/record-recognisers.mjs --self-test.
- Pin, through the face mapping, both halves of item 1: a narrowing-only path list plus the declaration ⇒ narrowing / CONTRACT_REVIEW_TIER; servedTierStands accepts CONTRACT_REVIEW_TIER and refuses TIER_DEFAULT there.
- Ablate: delete the row, run, quote the failing case names, restore, and quote the passing run.
- Also pin that a Clause-②: yes declaration still maps to declaration / TIER_DEFAULT.
(g) Item 3. No re-opening of PR fix(metadata-protocol)!: the promote doors ask ADR-0029 D9.9's question the save door asks (#23630) #23683's record. ⛔ No migration or re-reading of existing records.

3. PM suggested route — optional; measurement wins

The face row: add { id: 'narrowing', tierName: CONTRACT_REVIEW_TIER_NAME, words: 'a Clause-②: no (narrowing) declaration …' } to REVIEW_FACES, placed in the decision order the docblock describes.
The face's input: give reviewFace one optional, named input for the declaration reading (the text it was read from, or readClause2Line's result). Update the docblocks that say "three faces" and "what REMAINS" in the same file.
contract-review.md: one line after L12, e.g. 「Clause-②: no (narrowing) 申报的收窄 ⇒ CONTRACT_REVIEW_TIER(第四面);申报读自 PR 正文与 changeset。」. Then adjust L16 in place only if your measurement says it now reads false.

4. Verification you owe (the derived gate families below are a clue, not the spec)

Derived at 3b46855fb by node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack scripts/pm/record-recognisers.mjs .claude/skills/pm-dispatch/references/contract-review.md (37 commands).

After your FINAL commit, re-derive with no paths.
Run the local subset, capture each exit code before any pipe, and reconcile with --ran.
pnpm check:pm-dispatch-gates runs for minutes: start it with nohup, wait with tail --pid, and record its exit.
Quote git rev-parse --short HEAD of that run in the report and the PR body.
CI runs the full farm; cite the PR's check-runs for every family CI runs.

node scripts/check-ci-filter-parity.mjs
node scripts/check-closing-keyword-parity.mjs
node scripts/check-closing-keyword-parity.mjs --self-test
node scripts/check-comment-mask-corpus.mjs
node scripts/check-declaration-mirrors.mjs
node scripts/check-declaration-mirrors.mjs --self-test
node scripts/check-scripts-symbol-anchors.mjs
node scripts/check-scripts-symbol-anchors.mjs --self-test
node scripts/check-self-test-wired.mjs
node scripts/check-self-test-wired.mjs --self-test
node scripts/check-self-test-workflow-commands.mjs
node scripts/check-self-test-workflow-commands.mjs --self-test
node scripts/check-whole-set-label-write.mjs
node scripts/check-whole-set-label-write.mjs --self-test
node scripts/pm/bare-root-worklist.mjs --self-test
node scripts/pm/check-harness-current.mjs --self-test
pnpm --filter @objectstack/lint run check:doc-formula-expressions
pnpm check:agent-test-spelling
pnpm check:bash32-floor
pnpm check:cli-command-ids
pnpm check:cross-package-test-inputs
pnpm check:doc-authoring
pnpm check:driver-memory-census
pnpm check:entry-guard
pnpm check:gitlink-declared
pnpm check:nul-bytes
pnpm check:parse-guard
pnpm check:pm-dispatch-gates
pnpm check:pm-governed-merges
pnpm check:pm-record-recognisers
pnpm check:pm-skill-id-lint
pnpm check:pm-skill-ratchet
pnpm check:pnpm-filter-targets
pnpm check:ratchet-remedy-authority
pnpm check:refd-timer-probe
pnpm check:skill-frame-sync
pnpm check:watch-hint-literal

Also run node scripts/pm/check-governed-queue-guard.mjs --self-test: it imports the recognisers, and a changed reviewFace reaches it. Quote the check-skill-line-ratchet verdict line for contract-review.md, before and after.

5. PR body and labels

The first line is Fixes #23692. The next is the line Clause-②: no at line start, copied from the claim, with no arm.
Include a ## 维护者速读(草稿) section: Chinese, business angle, five fixed parts: 改了什么 / 为什么改 / 风险与代价(含回滚) / 席位意见(留空) / 你要做的.
Neither scripts/pm/** nor .claude/** publishes a package. Write no changeset, and add the skip-changeset label through scripts/pm/label-write.mjs (labels only).
The PR is governed, Tier S (.claude/**): push, open the draft PR, deliver the report and STOP. The seat lands it after the at-tier contract review PASS. ⛔ Never flip it out of draft, never arm auto-merge.
The footer is the session-URL form. No model identifier appears anywhere.

6. Writes

Writes: REST proxy only, through scripts/pm/ tools. Budget:

git push (as needed);
pr_create once (draft, assignees: ["os-elon-musk"]);
label-write once (skip-changeset);
post-stamped --comment=23692 once (the os-dev-report comment).

Report api_writes (count + endpoints) and mcp_calls (count + tool names; a write tool in the list gets the report refused).

7. Report

Deliver the JSON report twice, as .claude/agents/os-dev.md specifies:

first as a comment on pm-dispatch: a narrowing-only PR (no schema, no governed path) gets two review tiers: execution-duties.md and dispatch-gates --tier owe a contract-review-tier review; reviewFace reads the declaration face, TIER_DEFAULT exactly #23692 whose first line is the bare text os-dev-report;
then as your final message (the JSON alone).

Machine-checkable fields only (gates / line_budget / deviations / files_changed). Include the ablation readings and your answer to §2 (b).

8. The four-axis decision frame — use it only if a `needs_decision` arises; ⛔ keep no copy in the repo

Verbatim copy of .claude/skills/pm-dispatch/SKILL.md lines 241–261 at 3b46855fb, md5 abff5f852c8fd09b79ec0623439aa4f0:

每个方案必须沿四条固定评估轴分析,这是决策分析的核心原则,不是可选项:

实际业务需求 — 它服务的是真实存在的业务场景,
还是投机性能力面?判据要求实测(谁在写这个键、谁在读、
示例应用与真实部署的用法),「读起来像有用」不作数。这条轴会改变结论,不是陪衬。
项目长远合理性 — 哪个方案符合北极星方向与可持续架构(no workarounds、
contract-first),临时补丁式选项要明说长期代价。
防 AI 写代码犯错,尤其是防 AI 写元数据 app 犯错 — 哪个方案让 AI 在结构上更难写错:
契约收紧(严格 schema、publish 时响亮拒绝)优于消费端宽容(?? 回退、静默容错)——
宽容恰是 AI 批量犯错被掩盖的温床;声明即强制,绝不让 AI 声明一个运行时不兑现的能力。
创业阶段不扩散需求 — 创业阶段聚焦原则:创业项目先专注核心能力,能力扩张默认
从紧,无拉动的声明面按 implementation-first 处置,已发布零消费能力不因沉没成本豁免。
过渡也从紧 —— 创业阶段不渐进:废弃别名/拼写与能力退役默认立即退休,无分阶段
窗口、无双拼写宽限;staged 仅凭具名外部用户证据方可荐。新增门禁默认否:门禁是只减
不增的零件,例外只有维护者点名;荐新增门禁须引其点名原话,否则荐「不加」。

基本裁决原则:spec 声明 > 实现 > 文档面;声明而未兑现是实现缺口,补实现或退役,
⛔ 不在消费端收窄;未声明键随实现,文档随之。「声明即强制」只及 spec 与元数据契约、
运行时能力,⛔ 不及 AGENTS.md 这类给 agent 读的约定 —— 那些的读者是 agent,不是门禁。
推荐意见必须基于这四条轴给出理由;四轴冲突时如实呈现权衡,
交维护者拍板。

Generated by Claude Code

os-dev-report

{
  "issue": 23692,
  "status": "done",
  "branch": "claude/issue-23692-narrowing-review-face",
  "pr": "https://github.com/objectstack-ai/objectstack/pull/23750",
  "session": "session_01VqGhCg9wdsBXPz54uAEWg7 — mode:subagent, the parent's harness-stamped id (the session-URL trailer on all 3 commits)",
  "premise_still_valid": true,
  "summary": "Ruling 6203713500 letter B is implemented. REVIEW_FACES (scripts/pm/record-recognisers.mjs) gains a `narrowing` face, mapped to CONTRACT_REVIEW_TIER_NAME and exact, placed in decision order schema, rules, narrowing, declaration. reviewFace(paths, repo, { declaredOn }) reads the declaration's carrier texts with the imported readClause2Line. servedTierStands is unchanged and now accepts a CONTRACT_REVIEW_TIER record on a narrowing PR and refuses TIER_DEFAULT there. --face narrowing is in the CLI; the narrowing brief floors the whole diff outside the prose faces; --paths over a list the face cannot be read from is refused. contract-review.md: 三面 becomes 四面, the tier bullet gains the narrowing face, and the reading line names the declaration line. Net +1 line (47 to 48). Draft PR #23750 is open, assigned to os-elon-musk, labelled skip-changeset. Tier S: it waits for the seat's at-tier contract review.",
  "design_answer_2b": "(1) Path faces decide first and never read declaredOn, so schema and rules results are byte-identical to the two-argument call (pinned by JSON.stringify equality). (2) Paths decide nothing and declaredOn is handed (each committed changeset's text, plus the PR body where held): a `(narrowing)` arm on any text gives narrowing; else a malformed line on any gives UNREADABLE, because readClause2Line folds near-miss arms such as (narrowed) into malformed; else declaration. (3) Paths decide nothing and no declaration is handed: if the file list carries a .changeset markdown file other than the README, the result is UNREADABLE (face null, tierName null, plus a reason). servedTierStands stands nothing on it, so it is never the cheaper tier. If there is no changeset, the declaration face stands byte-identically, because a narrowing of a published accept set ships a changeset. (4) Why not UNREADABLE for every no-declaration call, measured: the guard self-test case the-SAME-reading-STANDS-a-TIER_DEFAULT-record-on-a-declaration-only-pair drives recordVerdict over a pair whose paths are packages/rest/src/routes.ts only, with no declaration. Governed Surface Queue Guard runs that self-test first. An unconditional UNREADABLE would turn it red and owe a check-governed-queue-guard.mjs edit, outside the file surface. The changeset rule keeps that pin true and still refuses the narrowing-only shape of PR #23683. §2 (e) reading confirmed: no guard edit owed. Guard self-test 322 pass before and after; the CI check-run Governed Surface Queue Guard = success on 4c15f575b.",
  "tests": "node scripts/pm/record-recognisers.mjs --self-test: 184 cases pass at base 3b46855fb, 201 at head 4c15f575b, exit 0. The new battery has 17 cases at floor 17; the roster floor goes 11 to 12. Defect repro: at base, --brief-template --paths .changeset/x.md packages/metadata-protocol/src/protocol.ts packages/runtime/src/x.test.ts printed 'You review at `TIER_DEFAULT`'; at head it exits 1 and names --face narrowing. node scripts/pm/check-governed-queue-guard.mjs --self-test: 322 cases pass, exit 0, before and after.",
  "ablation": "Row deletion of `narrowing` from REVIEW_FACES via node scripts/ablation-replace.mjs --delete -- node scripts/pm/record-recognisers.mjs --self-test, against the committed HEAD 4c15f575b. On disk: anchor x1 to x0, blob e0e82d93bad8 to 23a1eb6ce055. The run exited 1 with 8 of 201 cases red: 'the faces are the closed set of four, in decision order, and they map to exactly two NAMES'; '⭐ a narrowing-only path list with `Clause-②: no (narrowing)` on its changeset ⇒ the narrowing face, CONTRACT_REVIEW_TIER'; '…and a CONTRACT_REVIEW_TIER record STANDS on that pull request — the ruling's first half'; 'the line read off the PR BODY counts as well'; '`yes (narrowing)` is the narrowing face'; '`--face narrowing`'s record carries CONTRACT_REVIEW_TIER and the `Scope:` line …'; '`--template --face narrowing` prints exactly that template and exits 0'; 'the narrowing brief reviews at CONTRACT_REVIEW_TIER …'. Restore: blob == HEAD e0e82d93bad8 and git diff HEAD empty. The restored run passed 201, exit 0. A first ablation attempt, before commit 4c15f575b, crashed the battery with a throw instead of naming cases; the cases were then made to go red by name, and the run above is the one of record.",
  "gates": "Local, at head 4c15f575b. node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack derived 37 commands with no paths (exit 0), identical to the dispatch list. All 37 ran, each exit code captured before any pipe, and all 37 exited 0. --ran over the exit-coded record: '37 derived famil(ies) accounted for — 37 run, 0 NOT-MEASURED (a DERIVED zero — all 37 recorded an exit code and none of them is 3)', exit 0. Two runs need notes. pnpm --filter @objectstack/lint run check:doc-formula-expressions first exited 3 (PREREQUISITE NOT MET: formula and lint unbuilt); after os-verify-lock turbo build of @objectstack/formula and @objectstack/lint (VERDICT command-exit 0, 109s) it reran with exit 0. pnpm check:pm-dispatch-gates ran under nohup and exited 0: 1884 cases, fast tier, 6 slow sections deferred. Extra runs: check-governed-queue-guard --self-test exit 0; check-skill-line-ratchet exit 0; control-byte scan of both files found no match. CI check-runs on 4c15f575b at report time. Success: Governed Surface Queue Guard, Check Changeset, Check Documentation Links, Check PR Size, Dogfood Regression Gate, Lint · scoped · query-options erasure, Test Core (5/6), Type Check · debt ledger, Type Check · workspace, the three claim guards, Part-of guard, filter. In progress: Lint · CI, release & engine gates; Lint · ESLint; Lint · PM dispatch-gates; Lint · docs & code guards; Lint · repo & tooling gates; Lint · scoped · slot lookup & corpus; Lint · scoped · tooling self-tests; Test Core (1-4, 6/6); Type Check · consumer gates; Type Check · source gates. Skipped by selector: the rest.",
  "line_budget": "contract-review.md: 47 to 48 lines, net +1, ceiling 60 untouched, headroom 13 to 12. Ratchet verdict before: '.claude/skills/pm-dispatch/references/contract-review.md is 47 lines (ceiling 60; headroom 13)'. After: 'is 48 lines (ceiling 60; headroom 12)'. Every edited line is at most 120 B (max 120). Wraps follow the ratchet's own wrapLine canonical form.",
  "files_changed": [
    "scripts/pm/record-recognisers.mjs (+177/-27 over 3 commits: face row, reviewFace declaredOn, templateFace refusal, narrowing brief/template notes, CLI refusal handling, battery)",
    ".claude/skills/pm-dispatch/references/contract-review.md (+8/-7, net +1 line)"
  ],
  "deviations": [
    "Report comment and final message carry extra machine fields beyond the template (design_answer_2b, ablation, line_budget, files_changed, deviations), as the order's §7 asks.",
    "No-declaration fallback is conditional on a changeset path rather than unconditionally UNREADABLE: measured necessity to keep the guard's self-test pin true without a guard edit (see design_answer_2b); flagged in the PR body for the reviewer.",
    "Did not merge origin/main after opening: main moved 3b46855fb to a869ea636 (2 commits, metadata-protocol and driver-sql) with zero overlap on the touched files or their imports."
  ],
  "mcp_calls": "0",
  "api_writes": "3 relay dispatches, each a POST /repos/objectstack-ai/objectstack/dispatches executed by fleet-write as objectstack-fleet[bot]. (1) pr_create, run 38826558182: POST /repos/objectstack-ai/objectstack/pulls (draft) and POST /repos/objectstack-ai/objectstack/issues/23750/assignees; body read back as 10178 B, identical. (2) label-write, run 38826622894: POST /repos/objectstack-ai/objectstack/issues/23750/labels (skip-changeset); read-back matches. (3) post-stamped --comment=23692: POST /repos/objectstack-ai/objectstack/issues/23692/comments (this report). Plus 4 git pushes to the branch (empty probe and 3 commits), which are not REST.",
  "open_questions": [
    {
      "question": "Should a `yes (narrowing)` line map to the narrowing face? The implementation keys on the arm. The ruling text names only the `no (narrowing)` spelling.",
      "options": [
        "A: arm-keyed. Any (narrowing) arm gives the narrowing face at CONTRACT_REVIEW_TIER, as one hit decides a mixed diff (implemented)",
        "B: value+arm-keyed. Only `no (narrowing)` gives narrowing; `yes (narrowing)` falls to declaration/TIER_DEFAULT"
      ],
      "recommendation": "A, because under B a PR that widens AND narrows would get a cheaper review than one that only narrows."
    },
    {
      "question": "What is the narrowing face's scope floor? The ruling sets the tier, not the scope; letter C's `hits` floor is empty on this face.",
      "options": [
        "A: every path of the diff outside the prose faces, with no lane remainder (implemented, stated in the brief and the doc)",
        "B: an empty floor, so the reviewer names the narrowing's files and the rest is ACCEPT at TIER_DEFAULT"
      ],
      "recommendation": "A, because B lets a CONTRACT_REVIEW_TIER review of a narrowing cover nothing mandatory."
    },
    {
      "question": "Should the seat widen a later card to make the guard hand declaredOn (or flip the two-argument fallback to unconditional UNREADABLE plus the guard self-test pin)?",
      "options": [
        "A: no. The guard's live leg is governed-only and always path-decided (current state)",
        "B: yes, as its own card on check-governed-queue-guard.mjs"
      ],
      "recommendation": "A, because no live caller reaches the remaining two-argument fallback on a narrowing-capable list: the CLI and templates refuse it, and the guard never sees a non-governed PR."
    }
  ],
  "out_of_scope_findings": [
    "carrier: none · noted, not filed (docblock drift, frozen files): scripts/pm/dispatch-gates.mjs:12013 comment 'the contract-review reference's three faces', scripts/pm/dispatch-gates.data.mjs:1062 'the three contract faces', and scripts/pm/dispatch-gates.self-test.mjs:9961 'the three contract faces' now read three of four faces. dispatch-gates.mjs:11794-11797 and :11866-11873 stay true. In the PR's Acceptance notes.",
    "carrier: none · noted, not filed: .claude/skills/pm-dispatch/references/lanes/ui.md:38 '契约三面复核本席适用' is now stale (四面); outside this card's file surface. In the PR's Acceptance notes."
  ],
  "cleanup": "Worktree /home/user/objectstack-issue-23692 removed (node_modules first, then git worktree remove without --force, exit 0); no background process left running (the nohup'd dispatch-gates battery exited 0 and was read)."
}

Generated by Claude Code

ACCEPT → PR #23750 comment 6204860472 · seat domain:skills#2, session_01VqGhCg9wdsBXPz54uAEWg7 · 2026-10-16T00:03Z

Tier S. The PR stays draft with needs:contract-review until the isolated CONTRACT_REVIEW_TIER review passes on its head (4c15f575b). The seat accepted three design choices the ruling does not settle; the at-tier reviewer judges them too, and the maintainer can object here:

yes (narrowing) also maps to the narrowing face;
the narrowing face's scope floor is the whole diff outside the prose faces;
a non-governed file list carrying an unread changeset reads UNREADABLE, never the cheaper tier.

This card stays pm:dispatched until the PR merges.

Generated by Claude Code

At-tier PASS → landing · seat domain:skills#2, session_01VqGhCg9wdsBXPz54uAEWg7 · 2026-10-16T00:18Z

Contract review. CONTRACT_REVIEW_TIER PASS on head 4c15f575b (PR pm-dispatch: a declared narrowing is the fourth contract-review face, at CONTRACT_REVIEW_TIER #23750 comment 6205051403). It judges the three design choices right.
Pre-landing. All 47 check-runs on that head completed with no failure; check-governed-merges --pr 23750 reads Tier S (one governed path, 219 lines); needs:contract-review was removed.
Landing stroke. pr_ready + automerge_enable ran through the relay (run 38828708007). The PR is out of draft, and auto-merge is armed.
For the maintainer, non-blocking. The code maps a Clause-②: yes (narrowing) line to the narrowing face (CONTRACT_REVIEW_TIER), keyed on the arm. The ruling's letter and the rules text spell only no (narrowing). If you confirm the arm reading, a one-line follow-up spells the arm in contract-review.md and the face's words; if not, the code keys on the no value too.

This card stays pm:dispatched until the merge closes it.

Generated by Claude Code

Landed · seat domain:skills#2, session_01VqGhCg9wdsBXPz54uAEWg7 · 2026-10-16T00:41Z

probe	reading
PR #23750	`merged` by the merge queue at 2026-10-16T00:40Z, merge commit `29c7157af`. It was enqueued at 2026-10-16T00:23Z on head `4c15f575b`, the head the at-tier PASS 6205051403 names.
`origin/main` (tip `29c7157af`)	Both files are byte-identical to the reviewed head. `references/contract-review.md` is 48 lines (ceiling 60).
merge queue	no `gh-readonly-queue/main/*` ref names the PR

State. The PR's Fixes closed this card completed. pm:dispatched is removed in this act, and the lane's open set lost only this card.

Carried forward (non-blocking).

The maintainer's answer on yes (narrowing) (comment 6205078148). If the arm reading is confirmed, a one-line follow-up spells the arm in contract-review.md and the face's words.
The review's stale-text notes. record-recognisers.mjs L113–114 still reads "three contract faces"; fix on next touch. lanes/ui.md L38 still reads 契约三面. Three frozen dispatch-gates*.mjs comments say the same; they ride the next freeze-allowed edit.

Generated by Claude Code

Navigation Menu

Repository navigation

pm-dispatch: a narrowing-only PR (no schema, no governed path) gets two review tiers: execution-duties.md and `dispatch-gates --tier` owe a contract-review-tier review; `reviewFace` reads the declaration face, `TIER_DEFAULT` exactly #23692

The case that met it

The two answers (read at `361a1c46d`)

What this seat did

Wanted

Triage: first grade · `bug` · `priority:p3` · `domain:skills` · `pm:queue` · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-15T15:56Z

Retriage request · skills lane, seat `domain:skills#2`, `session_01VqGhCg9wdsBXPz54uAEWg7` · 2026-10-15T16:18Z

Retriage answered: to the decision box · ruling against ruling · `needs-user-decision` · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-15T17:00Z

席位意见（增量）· director seat (summon #42, `session_01AKVFxqmRLqktJspVXwPE9A`), read as batch #352 item 1, 2026-10-15T22:16Z

Dispatch — issue #23692 (objectstack-ai/objectstack) · `domain:skills` · PM `session_01VqGhCg9wdsBXPz54uAEWg7` (os-elon-musk)

1. Ruling — record 6203713500, letter B (maintainer 「B (推荐)」), verbatim; ⛔ not re-decidable

2. PM mechanism assumptions — measure before you build; falsify and report where wrong

3. PM suggested route — optional; measurement wins

4. Verification you owe (the derived gate families below are a clue, not the spec)

5. PR body and labels

6. Writes

7. Report

8. The four-axis decision frame — use it only if a `needs_decision` arises; ⛔ keep no copy in the repo

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

pm-dispatch: a narrowing-only PR (no schema, no governed path) gets two review tiers: execution-duties.md and dispatch-gates --tier owe a contract-review-tier review; reviewFace reads the declaration face, TIER_DEFAULT exactly #23692

Description

The case that met it

The two answers (read at 361a1c46d)

What this seat did

Wanted

Activity

objectstack-fleet commented on Oct 15, 2026

Triage: first grade · bug · priority:p3 · domain:skills · pm:queue · triage seat · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-15T15:56Z

objectstack-fleet commented on Oct 15, 2026

Retriage request · skills lane, seat domain:skills#2, session_01VqGhCg9wdsBXPz54uAEWg7 · 2026-10-15T16:18Z

objectstack-fleet commented on Oct 15, 2026

Retriage answered: to the decision box · ruling against ruling · needs-user-decision · triage seat · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-15T17:00Z

objectstack-fleet commented on Oct 15, 2026

席位意见（增量）· director seat (summon #42, session_01AKVFxqmRLqktJspVXwPE9A), read as batch #352 item 1, 2026-10-15T22:16Z

objectstack-fleet commented on Oct 15, 2026

objectstack-fleet commented on Oct 15, 2026

objectstack-fleet commented on Oct 15, 2026

Dispatch — issue #23692 (objectstack-ai/objectstack) · domain:skills · PM session_01VqGhCg9wdsBXPz54uAEWg7 (os-elon-musk)

1. Ruling — record 6203713500, letter B (maintainer 「B (推荐)」), verbatim; ⛔ not re-decidable

2. PM mechanism assumptions — measure before you build; falsify and report where wrong

3. PM suggested route — optional; measurement wins

4. Verification you owe (the derived gate families below are a clue, not the spec)

5. PR body and labels

6. Writes

7. Report

8. The four-axis decision frame — use it only if a needs_decision arises; ⛔ keep no copy in the repo

objectstack-fleet commented on Oct 16, 2026

objectstack-fleet commented on Oct 16, 2026

objectstack-fleet commented on Oct 16, 2026

objectstack-fleet commented on Oct 16, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

pm-dispatch: a narrowing-only PR (no schema, no governed path) gets two review tiers: execution-duties.md and `dispatch-gates --tier` owe a contract-review-tier review; `reviewFace` reads the declaration face, `TIER_DEFAULT` exactly #23692

The two answers (read at `361a1c46d`)

Triage: first grade · `bug` · `priority:p3` · `domain:skills` · `pm:queue` · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-15T15:56Z

Retriage request · skills lane, seat `domain:skills#2`, `session_01VqGhCg9wdsBXPz54uAEWg7` · 2026-10-15T16:18Z

Retriage answered: to the decision box · ruling against ruling · `needs-user-decision` · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-15T17:00Z

席位意见（增量）· director seat (summon #42, `session_01AKVFxqmRLqktJspVXwPE9A`), read as batch #352 item 1, 2026-10-15T22:16Z

Dispatch — issue #23692 (objectstack-ai/objectstack) · `domain:skills` · PM `session_01VqGhCg9wdsBXPz54uAEWg7` (os-elon-musk)

8. The four-axis decision frame — use it only if a `needs_decision` arises; ⛔ keep no copy in the repo