Skip to content

pm-dispatch: register the repo:hotcrm lane — 多仓协调 entry + lanes/hotcrm.md charter (maintainer rulings 2026-08-20) #10294

Description

@qq9340100

Filed by the skills seat (session session_019T1sSZbQTnLhrK9HhNdNiB). The repo:hotcrm execution seat is already live (seat post exists, staffed, queue 6) but the lane is in circulation while absent from the protocol text — the exact shape the lane table's own rule forbids (在流通而不在表 = 无主车道). This card lands the registration.

Ruling provenance (逐字,未译;both from the skills-seat chat, 2026-08-20)

  1. 「新增了 hotcrm 仓库的席位,这个仓库作为 objectstack 的样板工程,使用元数据开发crm应用,平台相关的功能应该在平台中实现,hotcrm 主要是展现平台能力,并且不扩散需求。」
  2. 「hotcrm 部署到objectos企业版时,就会有企业版的能力,但是在 objectstack 社区版中也可以运行。」

Scope

A. .claude/skills/pm-dispatch/SKILL.md (682/682 — pay by equal dedup):

  • 多仓协调 intro: hotcrm joins the repo roster as the exemplar app repo (元数据开发的 CRM 样板), outside the spec dependency chain (like objectos); triage seat scope 四仓 → 五仓 (sweep/首触定级/查重/转仓 uniform, no release board unless one is later ruled).
  • Seat roster note: repo:hotcrm = execution seat, full execution-seat discipline (⛔ 不产 domain:*/type/定级).
  • Routing: platform gaps discovered in hotcrm are file-at-destination to the platform repos — the charter forbids workarounds in the exemplar (this is the charter's teeth in triage terms).

B. New references/lanes/hotcrm.md (job description, versioned; enroll in the ratchet CEILINGS at landed count — scripts/pm/check-skill-line-ratchet.mjs edit is the mandatory companion). Charter content, from the rulings:

  • 样板工程: demonstrates platform capability with metadata-first CRM; the app is the showcase, not a feature lab.
  • 平台功能上游: any platform-relevant capability need lands as a card in objectstack/objectui (Blocked-by: back-link), never as a hotcrm workaround.
  • 不扩散需求: startup-scope discipline applies in full — capability expansion default-deny; the four-axis frame's axis ④ is this lane's primary filter.
  • 双版本兼容: hotcrm must RUN on objectstack 社区版; deployed on objectos 企业版 it GAINS enterprise capability. Operationally: hotcrm metadata may depend only on the community capability surface; enterprise features are enhancement-only, never a hard dependency — a hotcrm card that would break community-run is mis-scoped by definition.

Constraints

  • Hard serial: SKILL.md is occupied by the in-flight tiering-revision PR — dispatch after it MERGES, re-measure line budget then.
  • check:skill-frame-sync untouched; governed surface: draft PR, review request os-zhuang, human merge. Model tier at dispatch per the then-current clause ① (this is SKILL.md main-file protocol semantics either way).
  • ⛔ Do not edit the hotcrm seat post (#-referenced from the seat index; single-writer = its sitting PM).

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions