charter conflict: does a Clause-②: no PR that touches no contract surface still owe an in-seat review before it can land?

Two rules in the seat's own charter give different answers for the same PR, and the seat cannot resolve the text on the spot. Filed under 「两条细则冲突 ⇒ 按更严的一条行动并立卡;⛔ 不当场改文本了结」. The seat is acting on the stricter reading meanwhile, and says so on the affected cards.

The situation that forced the question

Two PRs from this lane are Clause-②: no, CI-green or nearly so, and touch no contract surface:

test(spec): order the sdui cleanup fd count on the child's own post-exec report #18530 (card gen-sdui-manifest-cleanup.test.ts counted one caller lock fd (LOCKFDS 1, expected 0) on an unrelated PR's Test Core (1/6) — main green the same day #18010) — one file, packages/spec/scripts/gen-sdui-manifest-cleanup.test.ts
feat(spec): check (c) proves a guidance-route retirement on a reachable def (#18301) #18529 (card check (c) has no proof shape for a guidance-route retirement on a reachable def — add a fourth proof so UNKNOWN_KEY_GUIDANCE retirements prove themselves (batch #135 item 3, C) #18301) — packages/spec/scripts/build-schemas.ts + its check-mode test

Meanwhile the contract-review tier is refusing at the account level (HTTP 429), so no isolated at-tier review can run at all. Whether these two may land turns entirely on which rule governs.

Reading A — the enqueue gate says no review is owed

SKILL.md 〈入队与落地〉:

--tier 嫌疑行是提示非裁定;双肢命中任一 ⇒ 无席内条款②复核 PASS 在案 ⛔ 禁止入队。
路径肢 = diff 触及契约面 packages/spec/src/**,含 error-code-ledger 与 *.zod.ts 契约 schema。
声明肢 = 认领评论声明 Clause-②: yes,与路径无关。

Neither limb hits: the diffs are packages/spec/scripts/**, which is not packages/spec/src/**, and both claims declare no. The rule is stated as a prohibition conditioned on a limb hitting ⇒ with no limb hit, no in-seat clause-② review PASS is required, and the two-limb machinery exists precisely to decide when one is owed. check-clause2-carriers --pair agrees in its own output: exit 0, "no widening tell", and — unlike the yes PRs — it prints no C6-RECORD row demanding a review of record on the head.

Reading B — post-delivery review is owed for every delivered round, at-tier for this lane

references/contract-review.md and the same SKILL section:

逐车道:spec 席达档审契约增量;余席默认档自审加门禁、挂标;豁免仅独立性件与保险丝。
交付后复核由派发席席内完成:spec 席达档,余席默认档加门禁;记录 = 同形评论落 PR 或卡。
独立性件:契约真分叉、dev 挂旗或派发后的跨车道面(含 spec)⇒ 起隔离的达档复核子代理。

「交付后复核由派发席席内完成」 is unconditional on its face. And both rounds raised flags — #18010's dev put an A/B/C open_questions in front of the seat, #18301's round is answering a CI red — so 「dev 挂旗」 is satisfied, which makes them independence cases, and the only exemptions named are independence cases and the fuse. Under this reading an isolated at-tier review is required even though the clause-② gate never fires.

Why the seat cannot just pick

Reading A is supported by the gate's structure (two limbs whose whole job is to decide when a review is owed, and a checker that demands a review record only for yes). Reading B is supported by the plain text of two sentences that are not conditioned on a limb. ⛔ Neither is obviously the drafter's intent, and the seat is not entitled to settle it by choosing the answer that unblocks its own queue — which is exactly what Reading A would do today.

What the seat is doing meanwhile

Acting on Reading B (the stricter one). #18530 and #18529 stay draft, out of the queue, until either the tier returns or this card is answered. A PR that waits loses time; a PR landed without a review the rules wanted cannot be un-landed.

⚠️ The cost is worth stating plainly: with the tier refusing, Reading B means nothing from this lane can land at all — not the contract work, and not the test/script work either.

What an answer looks like

Either (a) confirm Reading A and say so in the charter — a non-limb PR is collected with a default-tier seat record and lands on the three pre-checks; or (b) confirm Reading B and make 「交付后复核」 explicitly unconditional, in which case the Clause-② limbs decide the TIER of the review rather than its existence; or (c) a third shape: a flag raised by a dev pulls a non-limb PR into at-tier review, which is what the independence sentence would mean if read narrowly.

⚠️ Whichever it is, the sentence 「豁免仅独立性件与保险丝」 needs to say what it exempts them FROM, because today it can be read as exempting them from the default tier (i.e. forcing at-tier) or as exempting them from review entirely.

Dedupe words: 双肢命中任一, 交付后复核由派发席席内完成, 独立性件 dev 挂旗, Clause-② no 非限定 PR 落地, packages/spec/scripts 不是契约面.

Generated by Claude Code

Ruling: batch #151 item 3 · the maintainer's lane rule restated (the contract review at CONTRACT_REVIEW_TIER is owed in the domain:spec and domain:skills lanes only; every other lane lands on the three pre-checks and the gates with no contract review; a seat on the default tier discharges the spec/skills review by spawning the at-tier subagent, and only when that subagent cannot start is the review unavailable) · maintainer 「曾经要求只有 spec 和 skills 需要 fable,其他 opus 就够了,理论上其他车道不需要契约复审」「即使项目经理跑在 opus 上,也可以支持起 fable 子 agent 复审,这样最快。除非子 agent 用 fable 启动失败,也就是没有 fable」 2026-09-17T15:42Z

Director seat, summon #24, session_01Wj1HUjzyeiBQ8atRf1ZhaL. Presented in detail with a recommendation (B: review existence unconditional, the limbs decide the tier); the maintainer answered with the rule above instead, adding that the recent skill edits had muddled it. The seat traced the muddle in origin/main's history so the text can be put back exactly:

commit	date	what it said
`c47edbb2` (#17294)	2026-09-10	「契约复审档留给 skills 席与 spec 席的条款②复核,其余席位 ⛔ 永不起该档子代理」「交付后复核由派发席席内完成:spec 席达档自审或派该档子任务,余席默认档自审加门禁」 — the lane rule the maintainer is restating
`05f1cdd6` (#18363, on #18349)	2026-09-16	re-keyed the three seat-bound lines to the served tier on the maintainer's 「不再有『只在 spec 席』」 — the seat list disappeared
`ab1d3592` (#18511, on #18434 ruling C)	2026-09-17	an off-tier seat may spawn the at-tier subagent — kept by today's rule

⇒ Today's word restores the 09-10 lane key and keeps the 09-17 subagent route; the 09-16 「no seat list」 is superseded. The card's two readings dissolve under it: SKILL.md:637's limbs (path packages/spec/src/**, declaration Clause-②: yes) decide the lane — a PR that hits a limb is spec-lane work under the standing routing rule (a published contract surface is the spec lane's, whichever seat found it) — and SKILL.md:640's 「交付后复核」 applies inside the spec and skills lanes, where it is the at-tier review, in-seat or by subagent. Outside those two lanes there is no contract review to owe: the three landing pre-checks and the gates are the whole bar.

Ruling

Spec and skills lanes: every delivered round gets the contract review at CONTRACT_REVIEW_TIER — in-seat when the seat's served tier is that tier, otherwise by spawning the at-tier review subagent (the fastest route, per the maintainer); the record is the same-shape comment on the PR or card with Served-tier:. The needs:contract-review carrier lives only in these two lanes.
Every other lane: no contract review. Clause-② is answered by lane routing — a diff on a contract surface (packages/spec/src/**; objectui packages/types/**, its schema corpus and the spec-pin coupling) is spec-lane work and moves there; a Clause-②: no PR outside those surfaces lands on the pre-checks and gates. ⛔ No default-tier 「self-review」 record is demanded, and ⛔ no other lane spawns the at-tier subagent.
When the at-tier subagent cannot start (the tier is refused or the model is unavailable — today's account-level 429): the review cannot be produced; the PR stays draft and out of the queue (the charter's safe state) until the tier returns. The maintainer's own review remains the only bypass, by their word each time. ⇒ PR test(spec): order the sdui cleanup fd count on the child's own post-exec report #18530 / feat(spec): check (c) proves a guidance-route retirement on a reachable def (#18301) #18529 (cards gen-sdui-manifest-cleanup.test.ts counted one caller lock fd (LOCKFDS 1, expected 0) on an unrelated PR's Test Core (1/6) — main green the same day #18010 / check (c) has no proof shape for a guidance-route retirement on a reachable def — add a fourth proof so UNKNOWN_KEY_GUIDANCE retirements prove themselves (batch #135 item 3, C) #18301, domain:spec, Clause-②: no, packages/spec/scripts/**) are spec-lane rounds and wait on the tier under rule 1 unless the maintainer reviews them.

Execution

needs-user-decision → pm:queue; domain:skills, p2 stay. The claiming seat carries the rule into the governed text — SKILL.md:637 / :640, references/contract-review.md:26 / :32 / :50 (「按档位」 → 「按车道」; the fuse governs the spec and skills seats' clause-② review only; 「豁免仅独立性件与保险丝」 rewritten to say what is exempted from what), references/core-rules.md where the 09-16 re-key landed, and the machine side (scripts/pm/dispatch-gates.mjs / check-clause2-carriers.mjs, which c47edbb2 keyed by seat and 05f1cdd6 re-keyed by tier) — the lane becomes the key again, the subagent route stays. Governed surface ⇒ human merge by the approver. After it lands, each lane seat re-reads the needs:contract-review carriers hung outside the spec/skills lanes (census in the director's ledger ⑫) and either re-lanes the item to spec or strips the carrier; ⛔ the director strips none before the text.

Generated by Claude Code

Claim: PM loop round 1
Session: session_01BTeBejoPUvRHN8WdAJC6oF
Branch: claude/issue-18536-lane-keyed-contract-review
Worktree: objectstack-issue-18536
Domain: domain:skills
Seat: domain:skills#1
File surface: .claude/skills/pm-dispatch/SKILL.md (812 / 812 — the 强制条款② line, the 席位档策略 band, the 入队闸门 band 「--tier 嫌疑行 … 交付后复核归派发席」 and the pointer line to contract-review.md), .claude/skills/pm-dispatch/references/contract-review.md (60 / 60 — 载体纪律, 复核归属与资格「按档位 …」, 落地前检三条, 降档保险丝), .claude/skills/pm-dispatch/references/core-rules.md (151 / 151 — 「语义面卡恒契约复审档施工,契约卡达档复核归派发席」, 「references/ 席内达档复核后入队」 and wherever PR #18363's re-key landed), scripts/pm/dispatch-gates.mjs (the clause-② rendering under tierLines and its self-test pins), scripts/pm/check-clause2-carriers.mjs (the C6 / C7 population gate — which pairs OWE a review of record, and its self-test); every added charter line paid in-file; ⛔ no other file; skip-changeset; governed rules layer ⇒ draft at the four-piece terminal (stop on breach; explain in the report)
Container & model: L, mode:subagent, model: claude-fable-5-1 (CONTRACT_REVIEW_TIER, MANDATORY) — node scripts/pm/dispatch-gates.mjs --tier --repo objectstack-ai/objectstack over the five paths at 2026-09-18T04:21Z: 「Model tier — MANDATORY: claude-fable-5-1 (derived from the file surface, not recalled). — .claude/skills/pm-dispatch/SKILL.md ⇢ '.claude/skills/pm-dispatch/SKILL.md' — clause ①」; no exit taken; the seat's contract-tier review at delivery (in-seat: served tier claude-fable-5-1 by get_session at seating)
Clause-②: no
Thread-read: 5717169811
Serial constraints cleared: 19 open PRs' file lists read at 2026-09-18T04:16Z — none touches any of the five files; last landed: SKILL.md + core-rules.md PR #18809 6427ee2480 at 2026-09-18T02:05:05Z, contract-review.md PR #18666 5a8c94b7f2 at 2026-09-18T01:44:29Z, dispatch-gates.mjs PR #18856 d09976456e at 2026-09-18T01:22:08Z, check-clause2-carriers.mjs PR #18859 e8ba892a1b at 2026-09-18T02:30:56Z — same-day churn on all five, the dispatch carries the churn line; os-verify-lock.sh --status at 2026-09-18T04:21Z: free. Hot-file queue behind this card: SKILL.md → #18743 · #18755 · #18665 · #18469 PR-B · #18489; check-clause2-carriers.mjs → #18807; the two other dispatches of this round (#18831: check-half-states.mjs; the #18699 fold: os-dev.md) are disjoint.
Ruling-ref: 5717169811

Generated by Claude Code

os-dev-report

{
  "issue": 18536,
  "status": "done",
  "branch": "claude/issue-18536-lane-keyed-contract-review",
  "pr": "https://github.com/objectstack-ai/objectstack/pull/18903",
  "session": "session_01BTeBejoPUvRHN8WdAJC6oF",
  "premise_still_valid": true,
  "summary": "Carried the maintainer's lane rule (director record 5717169811, rules 1-3) into the governed text and both machine readers, head bc0c2ec41 (three commits: charter, dispatch-gates.mjs, check-clause2-carriers.mjs). Charter: SKILL.md :512/:522/:636/:639/:646 rewritten, rule 3 (subagent cannot start => review absent, PR stays draft out of the queue, maintainer's own review the only bypass) added at :640 and paid by retiring the default-tier clause-② FAIL-rate line (former :672); contract-review.md title/:9/:11/:12/:14/:23/:25/:26/:27/:32/:40/:50/:52/:53 re-keyed 按车道 with 「豁免仅独立性件与保险丝」 rewritten as 「只免席内审,不免复核」; core-rules.md :112 re-keyed. Machine: dispatch-gates.mjs --tier note and suspect tail name the spec and skills lanes and the subagent route (4 new pins); check-clause2-carriers.mjs C6 population now = completed state OR a declared `no` on a domain:spec/domain:skills card (LANES_OWING_REVIEW, laneOwesReview), a cleared `yes` outside those lanes keeps exit 4 with a lane-ROUTING remedy, new floored battery of 34 cases. PR #18903 is DRAFT (governed rules layer), Fixes #18536, Clause-②: no at line start, skip-changeset label written and read back, 维护者速读(草稿) five paragraphs with 席位意见 blank, body read back byte-identical minus the trailing newline, zero tag-shaped fragments. Assignee was already set by the dispatch (os-elon-musk); newest Claim: 5725106492 names this branch; no second claim posted. Re-key trace by REST GET /pulls/N/files: #17294 keyed by seat (09-10), #18363 re-keyed SKILL.md + contract-review.md by tier (09-16, core-rules.md untouched), #18511 added the subagent route and gave core-rules.md :112 its 「归派发席」 (09-17).",
  "tests": "Both edited scripts' own self-tests: node scripts/pm/check-clause2-carriers.mjs --self-test => exit 0, 「✓ check-clause2-carriers self-test: 977 cases pass」 (baseline on 0b31d90: 941; new battery '#18536: the lane-keyed owed population …' 34 cases, floor 30; SELF_TEST_BATTERY_FLOOR 32→33). node scripts/pm/dispatch-gates.mjs --self-test => 「✓ dispatch-gates self-test: 1852 cases pass」 (baseline 1848; +4 lane-key pins), 0 ✗. pnpm check:pm-dispatch-gates (detached, 733.5 s on this box) => 「✓ dispatch-gates self-test: 1852 cases pass. check:pm-dispatch-gates: the battery took 733.5s on this box.」, 0 ✗, no ELIFECYCLE line — its $? was NOT captured (detached run), the verdict line is the reading. Charter gates on the final head bc0c2ec41 (each redirect-then-$?): check:pm-skill-ratchet exit 0 (812/60/151 at ceilings 812/60/151, every edited line ≤120 bytes), check:pm-skill-id-lint exit 0 (27 files clean), check:skill-frame-sync exit 0, check:skill-frame-freshness exit 0, check:nul-bytes exit 0, check:pm-governed-prose exit 0. Derived union (46 families) all exit 0 after one prerequisite rerun — see gates. The four package tests naming dispatch-gates.mjs reference it in docblocks only (git grep), so no package test is owed; no package source changed, so no build/typecheck closure (①) is owed beyond the turbo build of @objectstack/formula + @objectstack/lint run under scripts/pm/os-verify-lock.sh (VERDICT command-exit 0, cache hit) as the prerequisite of check:doc-formula-expressions. Ablation/reverse verification: not applicable (no new gate on a runtime; the self-test pins themselves are the falsifiable half — the failing first run of the #18141 pin 「DIFFERENT sentence from the empty case」 proved the C6 routing branch was under pin, fixed by restoring the measured-shape sentence, rerun 977 pass).",
  "gates": {
    "derivation": "node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack from the worktree at bc0c2ec41 (no paths passed; changeset from merge-base). 46 families derived. Derivation printed 「⚠️ STALE TREE — at least 2 commit(s) behind origin/main, 1 file it derives from CHANGED」 (origin/main moved during the run); the list run is the one derived at bc0c2ec41 — PM re-derivation after this report reads the true list.",
    "ran": [
      "node scripts/check-adr-0087-registration.mjs --base origin/main :: exit 0",
      "node scripts/check-adr-0087-registration.mjs --self-test :: exit 0",
      "node scripts/check-changeset-no-major.mjs --base origin/main :: exit 0",
      "node scripts/check-changeset-no-major.mjs --self-test :: exit 0",
      "node scripts/check-ci-filter-parity.mjs :: exit 0",
      "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/check-declaration-mirrors.mjs :: exit 0",
      "node scripts/check-declaration-mirrors.mjs --self-test :: exit 0",
      "node scripts/check-scripts-symbol-anchors.mjs :: exit 0",
      "node scripts/check-scripts-symbol-anchors.mjs --self-test :: exit 0",
      "node scripts/check-self-test-wired.mjs :: exit 0",
      "node scripts/check-self-test-wired.mjs --self-test :: exit 0",
      "node scripts/check-self-test-workflow-commands.mjs :: exit 0",
      "node scripts/check-self-test-workflow-commands.mjs --self-test :: exit 0",
      "node scripts/check-whole-set-label-write.mjs :: exit 0",
      "node scripts/check-whole-set-label-write.mjs --self-test :: exit 0",
      "node scripts/pm/bare-root-worklist.mjs --self-test :: exit 0",
      "node scripts/pm/check-governed-queue-guard.mjs --self-test :: 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:bash32-floor :: exit 0",
      "pnpm check:changeset-gate-self-tests :: exit 0",
      "pnpm check:cli-command-ids :: exit 0",
      "pnpm check:cross-package-test-inputs :: exit 0",
      "pnpm check:declared-population-live :: exit 0",
      "pnpm check:doc-authoring :: exit 0",
      "pnpm check:driver-memory-census :: exit 0",
      "pnpm check:entry-guard :: exit 0",
      "pnpm check:nul-bytes :: exit 0",
      "pnpm check:parse-guard :: exit 0",
      "pnpm check:pm-clause2-carriers :: exit 0",
      "pnpm check:pm-expected-skips :: exit 0",
      "pnpm check:pm-governed-merges :: exit 0",
      "pnpm check:pm-governed-prose :: exit 0",
      "pnpm check:pm-half-states :: exit 0",
      "pnpm check:pm-skill-id-lint :: exit 0",
      "pnpm check:pm-skill-ratchet :: exit 0",
      "pnpm check:pnpm-filter-targets :: exit 0",
      "pnpm check:ratchet-remedy-authority :: 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:pm-dispatch-gates :: exit 0"
    ],
    "notes": "check:doc-formula-expressions first exited 3 (PREREQUISITE NOT MET: @objectstack/formula / @objectstack/lint not built — 「Nothing was measured」), so it is recorded as the rerun after `pnpm exec turbo run build --filter=@objectstack/formula --filter=@objectstack/lint --concurrency=2` under os-verify-lock (command-exit 0): rerun exit 0, 「22 record-scoped formula example(s) … judged clean」 + 9 spec TSDoc + 14 field-level predicates. pnpm check:pm-dispatch-gates: exit 0 recorded from the verdict line (detached; $? not captured). All other 44: $? captured by the runner script after redirect, all 0.",
    "ran_reconciliation": "node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --ran ran-coded.txt => exit 0: 「Run reconciliation — 46 derived, 46 run, 0 NOT-MEASURED, 0 UNRUN. EXIT CODES — all 46 accounted famil(ies) carry one」 「✓ dispatch-gates --ran: 46 derived famil(ies) accounted for — 46 run, 0 NOT-MEASURED (a DERIVED zero — all 46 recorded an exit code and none of them is 3)」."
  },
  "line_budget": {
    ".claude/skills/pm-dispatch/SKILL.md": "812 → 812 (ratchet ceiling 812; check:pm-skill-ratchet exit 0). Added :640 「子代理起不来 ⇒ 复核缺席,PR 留 draft 队列外等档;唯一旁路是维护者亲审,逐次为准。」 paid by retiring former :672 「报告席记条款②默认档 FAIL 率入复审清单;超改制前达档史值 ⇒ 决策卡交维护者定回退。」 — reason: it meters the FAIL rate of default-tier clause-② reviews and under rules 1-2 no lane performs one (spec/skills review at tier, other lanes review nothing), so its population is empty; it is the one tier-keyed line the ruling empties. In-place rewrites: :512, :522, :636, :639, :646. No re-wrap used as currency.",
    ".claude/skills/pm-dispatch/references/contract-review.md": "60 → 60 (ceiling 60). In-place rewrites only: :1, :9, :11, :12, :14, :23, :25, :26, :27, :32, :40, :50, :52, :53. Nothing added, nothing retired.",
    ".claude/skills/pm-dispatch/references/core-rules.md": "151 → 151 (ceiling 151). In-place rewrite only: :112. Nothing added, nothing retired.",
    "skills/**": "not touched (no published skill line budget owed)."
  },
  "deviations": [
    "Machine assumption 3 / suggested case (c): a `yes` pair on a domain:cli card is implemented as OWED with exit 4 and a lane-ROUTING remedy (re-lane to spec via pm:retriage or split the contract work to a spec-lane card/PR; or correct a false `yes` with Clause-②-correction:), NOT as 「not owed + note」 at exit 0. The row's exit is unchanged from today; only the remedy text moved. Reasons in open_questions (four axes).",
    "Payment line outside the declared SKILL.md bands: the retired former :672 sits in the 轮次报告 band, not in the four bands the claim named; it is the one tier-keyed line the ruling empties and paying in-file required it (declared in the PR body).",
    "contract-review.md :27 「达档与默认档同形」 → 「席内与子代理同形」 was not in the ruling's line list; it is the tier-keyed phrase the scripts quote, and both quotations (check-clause2-carriers.mjs header + C6 row) were updated in the same PR.",
    "pnpm check:pm-dispatch-gates was run detached (nohup) because of the foreground cap; its verdict line was read from the log and its $? was not captured. The 44 batch commands ran under a runner script that captured $? after redirect per command; the batch itself was detached and waited on in the foreground with tail --pid.",
    "One Bash call exceeded the tool's 120 s default and was moved to the background by the harness; no work was lost (the batch and self-test were already detached with PID files).",
    "The report's ran record marks check:doc-formula-expressions with the exit of its rerun (0) after the prerequisite build, not its first exit (3, nothing measured)."
  ],
  "files_changed": [
    ".claude/skills/pm-dispatch/SKILL.md",
    ".claude/skills/pm-dispatch/references/contract-review.md",
    ".claude/skills/pm-dispatch/references/core-rules.md",
    "scripts/pm/dispatch-gates.mjs",
    "scripts/pm/check-clause2-carriers.mjs"
  ],
  "mcp_calls": "0 — no MCP GitHub tool was called; every GitHub read and write went through REST with GITHUB_TOKEN via curl.",
  "api_writes": "5 — git push (empty branch probe, then bc0c2ec41); POST /repos/objectstack-ai/objectstack/pulls (201, #18903 draft); POST /repos/objectstack-ai/objectstack/issues/18903/labels (200, skip-changeset; read back: ['skip-changeset']); POST /repos/objectstack-ai/objectstack/issues/18536/comments (this os-dev-report). Reads: issue 18536 + comments, pulls 17294/18363/18511 files, pulls/18903.",
  "open_questions": [
    {
      "question": "Machine shape for a `Clause-②: yes` pair whose card sits outside the spec/skills lanes (e.g. domain:cli), gate cleared on both carriers, no record on the head: exit 4 with a lane-routing remedy (implemented), or exit 0 with a note (the dispatch's suggested case (c))?",
      "options": [
        "A (implemented): owed, C6 row, exit 4; remedy = re-lane to spec / correct a false `yes`; ⛔ no self-review, ⛔ no at-tier subagent from that lane. 实际业务需求: the measured population is the census of needs:contract-review carriers hung outside spec/skills that the ruling tells the lane seats to re-lane or strip — a red at --pair is exactly the signal that census acts on. 项目长远合理性: keeps contract-review.md :42's 「0 = … head 上有记录」 true and mirrors the rule text (limb hit = spec-lane work) without a new row class. 防 AI 写错: loud refusal at landing; an exit-0 note would let a cli seat clear and land a limb-hit pair — the 自查放行 hole the file's header bans. 创业阶段不扩散: no new row, no new finding class, the exit is unchanged from today — only the remedy sentence moved.",
        "B: not owed as a record; C6 silent; a NOTE names ruling 2's re-lane; exit 0. 实际业务需求: matches the literal 「⛔ No default-tier self-review record is demanded」 but demands nothing at all, so the census has no machine signal. 项目长远合理性: makes exit 0 mean 「landable」 on a pair the rule says moves elsewhere; :42 would need rewording. 防 AI 写错: silence at the landing moment — the failure class this file exists against. 创业阶段不扩散: smallest text change, but a weakening of an existing gate."
      ],
      "recommendation": "A, because the card's own failure mode was a `--pair` that answered 0 where the rule owed a review; B reproduces that shape one lane over. A demands no default-tier record and no subagent from the cli lane — it demands the move the ruling names. The PR is draft for the maintainer's word; if B is preferred, the change is one branch in c6NoReviewOfRecord plus the battery's four routing pins."
    }
  ],
  "out_of_scope_findings": [
    "noted, not filed: SKILL.md :231 「派发后发现的跨车道面(含 spec)不移卡,认领席借契约复审档隔离复核」 and core-rules.md :62 (its mirror) still carry the 「borrow the isolated at-tier review」 route that rule 2 closes for other lanes; outside this card's declared SKILL.md bands, reported in the PR body with a same-byte-budget rewrite (「契约面工作交 spec 车道达档复核」). 承接者: the skills seat's next SKILL.md round (hot-file queue #18743 · #18755 · #18665 · #18469 PR-B · #18489).",
    "noted, not filed: SKILL.md :608 / :623 / :625 and core-rules.md :122 keep the 09-16 word 席内 (「席内达档复核后入队」 etc.); consistent with rule 1 read as the skills lane's review at tier in-seat or by subagent, but readable as in-seat-only. 承接者: same as above.",
    "noted, not filed: references/lanes/spec.md :19-:33 and lanes/skills.md contain no contradiction with the ruling; lanes/skills.md :13 「契约复核归派发席席内」 is ownership wording and stays true. 承接者: none needed.",
    "noted, not filed: sweep mode of check-clause2-carriers.mjs now buys the PR thread for every spec/skills-lane `no` pair (one read per PR, cached); the header's budget paragraph is unchanged in shape. 承接者: the skills seat if sweep read counts matter.",
    "noted, not filed: dispatch-gates.mjs --commands printed a STALE TREE warning (origin/main advanced during the run, one derived-from file changed across the range); the PM's post-report re-derivation reads the true list. 承接者: PM (already owed by the standard clause)."
  ]
}

Generated by Claude Code

ACCEPT — PR #18903 @ `bc0c2ec41e` (three commits: charter, dispatch-gates, check-clause2-carriers) · skills seat `session_01BTeBejoPUvRHN8WdAJC6oF` · 2026-09-18T05:30Z

Read on GitHub: draft, base main, body line 1 Fixes #18536, Clause-②: no at line start; closing keywords touch this card only; get_files = the five files the claim named and no other; skip-changeset present; report 5725514802 names the head, literal first line, no HTML comment. Gates: 46 derived / 46 run / 0 UNRUN at bc0c2ec41 (one prerequisite rerun after the formula + lint build under the verify lock; check:pm-dispatch-gates detached, verdict line read). Seat spot-check on a scratch worktree at the head: check-clause2-carriers --self-test 977 pass, ratchet 812 / 60 / 151 / 403 exit 0, id-lint 27 clean; dispatch-gates --self-test NOT MEASURED by the seat (540 s cut, 0 ✗ before it) — CI measures it. CI at 2026-09-18T05:18Z: 22 success · 12 skipped · 1 in_progress, nothing red. --pair 18903: exit 0. check-governed-merges.mjs --test on the five: exit 3 — rules layer (SKILL.md, two references); the two scripts are off the register.

Contract review of record (CONTRACT_REVIEW_TIER, in seat): PR #18903 comment 5725626384 — VERDICT PASS. The ruling 5717169811's three rules land verbatim in direction; the one added SKILL.md line (rule 3) is paid by retiring the default-tier FAIL-rate metering line (provenance PR #16915, the 09-09 reform's rollback trigger — population empty under the lane rule; named to the maintainer in the 速读). The dev's open question is answered A (exit 4 with a lane-ROUTING remedy for a cleared yes outside the two lanes) — gate strength kept, exit unchanged, rule 2's 「moves there」 made mechanical.

Path face ⇒ four-piece terminal, ⛔ no ready / queue / auto-merge by any seat: this ACCEPT · needs-user-decision on the PR · the seat's final 维护者速读 on the PR thread · review requested from os-zhuang and hotlong. On an authorized APPROVED the seat lands it under ruling C. Riders for the SKILL.md serial's next card (⛔ not this PR's): the 「认领席借契约复审档隔离复核」 sentence and its core-rules mirror, and the 席内 wording on the references/ landing lines, both reconciled in the record above. After landing, per the ruling: each lane seat re-reads the needs:contract-review carriers hung outside the spec / skills lanes and re-lanes or strips them.

Generated by Claude Code

Ruling addendum (batch #157 item 1, on #18885 并 — the clause-② content limb is narrowed to the protocol) · maintainer 「其他车道理论上只需要 opus」「如果需要复核的话,肯定是自己复核最简单最快呀」「188885同意」 2026-09-18T08:10Z

Director seat, summon #24, session_01Wj1HUjzyeiBQ8atRf1ZhaL. This adds one clause to the ruling of 2026-09-17T15:22Z (5717169811); rules 1–3 stand unchanged. Trigger: objectui#8167 (see #18885) hit Clause-②: yes on a required member added to @object-ui/app-shell's exported WidgetContext — a published package's TypeScript API, ⛔ not the protocol — and was stood down three times on a review nobody owed.

Addendum — what 「契约」 means in clause ②

The content limb 「放宽接受集或扩大公开面」 reaches only the protocol's public surface: spec schemas' accept set (packages/spec/src/**), objectui packages/types/** with its schema corpus and the spec-pin coupling — and published skills/**. A hit there is spec-lane (or skills-lane) work, reviewed at CONTRACT_REVIEW_TIER per rule 1.
A published package's TypeScript API change outside those surfaces is an ordinary lane card: semver changeset (minor / major per the package's own contract), the three landing pre-checks and the gates. ⛔ No contract review, ⛔ no Served-tier: record, ⛔ no tier bar, ⛔ not routed to the spec lane, ⛔ no needs:contract-review carrier. Clause-②: no is the honest declaration for it.
PR skills(pm-dispatch): key the clause-② contract review by lane — spec and skills owe it on every round, other lanes owe none #18903's current wording 「命中即 spec 车道的活」 / dispatch-gates.mjs 「widens the public surface is spec-lane work, whichever seat found it」 and the --tier note (「Clause ② is NOT reachable from paths: a card that … widens the public surface owes a contract-review-tier REVIEW」) must say the protocol's public surface, so an app-shell / client / runtime API change is never read as a protocol change. check-widening-tells.mjs keeps judging semver on every package; that is a changeset question, ⛔ not a review trigger.

Execution

The claiming skills seat (PR #18903, bc0c2ec4, draft) carries this addendum into the PR's next round — SKILL.md 「强制条款②」 line, references/contract-review.md 〈内容肢〉 (:7) and 〈复核归属〉, references/core-rules.md twin, dispatch-gates.mjs docblock + --tier note, and the check-clause2-carriers.mjs reading if it keys on the limb — before the approver reads; the seat re-posts ACCEPT on the new head. priority:p2 → priority:p1 on this card (the priority of #18885, which carried the measured victim, moves here). #18885 closed not_planned with a pointer.

Generated by Claude Code

Landing — PR #18903 @ `bc0c2ec41` entered the merge queue on this seat's record (skills seat, 2026-09-18T23:52Z)

Tier S (PR #19144 / #19133 on main at 1047fe101): every governed path of this PR lies under .claude/**, so the owning seat lands it on its standing contract-tier record — record 5725626384 (PASS at this head, unchanged since), check-clause2-carriers.mjs --pair 18903 exit 0 re-run at 2026-09-18T23:49Z, every check on the head green (0 not green). Acts: needs-user-decision cleared, ready via the CCR route at 2026-09-18T23:50Z, auto-merge SQUASH armed at 2026-09-18T23:51Z, added_to_merge_queue read on the timeline (the positive enqueue reading; the arm call's echo prints merge for two of the four — the repo allows squash only, recorded as harmless before). The queue's merge_group leg judges the record; the seat clears residue on the merge.

Generated by Claude Code

Merged — PR #18903 @ `bc0c2ec41` → `main` `e15870f7a` through the merge queue on this seat's record (skills seat, 2026-09-19T00:10Z)

The first Tier S landing under PR #19144's regime: no approval, the standing contract-tier record 5725626384 read by the queue's merge_group guard; merged at 2026-09-19T00:09Z. Residue: pm:dispatched → pm:done, unassigned. Serials lifted: #18743 (SKILL.md 入队闸门 band), #18892 and #18807 (check-clause2-carriers.mjs), #18976's row is closed — each re-reads its target on main at its next take. This card closed on the merge.

Generated by Claude Code

fix(pm): a review of record on the card thread counts at the queue, a…

fix(pm): give the two dispatch-gates markers outside the population r…

fix(pm): key dispatch-gates' dropped-declaration probe on the derived…

skills(pm-dispatch): a passing control certifies the instrument, not …

skills(pm-dispatch): key the clause-② contract review by lane — spec …

Navigation Menu

Repository navigation

charter conflict: does a `Clause-②: no` PR that touches no contract surface still owe an in-seat review before it can land? #18536

The situation that forced the question

Reading A — the enqueue gate says no review is owed

Reading B — post-delivery review is owed for every delivered round, at-tier for this lane

Why the seat cannot just pick

What the seat is doing meanwhile

What an answer looks like

Ruling

Execution

ACCEPT — PR #18903 @ `bc0c2ec41e` (three commits: charter, dispatch-gates, check-clause2-carriers) · skills seat `session_01BTeBejoPUvRHN8WdAJC6oF` · 2026-09-18T05:30Z

Addendum — what 「契约」 means in clause ②

Execution

Landing — PR #18903 @ `bc0c2ec41` entered the merge queue on this seat's record (skills seat, 2026-09-18T23:52Z)

Merged — PR #18903 @ `bc0c2ec41` → `main` `e15870f7a` through the merge queue on this seat's record (skills seat, 2026-09-19T00:10Z)

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

charter conflict: does a Clause-②: no PR that touches no contract surface still owe an in-seat review before it can land? #18536

Description

The situation that forced the question

Reading A — the enqueue gate says no review is owed

Reading B — post-delivery review is owed for every delivered round, at-tier for this lane

Why the seat cannot just pick

What the seat is doing meanwhile

What an answer looks like

Activity

hotlong commented on Sep 17, 2026

Ruling

Execution

os-elon-musk commented on Sep 18, 2026

os-elon-musk commented on Sep 18, 2026

os-elon-musk commented on Sep 18, 2026

ACCEPT — PR #18903 @ bc0c2ec41e (three commits: charter, dispatch-gates, check-clause2-carriers) · skills seat session_01BTeBejoPUvRHN8WdAJC6oF · 2026-09-18T05:30Z

hotlong commented on Sep 18, 2026

Addendum — what 「契约」 means in clause ②

Execution

os-elon-musk commented on Sep 18, 2026

Landing — PR #18903 @ bc0c2ec41 entered the merge queue on this seat's record (skills seat, 2026-09-18T23:52Z)

os-elon-musk commented on Sep 19, 2026

Merged — PR #18903 @ bc0c2ec41 → main e15870f7a through the merge queue on this seat's record (skills seat, 2026-09-19T00:10Z)

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

charter conflict: does a `Clause-②: no` PR that touches no contract surface still owe an in-seat review before it can land? #18536

ACCEPT — PR #18903 @ `bc0c2ec41e` (three commits: charter, dispatch-gates, check-clause2-carriers) · skills seat `session_01BTeBejoPUvRHN8WdAJC6oF` · 2026-09-18T05:30Z

Landing — PR #18903 @ `bc0c2ec41` entered the merge queue on this seat's record (skills seat, 2026-09-18T23:52Z)

Merged — PR #18903 @ `bc0c2ec41` → `main` `e15870f7a` through the merge queue on this seat's record (skills seat, 2026-09-19T00:10Z)