Repository navigation
[Decision] Setup → Metadata retirement: where the on/off switch of positions, permission sets and sharing rules lives — on the item in Studio (A) or kept in Setup (B) #28559
Description
epic:#28130#1 · hotlong · session_040dfd80c4c9411b895c698e785a6848
Filing gate: ④ child of epic #28236 — a decision the P2/P3 drafting review found undecided by ADR-0146 (cut 2026-11-01 on the maintainer's 「四项提速措施全部按推荐执行」). ⛔ Not a claim.
Part of #28236 (decision M-1) · Governing text: ADR-0146 D1 ("Setup carries no metadata editor and no metadata catalog"), D4 (the operational switch is offered on the item in Studio; the packaged-action switch keeps its disable leg where it is), D7 (⛔ "The redirects do not retire a Setup → Metadata route whose administrative action has no Setup home yet").
Question
Where does the deployment on/off switch of positions, permission sets and sharing rules live after Setup → Metadata retires (#28578)?
Measured (50646f01f2). The switch is ui/packages/app-shell/src/views/metadata-admin/catalog-activation.ts on Setup's catalog item page, served by packages/runtime/src/domains/catalog-activation.ts. The four Setup entries reach those items through ?scope=environment catalog routes. ADR-0146 moved the flow switch to the item in Studio (D4, landed as #28148) and kept the action switch in Setup (D4, out of this epic). It names no home for the catalog types.
Options
| Option | What it means | Work | |
|---|---|---|---|
| A (recommended) | The switch goes with the item, into Studio | On the item page in Studio's Access pillar / All metadata area (#28561), like the flow switch (D4). Setup keeps only the people pages (position holders, permission-set assignment, #28241). #28578 retires all four catalog routes. | Inside #28578 / #28561; no new card |
| B | The switch stays in Setup | Under D7 ⛔ the four catalog entries and routes stay in Setup as a catalog list, which D1 rules out; ADR-0146 would need a carve-out line. | ADR line + Setup keeps four routes |
维护者速读
- 问的是什么： 岗位、权限集、共享规则这三类，管理员可以在本部署把某一项整体「停用」。这个开关今天在 Setup → 元数据的目录项页上。Setup → 元数据要撤（N-28），开关搬到哪里？
- 业务角度： 停用一个权限集是运维动作，但它停用的是一项元数据。流程的同类开关已经按 ADR 搬到 Studio 的项上（Studio: switch a read-only package's flow off for this deployment from the Automations pillar — ledger switch on the item, posture-aware, refusal verbatim #28148），动作的开关留在 Setup（不在本 epic）。这三类 ADR 没写。
- 实际需求： 开关今天在用（Setup 目录页上真实可点），不是投机能力；两种方案都保留它，只是位置不同。
- 长远合理性： A 与 D1「Setup 不放元数据目录」、D4「开关在项上」一致，一个规则管到底；B 要在 ADR 里为这三类开例外，Setup 留下一块目录列表，以后还会有人问「为什么这三类在 Setup」。
- 防 AI 写错： A 只有一个家，AI 写界面时不会在两处各做一个开关；B 让同一类开关分处两个界面，容易写出两套。
- 创业期不扩散： A 不新增任何能力，只是随页面一起搬；B 要多留四条路由和一段 ADR 例外。
- 席位推荐：A。代价：只有 Setup 权限、没有 Studio 权限的管理员，停用这三类时要进 Studio（他们本来就看不到目录列表，ADR 已认这个代价）。
- 等这个答案的： 只有 N-28 的第 2 项（四个目录入口与路由）；N-28 其余部分不等。
How to answer
Reply with the option letter. The PM records it as a Ruled: comment here, copies it into #28578 item 2, and closes this card.
Links back: #28236, ADR-0146 D1 / D4 / D7, #28148, #28241.
Generated by Claude Code
Activity
objectstack-fleet commentedon Nov 1, 2026
triage#1 · os-zhuang · session_01AavokzJ5DndAwitDXvKy4U
Path: none
Triage: lane hygiene ·
domain:uiadded · awaiting the maintainer · 2026-11-01T06:55Z⛔ Not a claim.
ui/packages/app-shell(Setup: retire Setup → Metadata behind redirects into Studio (datasource kept) and retire Packaged automation's flows half; Studio stops linking into Setup #28578 / Studio: an All metadata area in the builder — directory, lists, generic item page, history and diagnostics, per package and across packages; pillar types open their pillar #28561), sodomain:uiis added. Its p1 andneeds-user-decisionstand.Generated by Claude Code
objectstack-fleet commentedon Nov 1, 2026
epic:#28130#1 · hotlong · session_040dfd80c4c9411b895c698e785a6848
2026-11-01T07:03Z
Ruled: A — the on/off switch of positions, permission sets and sharing rules moves with the item into Studio; Setup keeps only the people pages.
Maintainer, in this seat's direct session (epic PM for #28236), verbatim: 「M-1（#28559）裁 A：岗位、权限集、共享规则的启停开关随项目搬到 Studio，Setup 只留人员相关的页面。」
What the ruling binds (Governing text: ADR-0146 D1, D4, D7):
packages/runtime/src/domains/catalog-activation.tsis offered on the item page in Studio (the Access pillar / the All metadata area, Studio: an All metadata area in the builder — directory, lists, generic item page, history and diagnostics, per package and across packages; pillar types open their pillar #28561), the way D4 put the flow switch on the item. The door, its gate and its readings are unchanged; only the surface moves.?scope=environmentcatalog entries and routes, with redirects into Studio: an All metadata area in the builder — directory, lists, generic item page, history and diagnostics, per package and across packages; pillar types open their pillar #28561's area, once the switch is reachable there. No ADR carve-out is needed. D1 ("Setup carries no metadata editor and no metadata catalog") holds as written.setup.accessbut nostudio.accessswitches these items in Studio. The release note says so.The decision is executed by #28578; this card closes as completed.