docs: shorten oa project node names

2026-06-14 04:34:41 +00:00
parent 9388cb0196
commit 575fa2d7c9
3 changed files with 22 additions and 18 deletions
@@ -24,11 +24,11 @@ Use this skill to keep HWLAB Cloud M1 project management centered on a stable ma

 ## Canonical HWLAB Issue Anchors

- L0 master specification: `PJ2026-01`, `pikasTech/HWLAB#1194` (`HWLAB 总项目规格（L0）：云端硬件研发平台总控`).
+- L0 master specification: `PJ2026-01`, `pikasTech/HWLAB#1194` (`HWLAB 总规格`).
 - Long-term navigation board: `pikasTech/HWLAB#645` (`HWLAB 长期总面板`). This is a board, not the specification.
 - Current Cloud M1 phase specification: `pikasTech/HWLAB#644` (`HWLAB Cloud SPEC / 云平台开发目标 20260601`). This is a phase spec, not an L1 direction.
 - When creating or updating HWLAB project-management issues, link nontrivial L1/L2/L3/L4 work back to `#1194` and keep `#645` as a navigation index only.
- Use the HWLAB hierarchy code on all management issues and specs: project codes use `PJ<YYYY>-<path>`: `PJ` means project, `2026` is the establishment year, HWLAB L0 is `PJ2026-01`; L1 codes are `PJ2026-0101`, `PJ2026-0102`, ...; L2 codes append two digits, e.g. `PJ2026-010102` means HWLAB L1 #01, L2 #02. Continue appending two digits per deeper level.
+- Use the HWLAB hierarchy code on all management issues and specs: project codes use `PJ<YYYY>-<path>`: `PJ` means project, `2026` is the establishment year, HWLAB L0 is `PJ2026-01`; L1 codes are `PJ2026-0101`, `PJ2026-0102`, ...; L2 codes append two digits, e.g. `PJ2026-010102` means HWLAB L1 #01, L2 #02. Durable node short names should usually be no more than 5 Chinese characters; put explanations in descriptions, not names.

 ## Workflow

@@ -33,7 +33,7 @@ Do not store the only copy of a stable requirement in an issue comment. If the r

 ## Current HWLAB Issue Anchors

- L0 master specification: `PJ2026-01`, `pikasTech/HWLAB#1194` (`HWLAB 总项目规格（L0）：云端硬件研发平台总控`).
+- L0 master specification: `PJ2026-01`, `pikasTech/HWLAB#1194` (`HWLAB 总规格`).
 - Long-term board/navigation: `pikasTech/HWLAB#645` (`HWLAB 长期总面板`). Do not treat this as the specification.
 - Cloud M1 phase specification: `pikasTech/HWLAB#644` (`HWLAB Cloud SPEC / 云平台开发目标 20260601`). This is a phase spec, not an L1 direction.
 - New or updated direction/topic/execution issues should include `上级总项目: #1194` unless the user explicitly scopes the task outside HWLAB Cloud M1.
@@ -45,7 +45,7 @@ Do not store the only copy of a stable requirement in an issue comment. If the r
 - L2 topic codes append the L2 two-digit sequence after the L1 code payload: `PJ2026-010101`, `PJ2026-010102`, `PJ2026-010201`, ...
 - L3/L4 persistent management codes continue appending two digits per level, e.g. `PJ2026-01010203` = HWLAB L1 #01 / L2 #02 / L3 #03.
 - Do not renumber existing codes just because priorities change. Add new suffixes for new durable nodes; execution-only PRs or one-off smokes may reference the nearest persistent code instead of receiving their own code.
- Issue titles should start with the code when the issue is a durable L0/L1/L2/L3 management node, e.g. `PJ2026-010102 PLC 71-FREQ AO ioProbe 造模`.
+- Durable node short names should usually be no more than 5 Chinese characters. Issue titles should start with the code and short name, e.g. `PJ2026-010102 频源造模`; put detailed explanations in the body.

 ## Suggested HWLabOA Structure

@@ -104,12 +104,12 @@ Do not use any of these as L1 directions:

 Typical HWLAB Cloud M1 directions:

