[META] terminology-canonical library long-term governance (residue from #135)

[kiki830621]

Source

Residue from /idd-close #135 (Step 3.6,IC_R011 #105 checkpoint)。

#135 diagnosis comment ### Residue line 2:

Terminology library governance:長期維護權、跨 plugin 共享(若 IDD 跟 spectra plugin 都要用)、versioning policy。初版 seed 6 rows 後的長期治理是 process governance,不是 single PR 能解決。

Background

#135 v4 design D4 設計 initial library:

• Maintainer initial seed(6 rows from [META][idd-issue] terminology trust gap — source 用錯 domain term 時 AI 繼承錯誤 #135 body + #804 incident)
• Rule-of-three promotion threshold
• Open PR contribution

但長期治理問題未解:

• 誰最終裁決新 row 進不進 library?(maintainer 之外有 committee?)
• 跨 plugin 共享 library(IDD + spectra)如何 version 同步?
• Row deprecation policy(過時 misuse 怎麼 retire)?
• Cross-language(English / Japanese / Korean source term)library 設計時機?

Open questions

• Library 是否要 versioning(semver)獨立於 plugin?
• Cross-plugin shared library 放哪裡(top-level npm / monorepo package)?
• Maintainer escalation path(disagreement on row addition)?
• Cross-language audit trail format?

Type

enhancement / governance policy

Priority

P3 — wait for first cross-plugin reuse request(spectra-discuss 是否也要 terminology library?)or first row-deprecation incident before designing。

Refs #135

Current Status

Phase: diagnosed
Last updated: 2026-05-25 by idd-diagnose (batch)

Complexity

Spectra when triggered (parking lot)

Routing

See diagnosis comment Strategy section for explicit WAIT trigger condition + next-step path.

[kiki830621]

Diagnosis

Type

enhancement / governance policy

Analysis

#135 residue 第 2 條 — 「Terminology library governance」horizon。#135 v4 design D4 解決初版 seed 機制(maintainer initial seed + rule-of-three promotion + open PR contribution),但 5 個長期 governance 問題未解:

1. 最終裁決權(committee?)
2. Cross-plugin shared library versioning
3. Row deprecation policy
4. Cross-language(en/ja/ko)source term library 設計
5. Library independent semver vs plugin-version-locked

Issue 自我 framed 完整;這些都是 process governance 問題,不是 single PR engineering。

Strategy

DEFER until 實際 governance friction 出現:

明確 trigger 條件:

• 第 1 個 disagreement 出現(maintainer + contributor 對某 row addition/deprecation 不同意見)→ escalation path 需要
• 第 1 個 cross-plugin library share request(per [META] terminology-canonical.md plugin-level extension architecture (closing follow-up from #135) #143 trigger,可能同時觸發 [META] terminology-canonical library long-term governance (residue from #135) #145)→ versioning policy 需要
• Row count 超過 ~50 → deprecation policy 變實際維護需求
• Cross-language audit trail 首次 user-reported case

Complexity

Spectra when triggered — governance policy 是 plugin-level published contract,影響 cross-plugin coordination。但目前 = parking lot。

Related

緊密 sister with #143(plugin-level extension architecture)— #145 governance 是 #143 architecture 的 dual。實際 implementation 時兩者可能同時 design + bundle 成 1 個 spectra change(architecture + governance together)。

Risks

• R1 Pre-engineering — governance pre-design 易過度規範,真實 friction 出現時規則需重設
• R2 Process governance ≠ tech spec — 部分 questions(誰裁決)本質非 spec 能解(需 actual maintainer community 形成)
• R3 Cross-language premature — IDD 目前 user base 是 zh-Hant + en 雙語,ko/ja 需求純假設

Residue

(NSQL §4.6):「open-source governance is irreducibly social」horizon — 任何 governance spec 都只是建議,真實 decision 由 maintainer + community trust 形成。Spec 是 starting point,不是 ending point。本 issue 不為 social-process 負責。

---

Vagueness Pre-check — Final

• **V1=2\n- **V4=3
• Triggered: no — both axes ≤ 3 (issue self-framed clear with explicit open questions + trigger condition)

Sister Concerns Filed (mid-diagnose, v2.47.0+ #528;v2.72.0+ default-flip #148)

(none surfaced — this issue IS itself a sister of #135 cluster (alongside #136 #137 #143 #144 #145 #146);cross-sister relationships already documented in each diagnose Strategy / Related section. Per IC_R011 §3 exemption "existing issue covers" — no net-new orphan to file.)