[决策] `dataset` 要不要一个 Studio Interfaces pillar 落位 —— nav 树无 dataset 成员,而 Metadata Directory 已全功能可编辑(#4019 的 dataset 半)

[yinlianghui]

从 #4019 拆出(objectui 分片 PM,批次 14)。#4019 的 action 半由 PR #4880 落地(designer 的 resolveSurface 缺 action case,致 schema 合法、运行时可派发的 nav action 条目在 Interfaces pillar 恒 disabled —— 已修);dataset 半经 dev 测量不可按卡面「rail 接线」实施,是产品裁定题,移到本卡。

测量事实(dev 实测 origin/main @ 6bb39c4,完整读数见 #4019 的 dev 回报与 PR #4880)

1. Interfaces pillar 的 rail 是 app navigation 树(client.list('app') → appDraft.navigation → NavTree → resolveSurface),不存在「per-type rail load」可 append —— view/page/dashboard/report 也只在 app nav 引用它们时出现。feat(access): localize curated capability labels client-side (#2600 B5 follow-up) #2657 的 08-07 审计 §2(a) 早已记录此事,卡面表述来自七月的过期矩阵。
2. dataset 结构上进不了 nav 树:spec NavigationItemSchema 是 9 成员判别联合(object|dashboard|page|url|report|action|component|separator|group),无 dataset 成员。
3. dataset 今天并非无家:注册表驱动的 Metadata Directory 已可 list/create/edit(审计 §2(b));preview 与 default inspector 均已注册。

三选项(dev 分析,PM 附议其推荐结构)

• A — Interfaces rail 增一个非 nav 的「package surfaces」区段,由注册表 domain: 'ui' 派生驱动(⛔ 手写 action+dataset 两名 —— 那是第六份独立类型枚举,objectstack#6242 已记录五份枚举漂移无门可拦;派生规则让后续 job/role/seed/mapping/datasource 落位卡免费继承)。子决策:同 domain 的 view/page/dashboard/report 是否也列、action 双入口(nav 树 + 区段)重叠是否接受。
• B — spec nav 联合加 dataset 成员:⛔ 建议直接否 —— 本卡明言 no spec change,且运行时无消费者,先造 authoring 面就是 objectstack#6888 刚惩罚过的「designer 教作者写死元数据」(ADR-0078)形。
• C — 裁定 dataset 的家就是 Metadata Directory,dataset 半按「已交付」关闭。审计已把问题从「无家」改写为「无专属 pillar」—— 若 pillar 槽位买不到可测的东西,C 是诚实收法,appetite 留给真买到东西的落位卡。

PM 建议:先答 dev 点出的那个真问题 ——「Directory 已全功能的前提下,pillar 槽位买什么?」有具体答案 ⇒ A(registry 派生形态);没有 ⇒ C。

关联:#4019(action 半,PR #4880)、objectstack#2657(Part A 裁定与 08-07 审计)、objectstack#6242(类型集五份枚举漂移)、#4881(resolveSurface 六种 schema 拒收拼法的休眠限,dev 顺手立)。

[os-steve]

Maintainer ruling (2026-08-17, recorded by PM session session_01DbRmJD3iPhXjKr6vhd4Qkv). The maintainer reviewed the four-card decision-inbox analysis in PM chat and approved its recommendations, verbatim: 「同意」.

Ruled: Option C — dataset's home is the Metadata Directory; the dataset half of #4019 is closed as delivered. Option B (adding a dataset member to the spec nav union) is refused outright — a spec-contract expansion with no runtime consumer.

Rationale on record:

• Zero measured pull: dataset is fully list/create/edit-able in the Metadata Directory today, with preview and default inspector registered; nobody is blocked.
• Coherence: a second entry point (nav tree + rail section) would create the two-surfaces-disagree class this repo keeps paying down; one concept, one home.
• Scope discipline: the pillar slot buys nothing measurable today; appetite stays reserved for a placement card that does buy something.

Reopen condition: if a future need names concretely what the pillar slot buys (e.g. job/role/seed/mapping falling into place), file a new implementation card using Option A's registry-derived (domain: 'ui') section shape as recorded in this card's body — ⛔ not a hand-written two-name list (that would be the sixth independent type enumeration; see objectstack#6242).

Closed as completed under this ruling.

---

Generated by Claude Code

[os-zhuang]

Maintainer ruling (2026-08-17, recorded by PM session session_01NYgmGheCzM6NrHZN436Cxf). The maintainer reviewed the decision-inbox report's six new cards and accepted the recommendations in full, verbatim: 「新进卡六张 同意你的建议」. For this card:

Ruled: Option C — dataset's home is the Metadata Directory; the dataset half of #4019 closes as delivered.

• The pillar-slot question ("Directory 已全功能的前提下,pillar 槽位买什么?") has no concrete answer today — zero measured pull for a dedicated Interfaces placement, and the Directory already provides list/create/edit with preview and inspector.
• Option B (spec nav-union member) stays rejected as filed. Option A's registry-derived form is recorded as the standing mechanism for this family: if a future placement need materialises (dataset or job/role/seed/mapping/datasource), it lands as a registry-domain-derived section — ⛔ never a hand-written type list (the sixth-enum-drift hazard objectstack#6242 documents).

This card closes with the ruling as its record — nothing to build. Closing as completed.

---

Generated by Claude Code