- `PJ2026-0101` Cloud AI hardware-development workflow: user request, workspace, Code Agent implementation, review, collaboration, delivery.
- `PJ2026-0102` Real hardware access and auditable validation loop: target device, debug probe, io probe, CaseRun, low-noise evidence.
- `PJ2026-0103` Multi-user cloud service and commercial metering: auth, API keys, credit, usage ledger, billing, admin operations.
- `PJ2026-0104` Execution substrate and resource orchestration: AgentRun/HWPOD/Code Agent runtime assembly, sessions, provider profiles, bundles, recovery.
- `PJ2026-0105` Capability accumulation, training feedback, and quality control: harness cases, failure taxonomy, review, reusable templates, model/tool improvement.
- `PJ2026-0106` User product surface and collaboration experience: Web/CLI/API workflows that expose the above capabilities to users.
+- `PJ2026-0101` 云智研: cloud AI hardware-development workflow; user request, workspace, Code Agent implementation, review, collaboration, delivery.
+- `PJ2026-0102` 硬验闭环: real hardware access and auditable validation loop; target device, debug probe, io probe, CaseRun, low-noise evidence.
+- `PJ2026-0103` 用户计量: multi-user cloud service and commercial metering; auth, API keys, credit, usage ledger, billing, admin operations.
+- `PJ2026-0104` 执行编排: execution substrate and resource orchestration; AgentRun/HWPOD/Code Agent runtime assembly, sessions, provider profiles, bundles, recovery.
+- `PJ2026-0105` 能力沉淀: capability accumulation, training feedback, and quality control; harness cases, failure taxonomy, review, reusable templates, model/tool improvement.
+- `PJ2026-0106` 产品协同: user product surface and collaboration experience; Web/CLI/API workflows that expose the above capabilities to users.

 ### L2 Topic

@@ -3,9 +3,10 @@
 ## L0 Master Specification Skeleton

 ```markdown
-# HWLAB Cloud M1 Master Specification
+# HWLAB Master Specification

 编号: PJ2026-01
+短名: HWLAB

 ## 1. Mission

@@ -25,12 +26,12 @@ One paragraph describing the product and research objective.

 | Level | Title | GitHub issue | Spec section | Current status |
 | --- | --- | --- | --- | --- |
-| L1 | PJ2026-0101 Cloud AI hardware-development workflow | TBD | ... | ... |
-| L1 | PJ2026-0102 Real hardware access and auditable validation loop | TBD | ... | ... |
-| L1 | PJ2026-0103 Multi-user cloud service and commercial metering | TBD | ... | ... |
-| L1 | PJ2026-0104 Execution substrate and resource orchestration | TBD | ... | ... |
-| L1 | PJ2026-0105 Capability accumulation, training feedback, and quality control | TBD | ... | ... |
-| L1 | PJ2026-0106 User product surface and collaboration experience | TBD | ... | ... |
+| L1 | PJ2026-0101 云智研 | TBD | ... | ... |
+| L1 | PJ2026-0102 硬验闭环 | TBD | ... | ... |
+| L1 | PJ2026-0103 用户计量 | TBD | ... | ... |
+| L1 | PJ2026-0104 执行编排 | TBD | ... | ... |
+| L1 | PJ2026-0105 能力沉淀 | TBD | ... | ... |
+| L1 | PJ2026-0106 产品协同 | TBD | ... | ... |

 ## 5. Global Acceptance Criteria

@@ -70,6 +71,7 @@ One paragraph describing the product and research objective.
 原因: 本 issue 是 HWLAB Cloud M1 总项目管理锚点，代码变更由下级 issue/PR 承载。

 编号: PJ2026-01
+短名: HWLAB
 上级面板: #645
 当前 L0 总规格: #1194
 总规格文档: <HWLabOA path or GitHub URL>
@@ -88,7 +90,7 @@ One paragraph describing the product and research objective.

 方向判定: L1 必须是直接服务 L0 的能力域；文档整理、项目管理、看板维护、skill 维护、仓库名、工具名和临时执行路径不得作为 L1。

-编号规则: 项目编号格式为 PJ<立项年份>-<层级路径>；PJ 表示项目，HWLAB L0 为 PJ2026-01；L1 为 PJ2026-0101；L2 继续追加两位，例如 PJ2026-010102 表示 HWLAB L1 第 1 个方向下的第 2 个 L2 课题；更深层级继续每级追加两位。
+编号规则: 项目编号格式为 PJ<立项年份>-<层级路径>；PJ 表示项目，HWLAB L0 为 PJ2026-01；L1 为 PJ2026-0101；L2 继续追加两位，例如 PJ2026-010102 表示 HWLAB L1 第 1 个方向下的第 2 个 L2 课题；更深层级继续每级追加两位。短名一般控制在 5 个中文汉字以内，解释写入正文说明。

 ## 全局验收

@@ -113,6 +115,7 @@ One paragraph describing the product and research objective.
 原因: 本 issue 是方向级项目管理锚点，代码变更由下级 topic/subtopic issue 承载。

 编号: PJ2026-010N
+短名: <5字以内>
 上级总项目: #1194
 总规格文档: <HWLabOA path or GitHub URL>

@@ -151,6 +154,7 @@ One paragraph describing the product and research objective.
 目标合并分支: <repo branch/lane>

 编号: PJ2026-010N0M
+短名: <5字以内>
 上级总项目: #1194
 所属方向: #...
 所属课题: #...