Skip to content

pm-dispatch: the domain table splits the governed-surface mechanism across two lanes — anchor instruction-architecture and governance-enforcement files to domain:skills #9528

Description

@os-zhuang

Blocked-by: #9495

Maintainer ruling (2026-08-18, PM chat, skills-seat session session_01Rn7aaamsR99FXRqLcpL99q), verbatim: 「skills 相关的应该都归你管,为什么派给了 devx」 — stated after a measured collision: the devx lane extended the ADR gate to skills/** (#9511, landed) in the same hours the skills lane retired that gate under the #9495 ruling (PR #9523) — opposite directions on one mechanism, hours apart, because the domain table anchors by file location and the governance mechanism's files sit in devx territory (scripts/ 门禁类, .github/**) while the governed surfaces and protocol text sit in skills territory. AGENTS.md has no owner in the table at all — the skills seat claims it in its seat post, but triage routes from the table, which is how #9403 landed in devx.

Change (the 域车道 table in .claude/skills/pm-dispatch/SKILL.md)

Add to the domain:skills row (and state the boundary in the devx row where needed):

  • AGENTS.md, CLAUDE.md — instruction-architecture files (all agent-facing constitution text);
  • .github/CODEOWNERS — the governance-routing half of the governed surface;
  • governance-enforcement files for the governed surface: the post-merge audit (scripts/pm/check-governed-merges.mjs, already under scripts/pm/**) and any future gate/audit whose subject is the governed surface itself.

Boundary kept honest: domain:devx retains genuine dev-tooling gates (lint machinery, doc gates, scripts/ general 门禁类) — the divider is the gate's SUBJECT: a gate that governs agent-instruction surfaces routes to skills; a gate that governs code/docs quality routes to devx.

Serial constraint: the table lives in SKILL.md, which PR #9523 (the #9495 retirement) currently edits — hard same-file serial, dispatch after #9523 merges. Fable (clause ① path mandate); ADR-class human merge. In-flight devx cards (#9403, #9519) finish where they are per the no-mid-flight-transfer rule; cross-lane coordination notes already on #9513/#9403.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions