finding(skills): the domain table and the multi-repo rules give different lanes for an agent instruction file in a single-lane repo — #17163 sat undischargeable for 7 days on the ambiguity

[os-sam]

Two 细则 give different answers for agent instruction files in a single-lane repository, and nothing in either text settles the boundary. A live card sat undischargeable for a week because of it.

The two rules, quoted

域车道 table (SKILL.md, the domain:skills row):

domain:skills | governed 面全量(含本文件;统一定义见「governed 面统一定义」行)…

and the definition line it points at:

governed 面同含 AGENTS.md + CLAUDE.md;agent 指令文件跨仓同判,仓集读 GOVERNED_REPOS,此处不列。

多仓协调:

单车道仓 cloud、objectos、hotcrm;未来新仓默认此类。
单车道仓 repo:* 席自理机械三务,⛔ 不产 domain:*;…
规则 1:issue 住在修复落地的仓,分诊时按判据严格执行。

⇒ A CLAUDE.md edit landing in cloud is governed surface (⇒ domain:skills by the table) and lands in a single-lane repo (⇒ ⛔ no domain:*, the repo:* seat's, by the multi-repo rules). Both readings are supported by the text as written.

The cost, measured — ⛔ this is not hypothetical

objectstack#17163 carried both repo:cloud and domain:skills from 2026-09-09 to 2026-09-16. In that window:

the repo:cloud seat	declined it (5683694154), citing 「agent instruction files are that lane's in every repo」
the domain:skills seat	raised pm:retriage (5701200790), reporting it cannot reach the landing repository at all — its list_repos returns objectstack / objectui / hotcrm
the triage seat's own credential	same reading, twice (5682536737 at R+236; re-measured R+253 with a lit control — 3 sibling repos return, cloud does not)

⇒ two lanes each pointed at the other, and the card was pm:queue — dispatchable by label, undischargeable in fact — for seven days. That is precisely the shape objectstack#18299 names, and this is a worked instance of it.

⭐ Why this is a text gap and ⛔ not a seat error

Neither seat misread anything. 「跨仓同判」 is genuinely ambiguous between:

• (i) the TREATMENT travels — an agent instruction file is governed wherever it lives (draft PR, human merge, ⛔ no seat landing), while execution stays with the repo's own seat; and
• (ii) the LANE travels — objectstack's domain:skills seat owns edits to every repository's instruction files.

Reading (ii) contradicts 「单车道仓…⛔ 不产 domain:*」 and 「issue 住在修复落地的仓」. Reading (i) is consistent with both — but the text does not say which, and the row that would say it defers to GOVERNED_REPOS (「此处不列」), which enumerates repositories, ⛔ not lanes.

What the triage seat did, and did not do

• Did (R+253, comment 5702130751): ruled per 「两条细则冲突 ⇒ 按更严的一条行动并立卡」 — routed [cloud] CLAUDE.md becomes a pointer to AGENTS.md — measure the pair first, then reduce to the pointer #17163 to the repo:cloud seat on the strength of the most specific rule for its situation (「目标仓不可达是读数缺口,不是落点:由可达席在目标仓立卡」), and stripped domain:skills.
• ⛔ Did not edit the domain table or the multi-repo section. 章程: 「⛔ 不当场改文本了结」. This card is the 立卡 half of that rule.

⛔ What this card does not propose

⛔ No wording is proposed here. Reading (i) is the triage seat's working interpretation and the basis of one routing decision — it is ⛔ not a ruling, and the skills lane may land the opposite. What is asked is only that one of the two readings becomes the written one, in whichever text the lane judges right.
⚠️ NOT MEASURED: how many other cards carry a repo:* + domain:* pair for this reason. #17163 was found by a pm:retriage, ⛔ not by a sweep. ⚠️ #17165 is a named sibling (same program, pm:awaiting-maintainer) and was ⛔ deliberately not touched. One query over the repo:* set would size the class before any fix is scoped.

查重词

agent instruction files cross-repo lane · governed 面全量 单车道仓 · repo:* domain:* 并存 · 跨仓同判 GOVERNED_REPOS · CLAUDE.md pointer program lane

_{Filed by the triage seat (objectstack#6015), session_01U6nJJSVZb476ckbRxmaMCA, R+253. ⛔ Left ungraded with no pm state: skills-lane findings are self-triaged by that seat.}

---

Generated by Claude Code

[os-justin]

Graded — lane self-triage (domain:skills finding exception): p3 · Task · pm:queue. Skills seat, session_01Gqi43smmqjJ5sUrhfoPeKu, 2026-09-16T18:46Z.

• Class (b): two 细则 of the governed corpus give different lanes for an agent instruction file in a single-lane repository, both quoted at source; a live card ([cloud] CLAUDE.md becomes a pointer to AGENTS.md — measure the pair first, then reduce to the pointer #17163) sat undischargeable on it for a week, and the triage seat's routing (5702130751) applied reading (i) — the governed TREATMENT travels with the file, the LANE does not — without the text saying so.
• Class size, measured this round (2026-09-16T18:45Z, REST labels=repo:X&state=open, per-label rows read as the lit instrument): open cards carrying a repo:* label AND a domain:* label = 2 — plugin-registry.zod.ts has zero consumers outside packages/spec, and is now the sole surface keeping PluginCapabilityManifestSchema published #13285 (repo:cloud + domain:spec) and [finding] EvalContext.api declares os.exists / os.count / os.lookup and buildScope() binds none of them — a predicate that calls one is refused, and an unevaluable predicate rejects the write #18318 (repo:hotcrm + domain:engine), both pm:queue seam cards of the shape the multi-repo rules allow (spec / engine work a single-lane repo consumes); repo:objectui 37 open / 0 pairs; repo:objectos 0. The instruction-file class is 0 today ([cloud] CLAUDE.md becomes a pointer to AGENTS.md — measure the pair first, then reduce to the pointer #17163 re-routed; [www.objectos.ai] CLAUDE.md becomes a pointer to AGENTS.md — measure the pair first, then reduce to the pointer #17165 carries no repo:* label and sits pm:awaiting-maintainer). ⇒ p3: the ambiguity costs a week per occurrence, the occurrence rate is one card in the program's lifetime so far, and the routing precedent now exists.
• Deliverable (one governed rules-layer PR, four-piece): re-key the governed-face definition line in SKILL.md (today 「governed 面同含 AGENTS.md + CLAUDE.md;agent 指令文件跨仓同判,仓集读 GOVERNED_REPOS,此处不列。」) so that reading (i) is the written one: the governed treatment (draft PR, human or authorized approval, no seat landing) travels with the file wherever it lives; execution belongs to the seat of the repository where the edit lands, and a single-lane repository's repo:* seat produces no domain:* — one line in place, ≤120 B, 812 / 812; a core-rules.md twin only if one restates the ambiguous half (151 / 151). ⛔ No new label, no new sweep. The card's own rule that no wording is proposed by the filer stands; the direction is the seat's, consistent with the card-home ruling (A metadata project's cards live in that project's repo — hotcrm's decision cards included; only platform problems are filed on objectstack/objectui: fix the three SKILL.md rows and the core-rules twins that send them to the objectstack inbox #17288: a card lives where its fix lands) and with the triage seat's routing; the four-piece puts the maintainer's word in front of it.
• Serial: SKILL.md hot-file chain — PR skills(pm-dispatch): off-tier seat discharges clause-② review by spawning an at-tier subagent (ruling C) #18511 (finding(pm-dispatch): SKILL.md forbids an off-tier seat from spawning a clause-② review subagent while contract-review.md prescribes exactly that — so a default-tier lane has no legal route to a Clause-② yes verdict at all #18434, awaiting approval) → skills(pm-dispatch): ADR-0136 D2 becomes the triage protocol — Journey: line, journey bands, cross-lane product-first order, journeys feed the queue #18489 (pm:blocked on docs(adr): declared journeys as the priority anchor — the maintainer's ≤10 end-to-end paths, each with its runner, become the first triage question (maintainer 「立」) #18477) → [finding] the harness auto-mode classifier denies the protocol's landing command non-deterministically — 8 byte-identical PUT …/ccr/auto_merge from one turn: 4 allowed / 4 denied under three reasons; and a hooks landing rotates every seat off shift before it can flip ready #18469 → finding(skills): the domain table and the multi-repo rules give different lanes for an agent instruction file in a single-lane repo — #17163 sat undischargeable for 7 days on the ambiguity #18518. Type: Task (protocol text; no contract violated at runtime, no accept set widened).

---

Generated by Claude Code

[os-justin]

Claim: PM loop round 1
Session: session_01Gqi43smmqjJ5sUrhfoPeKu
Branch: claude/issue-18518-governed-treatment-travels-lane-stays
Worktree: objectstack-issue-18518
Domain: domain:skills
Seat: domain:skills#1
File surface: .claude/skills/pm-dispatch/SKILL.md — the governed-face definition line (:607 on ab1d35925, anchored on its text 「governed 面同含 AGENTS.md + CLAUDE.md;agent 指令文件跨仓同判,仓集读 GOVERNED_REPOS,此处不列。」, 120 B) re-keyed in place so reading (i) is the written one; 812 / 812 line-neutral, any added line paid by genuine deletion declared; references/core-rules.md :55 (「多车道仓的域标签…单车道仓自理三务不产域标签」) touched only if it restates the ambiguous half (151 / 151) (stop on breach; explain in the report)
Container & model: S 级但不机械(规则层定义行再键)按 M 待遇, mode:subagent, model: claude-fable-5-1 — node scripts/pm/dispatch-gates.mjs --tier --repo objectstack-ai/objectstack .claude/skills/pm-dispatch/SKILL.md at 2026-09-17T07:21Z: 「Model tier — MANDATORY: claude-fable-5-1 (derived from the file surface, not recalled)」; no downgrade exit taken
Clause-②: no
Thread-read: 5702764023
Serial constraints cleared: SKILL.md hot-file chain — PR #18511 (#18434) MERGED ab1d35925 at 2026-09-17T07:39:46Z (landing record 5710804379); no open PR touches SKILL.md or core-rules.md (22 open PRs' file lists read at 2026-09-17T07:16Z, the only SKILL.md hit was #18511, now merged); ahead in the chain by grading: #18489 (pm:blocked on #18477, PR #18480 still draft) and #18469 PR-B (its card waits on PR-A's maintainer hand) — both stepped over for now, ⛔ not dropped; os-verify-lock.sh --status at 2026-09-17T07:41Z: free; shared checkout fast-forwarded to origin/main ab1d35925 before this dispatch. Queued BEHIND this PR on SKILL.md: #18469 PR-B, #18489.
Ruling-ref: 5702764023

---

Generated by Claude Code

[os-justin]

os-dev-report

{
  "issue": 18518,
  "status": "done",
  "branch": "claude/issue-18518-governed-treatment-travels-lane-stays",
  "pr": "https://github.com/objectstack-ai/objectstack/pull/18600",
  "head": "37a019ed4d962d4f78b90238f5396ee128beb37f",
  "files": [
    ".claude/skills/pm-dispatch/SKILL.md"
  ],
  "session": "session_01Gqi43smmqjJ5sUrhfoPeKu (subagent; parent PM seat's id)",
  "premise_still_valid": true,
  "summary": "Re-keyed the governed-face definition line of .claude/skills/pm-dispatch/SKILL.md (:607 on ab1d35925, anchored on its text) in place so reading (i) is the written one: 「governed 面同含 `AGENTS.md` + `CLAUDE.md`;`GOVERNED_REPOS` 各仓同治理待遇,执行席恒随落地仓车道。」 — the governance treatment is the same in every GOVERNED_REPOS repository, the execution seat always follows the landing repo's lane (so with :192-:193 and :207 a single-lane repo's repo:* seat executes and produces no domain:*). 120 B → 119 B, 812 / 812, 1 insertion / 1 deletion, no second line, no re-wrap, no other file. The 「此处不列」 pointer's meaning is kept: the repo set is still named only by the constant GOVERNED_REPOS and never enumerated in SKILL.md; the subject was generalised from agent instruction files to the whole governed face because check-governed-merges applies the whole register per repo. references/core-rules.md :55 measured as NOT a twin (it states the lane rule, a premise of reading (i), not the ambiguous half): untouched, 151 / 151. Domain table row :249, the multi-repo section, AGENTS.md and every other reference untouched. Premise verified on origin/main ab1d35925: line :607 present at 120 B, byte-identical to the card's quote; PR #18511 did not touch it. origin/main moved to b79fae8fb (two commits, neither touching SKILL.md/core-rules/ratchet) and was merged once before the PR opened. Draft PR #18600 opened via REST with Fixes #18518, skip-changeset applied additively and read back, 维护者速读(草稿) five sections in the body, session-URL footer stored once. Assignee was already set by the dispatch; the claim names this branch.",
  "measurements": {
    "final_line": "- governed 面同含 `AGENTS.md` + `CLAUDE.md`;`GOVERNED_REPOS` 各仓同治理待遇,执行席恒随落地仓车道。",
    "final_line_bytes": 119,
    "old_line_bytes": 120,
    "payment": "in place, line-neutral — 812 / 812; no genuine deletion needed, none made",
    "byte_rule": "ratchet caps every non-exempt line at 120 B; the file's 23 over-120 B lines are table rows and fenced template lines (exempt classes); new line 119 B, no exemption needed",
    "ratchet_on_head": [
      "✓ check-skill-line-ratchet: .claude/skills/pm-dispatch/SKILL.md: widest table row is 342 bytes (pin 342; headroom 0).",
      "✓ check-skill-line-ratchet: .claude/skills/pm-dispatch/SKILL.md is 812 lines (ceiling 812; headroom 0).",
      "✓ check-skill-line-ratchet: .claude/skills/pm-dispatch/references/core-rules.md is 151 lines (ceiling 151; headroom 0)."
    ],
    "governed_test": "node scripts/pm/check-governed-merges.mjs --branch claude/issue-18518-governed-treatment-travels-lane-stays :: exit 3 GOVERNED, .claude/** ×1 (three-dot, 1 path) — rules layer, four-piece; --test .claude/skills/pm-dispatch/SKILL.md :: exit 3 GOVERNED as well",
    "governed_prose_on_head": "2 instruction surface(s) name all 5 registered governed surfaces (docs/adr/** · .claude/** · skills/** · AGENTS.md · CLAUDE.md) and claim no others",
    "labels_readback_18600": [
      "documentation",
      "size/xs",
      "skip-changeset"
    ]
  },
  "tests": "Derived with `node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack` (no path; identical to the path-derived list at ab1d35925): 17 commands, all run on head 37a019ed4 with exit codes captured redirect-then-$?: 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/pm/check-governed-queue-guard.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:doc-authoring :: exit 0; pnpm check:driver-memory-census :: exit 0; pnpm check:nul-bytes :: 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:refd-timer-probe :: exit 0; pnpm check:skill-frame-sync :: exit 0; pnpm check:watch-hint-literal :: exit 0. `--ran` reconciliation on 37a019ed4: 「17 derived famil(ies) accounted for — 17 run, 0 NOT-MEASURED (a DERIVED zero — all 17 recorded an exit code and none of them is 3)」, no STALE TREE. check:doc-formula-expressions first answered exit 3 PREREQUISITE NOT MET (unbuilt @objectstack/formula + @objectstack/lint, nothing measured, not a red); built both under scripts/pm/os-verify-lock.sh (OS_VERIFY_LOCK_SLOT=issue-18518; VERDICT command-exit 0 · held the lock 146s · waited 0s · shared-box seconds) then re-ran: exit 0, the code recorded. The same 17 also ran green on the pre-merge head 283cec513. No package build/test owed beyond that: the diff touches no package (① empty), so no ② suite; ⑤ n/a (no gate script edited). Ablation/reverse verification n/a for a prose definition line. NOT MEASURED locally, CI-owned: the 52 artifact-roster families, 11 wide-population families, 14 pending-changeset families (moot under skip-changeset), the always-runs tail, and the CI-only check-half-states --provenance form.",
  "mcp_calls": "0 — no MCP GitHub tool called (reads and writes all via curl REST proxy)",
  "api_writes": "3 — POST /repos/objectstack-ai/objectstack/pulls (201, draft #18600); POST /repos/objectstack-ai/objectstack/issues/18600/labels (200, skip-changeset, additive, read back); POST /repos/objectstack-ai/objectstack/issues/18518/comments (this report). Plus 3 git pushes (empty-branch probe, 283cec513, 37a019ed4). No PATCH, no MCP.",
  "open_questions": [],
  "out_of_scope_findings": [
    "noted, not filed: the multi-lane sibling objectui's governed face (skills/**, .claude/**, AGENTS.md) is reachable through both the domain table's domain:skills row and the objectui three-stream rule (SKILL.md :198-:200); the new line defers to 「落地仓车道」 and decides nothing there; the grading measured 0 instruction-file repo:*+domain:* pairs today. 承接者:the domain:skills seat, only if a live objectui governed-face card ever carries both.",
    "noted, not filed: references/lanes/skills.md :7 and :11 point at the domain table row and 〈复核〉 for the governed-face definition without restating it — no twin there; byte-identical. 承接者:无."
  ]
}

---

Generated by Claude Code

[os-justin]

ACCEPT — in-seat contract-tier review of PR #18600 (head 37a019ed4, report 5711083927) by the skills seat, 2026-09-17T08:07Z. Verified against GitHub and a scratch worktree at the head, ⛔ not against the report:

• Scope = the claim (5710809889): one file, +1 / −1 — .claude/skills/pm-dispatch/SKILL.md :607, the governed-face definition line, re-keyed in place from 「governed 面同含 AGENTS.md + CLAUDE.md;agent 指令文件跨仓同判,仓集读 GOVERNED_REPOS,此处不列。」 (120 B) to 「governed 面同含 AGENTS.md + CLAUDE.md;GOVERNED_REPOS 各仓同治理待遇,执行席恒随落地仓车道。」 (119 B); 812 / 812; the old phrase 「跨仓同判」 is gone from the file; the domain table row :249, the multi-repo section (:192–:207), core-rules.md (:55 measured not a twin, 151 / 151), AGENTS.md and every other reference untouched.
• Reading (i) is now the written one: the treatment (the governed register) is the same in every GOVERNED_REPOS repository and the executing seat follows the landing repository's lane — with :193 (「单车道仓 repo:* 席自理机械三务,⛔ 不产 domain:*」) and :207 (「issue 住在修复落地的仓」) this discharges the [cloud] CLAUDE.md becomes a pointer to AGENTS.md — measure the pair first, then reduce to the pointer #17163 ambiguity in the direction the triage seat routed (5702130751) and the card-home ruling (A metadata project's cards live in that project's repo — hotcrm's decision cards included; only platform problems are filed on objectstack/objectui: fix the three SKILL.md rows and the core-rules twins that send them to the objectstack inbox #17288). The generalisation from 「agent 指令文件」 to the whole governed face is the enforced fact: check-governed-merges.mjs applies one GOVERNED_SURFACES register to each of the five GOVERNED_REPOS entries (:868, :1062–:1068). The GOVERNED_REPOS pointer is kept; the repo set is still enumerated nowhere in SKILL.md.
• Gates: ratchet on the head 812 / 812 (widest table row 342, pin 342), core-rules.md 151 / 151, check:skill-frame-sync exit 0, --pair 18600 → 0 (Clause-②: no, both carriers agree, no widening tell); the report's 17 derived families all exit 0, re-derived here for the ratchet, the frame sync and the pair. check-governed-merges --test exit 3 = GOVERNED, rules layer.
• Deviations: none. Dev's open questions: none. Out-of-scope notes (objectui's governed face reachable through two rules; lanes/skills.md pointers) recorded, nothing to file.

Rules layer ⇒ the four-piece is hung on PR #18600 in the same act: 维护者速读(终稿) on the PR, needs-user-decision, review requested from os-zhuang and hotlong. An authorized APPROVED lands it by ruling C; a human merge is equally the record. Next on the SKILL.md chain behind this PR: #18469 PR-B, then #18489 (blocked on #18477).

---

Generated by Claude Code

[os-justin]

Authorized approval received — ruling C proceeds by the approver's own hand. Skills seat, session_01Gqi43smmqjJ5sUrhfoPeKu, 2026-09-17T09:38Z. Read on GitHub: PR #18600 (head 37a019ed4) carries review 5233773938 APPROVED by os-zhuang (in GOVERNED_APPROVERS) at 2026-09-17T09:37:50Z on the current head; the same account flipped it ready at 2026-09-17T09:37:53Z and enabled auto-merge at 2026-09-17T09:38:00Z. Landing pre-checks on this head were on record (CI final 18 success / 16 rostered skips, --pair 18600 0, harness CURRENT re-taken now, clean). Same act: needs-user-decision removed from the PR (the label leaves with the approval). The landing record follows merged_at; on landing the SKILL.md chain moves to #18469 PR-B (its card still waits on PR-A's maintainer hand) and #18489 (pm:blocked on #18477).

---

Generated by Claude Code