governance

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

Keep the system consistent as it grows. Apply versioning, contribution, and deprecation rules.

在设计系统发展过程中保持一致性。应用版本管理、贡献和弃用规则。

Read
```
workflows/governance.md
```
(SemVer table, contribution workflow, deprecation policy, change comms).
Classify the change: major (breaking — renamed/removed token or prop, changed anatomy/default), minor (additive — new token/component/variant/optional prop), patch (fix — contrast/bug/doc/value tweak in tolerance).
For a new component/token: confirm it serves a real, repeated need (≥ 2 places) before promoting product → candidate → core. Design it to the full quality bar (
```
.claude/rules/components.md
```
→ Component Quality Bar).
For a deprecation: mark with reason + replacement + removal version; keep working ≥ 1 minor cycle; provide a migration map (
```
design-systems/crosswalk.md
```
style); remove only in a major.
Wire any new file into
```
CLAUDE.md
```
(File Reference Map + relevant table/router) and add a changelog entry.

阅读
```
workflows/governance.md
```
（包含SemVer对照表、贡献工作流、弃用策略、变更沟通相关内容）。
对变更进行分类：major（破坏性变更 —— 重命名/删除token或prop、更改组件结构/默认值）、minor（新增性变更 —— 新增token/组件/变体/可选prop）、patch（修复性变更 —— 对比度/bug/文档/在容差范围内的数值微调）。
对于新增的组件/token：先确认它能满足真实的、可复用的需求（至少在2个场景中使用），再按照「产品级 → 候选级 → 核心级」的路径晋升。需按照完整质量标准进行设计（参考
```
.claude/rules/components.md
```
→ 组件质量门槛（Component Quality Bar））。
对于弃用操作：需标注弃用原因、替代方案以及移除版本；至少在1个minor版本周期内保持可用；提供迁移指引（参考
```
design-systems/crosswalk.md
```
的格式）；仅可在major版本中执行移除。
将所有新增文件接入
```
CLAUDE.md
```
（文件参考映射 + 相关表格/路由），并添加一条变更日志记录。

Change has a SemVer level and a changelog entry.
Removals have a deprecation window, a replacement, and a migration table.
New spec meets the 8-state + a11y + token-mapping bar and is reachable via the router.
```
python3 scripts/validate_tokens.py
```
passes; contrast re-checked if colors changed.