contract review owed: PR objectui#9378 carries needs:contract-review with no review record, and the tier belongs to the skills seat

[os-justin]

Filed by the domain:ui execution seat (session_01XeoGH6X7MtfbjcRDscyXi1) while discharging objectui#9570. A cross-seat request is work, so it is a card in the target lane's queue, ⛔ not a knock on a seat post.

domain:skills is inherited from objectui#9370, of which this is a derivative — the 衍生承父卡域 exception, the one documented bypass of triage. ⛔ This seat did not grade or route it.

What is needed

PR objectui#9378 (draft, head 5df0ee9719178037689ca3fb7c61394eab88ec2d) carries needs:contract-review and has since 2026-09-13T08:46Z. Card objectui#9370 declares Clause-②: yes. No review record of any kind exists, so per the standing contract the carrier correctly still hangs.

The review is blocked on tier, and only on tier:

• The card's surface is published skills/** — 协议语义面 under 强制条款①, and 「发布的 skills/** 整根随 npx skills add 发运,⛔ 无一行级豁免」, so no line-level exemption applies however small the diff.
• Where the build was dispatched below that tier, the charter's compensating control is explicit: 「降档施工的补偿控制 = 复核席跑契约复审档」.
• The domain:ui seat ⛔ cannot supply it: 「契约复审档留给 skills 席与 spec 席的条款②复核,其余席位 ⛔ 永不起该档子代理」.

⇒ this is the skills seat's review, ⛔ not this lane's. Independence is already satisfiable — the implementer was an os-dev on claude/issue-9370-skills-data-root, so a Reviewed-by: from any seat other than that build is independent.

One executable criterion

Post a 同形 contract-review record against head 5df0ee97, in the required shape — a ## Contract review heading · the reviewed head sha · items ①②③ (derived judgments / semver / boundary flags) · an independence pair (Implemented-by: / Reviewed-by:) · a Served-tier: line · a PASS/FAIL verdict — then strip both carriers in one stroke with a provenance comment citing the record id and the judged head. ⚠️ Served-tier: is mandatory and its omission is what made an earlier record fail --pair at exit 4.

Verify with PM_SWEEP_REPO=objectstack-ai/objectui node scripts/pm/check-clause2-carriers.mjs --pair 9378 before stripping, ⛔ not after. That script lives in objectstack and defaults to the objectstack board — without the env var it answers about the wrong repo.

State this card does NOT change

⛔ objectui#9370 keeps its assignee, its pm:dispatched state and its claim. This card asks for one review record, ⛔ not for the card to move lanes. The domain:ui seat carries objectui#9370 to MERGED per 「认领即跟到 MERGED」.

⚠️ PR objectui#9378 is a governed-surface PR (published skills/**): 命中即停 draft. ⛔ No ready-flip, ⛔ no queue, ⛔ no auto-merge, ⛔ no approval — a human merges it. The contract review is owed in addition to that human merge, ⛔ not instead of it; the two stack.

Current reading, taken this fire

--pair 9378 now returns exit 0 — 「the clause-② declaration is readable in the fixed spelling and both carriers agree」. It read UNJUDGED for two days until objectui#9570 was discharged (recovery comment 5689310818). ⇒ the pair is judgeable now; what is missing is the judgement.

Refs: objectui#9370 · PR objectui#9378 · objectui#9570 · seat post objectui#5560

Dedup terms for triage: 9378 contract review · 9370 Served-tier · skills contract-review carrier · needs:contract-review 9378

---

Generated by Claude Code

[os-justin]

CLOSING — withdrawn on the maintainer's ruling; the review folds back into this seat

Closed by the domain:ui execution seat, session_01XeoGH6X7MtfbjcRDscyXi1 (os-justin), 2026-09-16T04:2xZ.

Provenance — whose instruction, verbatim, and where

Maintainer, in the /pm-dispatch session driving this seat, untranslated:

#9577 撤回 ui 席(或关闭,并入 PR #9378 的席内复核);#9570 解封;
#7945 可派:施工按「降档施工」走默认档,补偿控制 = 复核席跑契约复审档(它席内即是),四件套照旧等你批(发布的 skills/** 是规则层,这点不变);

Why this card existed, and why it is wrong now

It was filed because this seat read two charter lines as leaving it no route: 强制条款① makes published skills/** 协议语义面 with 「⛔ 无一行级豁免」, while SKILL.md says 「契约复审档留给 skills 席与 spec 席…其余席位 ⛔ 永不起该档子代理」. Reading the stricter line, the seat concluded PR objectui#9378's review was ⛔ not available to it and routed the request here.

The maintainer has now settled it the other way: the build goes at default tier as a 降档施工, and the compensating control is the reviewing seat's own in-seat review — 「它席内即是」. ⇒ this lane's in-seat review is the control, and no cross-seat request is owed.

⇒ closed not_planned — a withdrawal, ⛔ not completed work. The substance moves into PR objectui#9378's in-seat contract review, which is now this seat's to render.

⛔ What does NOT change

• Published skills/** stays 规则层: 「四件套照旧等你批」. PR objectui#9378 stays draft-and-wait for a human merge. ⛔ No ready flip, ⛔ no enqueue, ⛔ no auto-merge, ⛔ never an approval from this seat.
• The needs:contract-review carriers on PR objectui#9378 and card objectui#9370 stay hung — they hang exactly while no review record exists, and none does yet.

⚠️ Honest statement of what this unblocks, and what it does not

This ruling removes the authority blocker. It does ⛔ not remove the channel blocker: the in-seat 同形 record it authorises is the same write the harness auto-mode classifier is refusing this seat as [Self-Approval] on PR objectui#9578 and PR objectui#9589. ⇒ PR objectui#9378 now joins those two, and all three clear on one permission fix rather than three separate ones. ⛔ Recorded rather than quietly retried.

Refs: objectui#9370 · PR objectui#9378 · objectui#9570 · seat post objectui#5560

---

Generated by Claude Code