spec: a shared picklist (global value set) metadata kind — option lists reused across objects and packages are TypeScript constants today

[os-elon-musk]

Path: 本地跑起来、看到 — records-forms (清单项待写, authored with #19518) | P2

Parent of a cross-layer feature point (ruling batch #209 item 1 · A · maintainer 「18164 同意」): sub-issues in Blocked-by: order — #19518 (spec) → #19519 (runtime) → objectui#10202 (Studio). This card is a coordination node and is never dispatched itself; the road order (behind the open product P0/P1 items) decides when #19518 is taken.

Gap

There is no metadata kind for an option list that several objects share. Checked on @objectstack/spec 17.4.0's dist/index.d.ts and dist/data/index.d.ts: no globalPicklist, valueSet, picklists or equivalent key. An app that wants industry, lead_source, salutation, opportunity_stage or territory to mean the same thing on several objects keeps them as exported TypeScript arrays and spreads them into each Field.select({ options: [...] }).

Evidence (hotcrm, origin/main c716a2c)

• src/objects/_picklists.ts — ~3,001 authored tokens; imported by 17 files: seven objects (account, contact, lead, opportunity, task, event, event_attendee, plus contract and quote), two views, a flow, an action, a dashboard, an import mapping and a locale bundle.
• Under the ADR-0130 package split (Epic: split HotCRM into ADR-0130 packages — sales is the app, service / revenue / marketing are modules, a directory is a package hotcrm#1904) those consumers sit in three packages (sales, revenue, and the app's own dashboards and translations), so the file becomes cross-package source that every module must import from the app package — the shape a metadata kind would replace with a reference by name.
• The same lists are what a customer overlay most often wants to extend (a customer-specific industry or lead-source value), and today that is a source edit in the app, not an overlay (ADR-0005 has nothing to overlay).

Ask

A picklists (or valueSets) stack collection: { name, label, options: SelectOption[] }, owned by a package like any other metadata, referenced from a select field by name (Field.select({ picklist: 'crm_industry' })), translatable through the locale packs the way field options are, and extensible by an org overlay (ADR-0005) so a customer can add a value without forking the object. Salesforce Global Value Sets and Dataverse global option sets are the reference shape.

Dedupe words: global picklist, value set, shared select options, _picklists.ts, picklist metadata kind.

---

Generated by Claude Code

[hotlong]

Ruling: batch #147 item 2 · letter 停放 (parked; the design discussed with the maintainer is recorded here so the restart starts from it) · maintainer 「18164 停放」 2026-09-17T14:09Z

Director seat, summon #24, session_01Wj1HUjzyeiBQ8atRf1ZhaL. Presented in detail; the maintainer first said 「这是非常具体的业务需求,主流平台应该都支持吧,这个应该要开发。你可以和我讨论具体的方案」, the seat laid out a design, and the maintainer then ruled 「18164 停放」 under 「创业期现在不追求功能多,追求稳定」. Under the corrected need standard (5715688324) the need is real (Salesforce Global Value Sets, Dataverse global option sets); the park is a sequencing decision, ⛔ not a judgement that the need is absent.

Ruling — 停放

• needs-user-decision → pm:on-hold. Restart-when (body's leading line): a customer requirement needs a shared option list extended per organization without forking the app, or the maintainer schedules it after the current stability work (package split, can, spec narrowings) lands.
• Meanwhile the reference app keeps its TypeScript constants (src/sales/objects/_picklists.ts, spread at each use site) — a working, non-silent shape.

Design recorded for the restart (discussed on the direct channel; ⛔ not ruled in detail — the three open points are the maintainer's)

1. New metadata kind picklist (name to confirm: picklist vs valueSet): { name, label, description?, options: SelectOption[] } — SelectOption is today's field option shape, ⛔ no new option shape; package-owned, file pattern *.picklist.ts, registered before object in load order.
2. Field reference Field.select({ picklist: 'industry' }), mutually exclusive with options; both or neither on a select type is refused.
3. Server-resolved: field metadata served to clients carries the resolved options, so objectui's renderers, validation and filters are unchanged in phase 1; write validation uses the resolved set.
4. Extension and overlay are additive only: package-level picklistExtensions: [{ extend, options }] (the objectExtensions idiom); per-organization overlay of the same shape in sys_metadata with allowOrgOverride: true and an overlay schema that accepts new values only — removal/rename stays with the owning package (open point: allow the org overlay at all, or package-level extension only).
5. Translation: TranslationData.picklists.<name>.{ label?, options: { value: label } }; a field referencing a picklist inherits it; field-level options translation remains for inline options.
6. Verification (ADR-0136 D2.4): two records-forms checklist items + one dogfood case (one picklist, two objects, org A adds a value, A writes it, B is refused, locale switch relabels); hotcrm migrates its shared lists as the acceptance.
7. Phases: 1 = spec + engine + CLI compile + translation + hotcrm migration (Studio untouched); 2 = Studio picklist page and 「use picklist」 in the object designer. Not in v1: cascading picklists (per-option visibleWhen and dependsOn exist), unrestricted mode, per-record-type value restriction. Open point three: one-page ADR first vs. straight to a card.

---

Generated by Claude Code

[os-steve]

回决策箱(维护者指令,skills 席 2 代执行)— 2026-09-21T03:45Z

出处三件(SKILL.md :149 代执行他人指令,评论带出处三件)— 谁的指令:维护者,在本席(domain:skills seat 2,session_017ETYWqMQD4qMtZzAGovWNi,席位帖 #19287)会话内的真实用户轮次。在哪说:本席会话聊天,2026-09-21,在本席呈交「停放排查」四组清单(全板 165 张停放卡:pm:blocked 64 + pm:on-hold 101;其中 38 张的停放条件已消失——正文与评论里 Blocked-by: / Restart-when: 指向的卡或 PR 全部已关或已合)之后。原话(逐字,⛔ 未翻译、未润色):「还有哪些应该解除停放的你一起排查一下」;对四组清单:「同意」。

本卡属第三组「条件已消失的决策卡 ⇒ 回决策箱」:本席于 2026-09-21T03:00Z 机器复核,本卡停放所指向的目标已全部关闭/合并;卡的本体是一道待维护者裁的题,停放条件消失后它不该继续 hold,而该回到 needs-user-decision 收件箱排批。

动作:停放状态标签一笔换为 needs-user-decision;⛔ 本席不代裁、不派发。所属车道席位或总监席在下次决策批前按 SKILL.md 〈决策箱勤务〉补全四棱卡面块与「维护者速读」(存量卡低频子轮回填);H62 在补全前对本卡报行属正常。

---

Generated by Claude Code

[os-project-manager]

Ruling: batch #209 item 1 · letter A · maintainer 「18164 同意」 2026-09-21T05:05Z

Director seat, summon #25 (session_012GcsUbuqFGBibkEDMRC1eE). Returned to the decision box at 5755100805 under the maintainer's 「还有哪些应该解除停放的你一起排查一下」/「同意」; presented in detail with the recommendation A (facet ①: every mature platform models a shared option list as first-class metadata — Salesforce Global Value Sets, Dataverse global option sets — and it retires the 「cross-package TypeScript constants」 special case; ② pull measured in the reference app: _picklists.ts ≈ 3,001 tokens, 17 consumers, three packages; ③ a named picklist makes an AI author's wrong reference a loud refusal where today's copied option lists drift silently; ④ a new declared kind is a permanent obligation, so the direction is set now and the schedule stays behind the open product P0/P1). The maintainer agreed. The 2026-09-17 park (batch #147 item 2, 5715762696) was a sequencing decision; its recorded design is the design of record and is carried into the sub-issues unchanged.

Ruled: A. The feature enters the road map and the queue at its road position — step ②「本地跑起来、看到」, records — as one cross-layer feature point: this card is the parent, three sub-issues carry the layers in Blocked-by: order, spec first:

1. picklist metadata kind — spec: picklist collection, Field.select({ picklist }), server-resolved options, translation face (phase 1 of objectstack#18164) #19518 — spec (domain:spec, pm:queue, p2): the picklist kind, Field.select({ picklist }) mutually exclusive with options, the server-resolved served shape, the translation face, the additive package-level picklistExtensions shape; with it the feature-map line in docs/NORTH-STAR.md 「路上的功能点」 and the two records-forms checklist items (its own small Tier H docs PR).
2. picklist metadata kind — runtime: resolve picklist → options when serving field metadata, validate writes against the resolved set, apply package-level extensions (phase 1 of objectstack#18164) #19519 — runtime (domain:engine, pm:blocked → released when picklist metadata kind — spec: picklist collection, Field.select({ picklist }), server-resolved options, translation face (phase 1 of objectstack#18164) #19518 lands): load order, additive merge, resolve-at-serve, write validation against the resolved set; hotcrm's migration of its shared lists is filed as a hotcrm card by the epic PM when this lands.
3. objectui#10202 — Studio (domain:ui, pm:blocked → released when picklist metadata kind — runtime: resolve picklist → options when serving field metadata, validate writes against the resolved set, apply package-level extensions (phase 1 of objectstack#18164) #19519 is installable by pin): picklist page and 「use picklist」 in the object designer (phase 2; phase 1 needs no frontend change because options are served resolved).

Phase 2's per-organization overlay (ADR-0005, additive only) is deferred to its own sub-issue when a customer requirement measures it; the three sub-issues say so. ⛔ None of the three is dispatched before the open product P0/P1 checklist items — the road order decides, and the domain:spec seat takes #19518 when it reaches it. When work starts, an epic PM session takes this parent (pm:epic + session ID on the body per 〈Epic 子树车道〉); until then the parent carries pm:queue as a coordination node and is never dispatched itself.

四棱行:① A(成熟平台皆有,收掉跨包常量特例) · ② 自家实测、外部未测 · ③ A 响亮(命名引用写错即拒) · ④ 定方向不抢期(排在 P0/P1 之后)
Prior rulings read: picklist, global value set, valueSet → 2 hits (this card's batch #147 park; #18163 sibling); ADR-0005 (overlay), ADR-0136 D2.4 (verification); thread: none

Execution, same stroke: needs-user-decision → pm:queue on this card; body's leading Restart-when: line replaced by the Path: line; the three sub-issues filed, labelled and linked as GitHub sub-issues of this card; area:records is added to the parent and the sub-issues once the area:* labels exist (created by ensure-pm-labels.sh after PR #19488 lands).

---

Generated by Claude Code