[Decision] Objects with many actions: a platform-default 「设置」 tab composed from record_section actions (spec group key + objectui default record page) and a record_header count lint #24277

Activity

1. objectstack-fleet

   added

   priority:p2Medium: important, M3Medium: important, M3

   needs-user-decisionBlocked on a maintainer decision — do not dispatch; decision cards only, never on a PRBlocked on a maintainer decision — do not dispatch; decision cards only, never on a PR

   domain:specDomain lane — seat card indexed by label:pm:seatDomain lane — seat card indexed by label:pm:seat

   domain:uiDomain lane — seat card indexed by label:pm:seatDomain lane — seat card indexed by label:pm:seat

   on Oct 18, 2026
2. objectstack-fleet commented on Oct 18, 2026

   

   objectstack-fleetBot

   on Oct 18, 2026

   ContributorAuthor

   More actions

   席位意见(增量 · 效果图与 cloud#3001 的关系)· director seat (summon #43 continuation 5, session_01QJC7i981TSs9L1CGJK59Ax) · on batch #365 item 1, 2026-10-18T10:05Z

   The maintainer's words in this session's chat, verbatim: 「24277 如果按照这个开发，开发出的效果图会是什么样？cloud 3001 还需要吗？」 and 「3001 为什么关闭，还需要开发吗」. Two answers, no letter yet.

   1. What option A renders, drawn. Two artboards added to the cloud#3001 canvas, https://claude.ai/artifact/WEQfNGTRQw19uqBVH3eqKb (second row): 「环境 · 默认记录页」 and 「用户 (sys_user) · 默认记录页」. Both are the console's default record page with zero page code: the header is the record chrome (⟳, the object's record_header actions up to maxVisible, ⋯), the tab strip is the synthesizer's 详情 / 相关 / 活动 plus the generated 「设置」; inside it one section per group in declaration order, one row per record_section action (the action's label, its description as the muted line, its button), and a red-bordered 「危险操作」 section at the bottom that collects every variant: 'danger' action whatever its group. The rendered PNGs went to the maintainer as files (the relay cannot upload images).

   • Visible difference from cloud#3001's authored page: the default has no per-row 「当前：…」 value line and no per-section caption — those are page knowledge (plan, hostname, SSO state), not action metadata. Closing that gap would need two more spec keys (a group caption and a record-bound row summary); the seat does not recommend them now. The default is the floor every object gets; an authored page remains the ceiling.

   2. Why cloud#3001 is closed, and whether it still needs development. cloud#3001 was a decision card, not an execution card: its own 「执行 · 取 A」 line says the card closes once the letter is recorded and points at cloud#2916, the execution card. The ruling (6247273688) bound the 「设置」 tab and the confirmed design onto cloud#2916 (pointer 6247289049), which is pm:blocked on the objectui pin carrying objectstack-ai/objectui#12933. So yes, the development is still owed — in cloud#2916's round, by the repo:cloud#2 seat, as ruled.

   • If [Decision] Objects with many actions: a platform-default 「设置」 tab composed from record_section actions (spec group key + objectui default record page) and a record_header count lint #24277 is ruled A: cloud#2916 stops authoring the five record:quick_actions blocks; cloud only moves the actions' locations to record_section, sets group, and the tab appears by itself after the objectui pin that carries A (the same kind of pin wait cloud#2916 already has). The 概览 half of cloud#2916 Target 2 (header with 打开 / 安装应用 / 升级 on Free, the summary row, the installed-apps card, the URL card, the read-only 访问与登录) stays authored — the default page does not draw it. The confirmed design stays the 样式 for both: what cloud authors, and what the platform's default tab should look like. The director records this on cloud#2916 with the letter.
   • If [Decision] Objects with many actions: a platform-default 「设置」 tab composed from record_section actions (spec group key + objectui default record page) and a record_header count lint #24277 is ruled B or C: cloud#2916 builds the 「设置」 tab exactly as cloud#3001 ruled A; nothing changes.
   • Timing under A: two pins (spec, then objectui) before cloud can use the default. If the maintainer wants the environment page sooner than that, the fallback is cloud#3001's A as ruled, and cloud swaps to the default tab when it lands — double work, which the 口径 「平台相关的功能，应该尽量先改平台」 argues against; the seat recommends waiting.

   os-decision-facets

   • ① 项目长远合理性:不变 —— A 是平台给所有对象的地板,手写页是天花板;两者用同一份样式。
   • ② 实际业务拉动:不变 —— 环境页的开发仍在 cloud#2916 的轮次里,未丢。
   • ③ 防 AI 犯错:效果图把「默认页没有当前值行」这个差别画明,避免 dev 把页面知识硬塞进动作元数据。
   • ④ 创业阶段不扩散:不为补当前值行再加 spec 键;A 下 cloud 的「设置」页签工作量从 S–M 降到 S(只挪 locations 加 group)。

   自检:只看①选 A;②③④ 是否翻转:否。
3. objectstack-fleet commented on Oct 18, 2026

   

   objectstack-fleetBot

   on Oct 18, 2026

   ContributorAuthor

   More actions

   席位意见(增量 2 · 页签何时出现;一处更正)· director seat (summon #43 continuation 5, session_01QJC7i981TSs9L1CGJK59Ax) · on batch #365 item 1, 2026-10-18T10:07Z

   The maintainer's words in this session's chat, verbatim: 「对象在场景下会生成这样的设置页签呢」 — read as: under what conditions does an object get the generated 「设置」 tab. The rules option A proposes, stated so a dev can pin them in tests:

   When the tab is generated (default record page only).

   1. Trigger: the object declares at least one action whose locations contains record_section. Nothing else: no object-level switch, no page metadata. An object with no record_section action gets no tab and sees no change — today that is every hotcrm object and every cloud object except sys_environment after its actions move.
   2. Per viewer, per record: the tab lists only the actions whose own visible CEL and permission gate pass for this viewer on this record (the same path the header uses). When nothing passes, the tab is not drawn for that viewer. sys_user's actions are record.id == ctx.user.id, so its tab would show on your own record only.
   3. Sections: one per distinct group, in first-declaration order; actions without group sit under 「常规」; every variant: 'danger' action is drawn in the red-bordered 「危险操作」 section at the bottom whatever its group.
   4. Row: the action's label, its description (when declared) as the muted line, its button; params dialog and confirm as everywhere else.

   Authored pages — a correction to delta 1 (6248562326). Delta 1 said the environment page's tab 「appears by itself after the objectui pin」. That overstated it: the environment page is an authored (kind: 'slotted') page, and option A leaves authored pages untouched — the synthesizer never injects a tab into a page an author wrote. What an authored page gets is the same rendering as one block: the seat proposes record:quick_actions with a new layout: 'sections' mode (location: 'record_section', no actionNames), which draws every record_section action of the object grouped by group with the danger zone, exactly what the default tab draws. actionNames omitted today renders an empty bar (measured, component.zod.ts:2347), so the mode must be explicit, never a silent fallback. Under A, cloud#2916's environment page therefore authors a 「设置」 tab containing that one block (instead of five hand-named blocks), and sys_user's page keeps its own 「安全」 tab as is or swaps to the one block — the author's choice.

   What this adds to option A's contract list: ActionDefinition.group (new key) · record:quick_actions.layout: 'sections' (new value on an existing block) · the synthesizer rule (1)–(4) · the record_header count lint. Workload unchanged: spec S, objectui M.

   os-decision-facets

   • ① 项目长远合理性:不变 —— 触发条件只有一条(对象声明了 record_section 动作),无新开关;手写页与默认页共用同一块渲染。
   • ② 实际业务拉动:不变。
   • ③ 防 AI 犯错:layout: 'sections' 必须显式写,不把今天「actionNames 缺省即空」的实测行为改成静默回退;页签对每个查看者按 visible 与权限过滤,与页头同一条路。
   • ④ 创业阶段不扩散:只多一个枚举值,不加新块;没有 record_section 动作的对象零变化。

   自检:只看①选 A;②③④ 是否翻转:否。
4. objectstack-fleet commented on Oct 18, 2026

   

   objectstack-fleetBot

   on Oct 18, 2026

   ContributorAuthor

   More actions

   席位意见(增量 3 · 元数据怎么改;两个更省的设计 D、E;推荐改为 E)· director seat (summon #43 continuation 5, session_01QJC7i981TSs9L1CGJK59Ax) · on batch #365 item 1, 2026-10-18T10:16Z

   The maintainer's words in this session's chat, verbatim: 「具体解释 对象至少有一个动作的 locations 含 record_section。元数据有些什么调整。这个开发感觉有点太牵强了，还有更好的设计方案吗」 and then 「如果保持现状，而是优化更多按钮的下拉菜单呢」. Three answers.

   1. What option A changes in metadata, concretely (packages/service-tenant/src/objects/sys-environment.object.ts, 23 of the 24 header actions, one edit each; the three that stay in the header — 打开, 安装应用, 升级 — untouched):

   // today (one of the 23)
   { name: 'rename_environment', label: 'Rename', variant: 'secondary', locations: ['record_header'], … }
   // option A
   { name: 'rename_environment', label: 'Rename', variant: 'secondary', locations: ['record_section'],
     group: { en: 'Name & domain', 'zh-CN': '名称与域名', … }, … }

   「At least one action with record_section」 means: the moment any action on the object says 「I live in a body section」, the default page has something to put in a 「设置」 tab and draws one; the page itself declares nothing. The seat agrees with the maintainer's reading: that is an inferred switch (a tab triggered by a location value plus a danger zone inferred from variant), and the mechanism needs four pieces (group, the synthesizer rule, a layout: 'sections' block mode, a lint) for one effect.

   2. Option D — an explicit object-level declaration, the clean version of the generic tab. One new object key beside actions and listViews, read by the default page and by one block:

   settings: [   // ← present ⇒ the record page has a 「设置」 tab; absent ⇒ nothing changes
     { name: 'apps',      label: L('Applications', '应用'),        actions: ['install_application', 'check_app_updates', 'export_package'] },
     { name: 'billing',   label: L('Plan & billing', '套餐与计费'), actions: ['upgrade', 'buy_credits', 'change_plan'] },
     { name: 'naming',    label: L('Name & domain', '名称与域名'),  actions: ['rename_environment', 'change_hostname', 'add_domain'] },
     { name: 'access',    label: L('Access & sign-in', '访问与登录'), actions: ['disable_platform_sso', 'enable_platform_sso', 'set_platform_sso_enforced', 'set_platform_sso_optional', 'enable_mcp', 'upgrade_for_mcp', 'disable_mcp', 'set_audience_posture'] },
     { name: 'lifecycle', label: L('Lifecycle', '生命周期'),        actions: ['suspend_environment', 'resume_environment', 'restore_environment'] },
     { name: 'danger',    label: L('Danger zone', '危险操作'), danger: true, actions: ['archive_environment', 'delete_environment'] },
   ]

   plus the same locations edit as A (record_header → record_section) on the moved actions, which every design needs: an action that keeps record_header stays in the header fold. Trigger: the key is present. Danger zone: declared (danger: true), not inferred. Captions possible (description on a section). Validator: every named action exists on the object and carries record_section, no action in two sections, no empty section. Authored pages place one block, record:settings, which draws the declaration; the default page puts that block in a 「设置」 tab. Contract: one object key, one block. Studio can edit it as a list, like listViews. The mock on the canvas stands for D as drawn (the section labels become the author's).

   3. Option E — keep the status quo, improve the ⋯ menu. The maintainer's question. Actions gain group (the same key as A); nothing else moves: locations stay, the header fold stays (maxVisible 3, order picks the inline three). objectui's ⋯ menu renderer (containers.tsx 2066, today three bands) draws a small heading per group with separators, keeps the console's injected 分享 / 收藏 in their own band, and puts every variant: 'danger' action last in red. No tab, no block, no synthesizer rule. Drawn on the canvas (third row): https://claude.ai/artifact/WEQfNGTRQw19uqBVH3eqKb — a running free-plan environment shows about 16 items after visible. Honest limit: a grouped menu reads well up to roughly a dozen items; above that a page reads better. So E alone does not make the environment page good — cloud#3001's authored page (ruled A) remains the answer there, because that page also needs current values (plan, hostname, SSO state) that no menu carries. E is the floor every object gets; it reaches hotcrm's objects (≤3 header actions today) as soon as they add group, with no page work.

   Seat's recommendation, revised: E now; cloud#3001 as ruled; D parked; A withdrawn. E is the smallest platform change that helps every object (one spec key, one renderer change, one objectui pin), consistent with 「平台相关的功能，应该尽量先改平台」. When a second object outgrows a menu, the generic tab is D, not A: an explicit declaration beats an inferred switch. The record_header count lint rides whichever letter.

   Workload: E = spec S + objectui S · D = spec S + objectui M · A = spec S + objectui M.

   Execution: E → the director files an objectstack spec card p2 pm:queue (ActionDefinition.group, docs) and an objectui card p2 pm:blocked on the spec pin (grouped ⋯ menu); cloud#2916 unchanged. D → spec card (settings key + record:settings block) and objectui card; cloud#2916's 「设置」 tab becomes the one block after the pins. A → as delta 1 and 2.

   os-decision-facets

   • ① 项目长远合理性:E —— ⋯ 菜单是平台已有的通用面,给它分组是每个对象都受益的地板;要通用页签时选 D(显式声明)而非 A(靠位置值与 variant 推断)。
   • ② 实际业务拉动:E 一次 objectui pin 即惠及所有对象;D、A 等两次 pin 且今天只有一个消费方;环境页仍由 cloud#3001 的手写页解决,它需要当前值。
   • ③ 防 AI 犯错:E 与 D 都不做推断;D 的清单逐项校验(动作存在、位置一致、不重复、不空);A 的页签由一个位置值触发、危险区由 variant 推断。
   • ④ 创业阶段不扩散:E 一键一改;D 一键一块;A 一键一模式一规则一 lint。

   自检:只看①选 E;②③④ 是否翻转:否。
5. objectstack-fleet commented on Oct 18, 2026

   

   objectstack-fleetBot

   on Oct 18, 2026

   ContributorAuthor

   More actions

   席位意见(增量 4 · 下拉菜单要不要分组;不分组时的排序)· director seat (summon #43 continuation 5, session_01QJC7i981TSs9L1CGJK59Ax) · on batch #365 item 1, 2026-10-18T10:36Z

   The maintainer's words in this session's chat after the letter 「24277 E；3002 A」, verbatim: 「24277 下拉菜单需要加分组吗？」 and 「如果不加分组会有排序的概念吗」. The letter E is held until the maintainer picks one of the two readings below; no E write has been made.

   What the ⋯ menu already does, read at objectui a8560b228527 (packages/components/src/renderers/layout/containers.tsx):

   1. Ordering exists. Before the inline/overflow split the whole header list is sorted once: order ascending (unset = 0; lower = more prominent), variant: 'primary' as a tie-break, then registration order, stable (objectui#2339 / feat(plugin-auth): reject breached passwords via HIBP (ADR-0069 D1, P1) #2361; spec action.zod.ts:1314–:1327). Every band of the menu keeps that order. So without group, an object already controls the menu's sequence by order on its actions, and by declaration order when it sets none.
   2. Bands exist. The overflow reads in three bands (objectui#12529): the object's own actions, then the console's chrome (Edit / favorites / Share), then every destructive entry last behind a separator, painted red.
   3. One defect, from source, not yet measured in a browser: the destructive test is a?.variant === 'destructive' || a?.name === 'sys_delete'. The spec's action variant enum is primary | secondary | danger | ghost | link — danger, not destructive — and the environment's archive and delete declare variant: 'danger' (sys-environment.object.ts:1162, :1221). Nothing on the header path maps danger to destructive (only DeclaredActionsBar.tsx:409 does, for its own buttons). So an app's own danger actions most likely sit in band 1, unmarked, and only the console's 删除 reaches the red band. That is an objectui fix with no spec change.

   The two readings of E:

   • E1 · no grouping. No new spec key. objectui: the red band honours the spec's danger spelling (item 3), pinned by a test; otherwise the menu stays as it is. Objects that want a better menu set order and declare variant: 'danger' — both already in the contract. Work: objectui S; nothing waits on a spec pin. A long menu stays a long list, which for the environment is moot (cloud#3001 A gives it an authored page).
   • E2 · grouping. E1 plus ActionDefinition.group and the sectioned menu (delta 3, the third-row artboard). Work: spec S + objectui S; two cards, one pin wait for the renderer. Today no object both has a long menu and lacks an authored page, so the headings have no consumer yet.

   Seat's reading: E1 now; group when a consumer appears. The answer to 「需要加分组吗」 is therefore 「现在不需要」, and to 「不加分组会有排序的概念吗」 is 「有,已经在平台里」.

   os-decision-facets

   • ① 项目长远合理性:E1 —— 排序与危险区都已在契约里(order、variant: 'danger'),缺的只是渲染器认错拼写;group 等有消费方再加。
   • ② 实际业务拉动:环境页走手写页(cloud#3001 A),长菜单没有第二个对象;E1 修的缺陷影响所有声明了 danger 动作的对象。
   • ③ 防 AI 犯错:E1 不加键;修的正是「spec 说 danger、渲染器查 destructive」这类一词两拼的错。
   • ④ 创业阶段不扩散:E1 只有 objectui 一张小卡;E2 两仓两卡。

   自检:只看①选 E1;②③④ 是否翻转:否。
6. objectstack-fleet commented on Oct 18, 2026

   

   objectstack-fleetBot

   on Oct 18, 2026

   ContributorAuthor

   More actions

   Ruling: batch #365 item 1 · letter E1 · maintainer 「24277 E」 then 「E1」 2026-10-18T12:12Z

   Director seat, summon #43 continuation 5, session_01QJC7i981TSs9L1CGJK59Ax, on the director's own card (A recommended at filing; revised to E in delta 3, 6248654513; E split into E1 / E2 in delta 4, 6248833927, after the maintainer's 「24277 下拉菜单需要加分组吗？」 and 「如果不加分组会有排序的概念吗」), the deltas 6248562326 / 6248585323 / 6248654513 / 6248833927 and the canvas https://claude.ai/artifact/WEQfNGTRQw19uqBVH3eqKb (opening marker #12708, comment 6247058702). The maintainer's words in this session's chat: 「24277 E；3002 A」, then 「E1」.

   What the ruling binds (letter E1 — keep the status quo; no new spec key; the ⋯ menu's existing order and bands do the work):

   1. No change to the spec: no group, no settings-tab key, no block mode, no synthesizer rule, no lint. A many-action object is laid out with what the contract already has — order (lower = more prominent; primary tie-break; declaration order otherwise), record_more for actions that never need an inline slot, variant: 'danger' for the red band.
   2. objectui: the ⋯ menu's destructive band honours the spec's danger spelling (delta 4 item 3, read from source, measured first) — console: the record ⋯ overflow menu's destructive band honours the spec's variant: 'danger' (objectstack#24277 ruling E1) objectui#12961, p2 pm:queue. Nothing else in the menu changes.
   3. cloud#2916 and cloud#3001 are unaffected: the environment page keeps its authored 「设置」 tab (cloud#3001 ruling A, 6247273688).
   4. E2 (group and the sectioned menu, the third-row artboard), D (an explicit object-level settings declaration) and A (the inferred default tab) stay on this record for the day an object both has a long menu and lacks an authored page; D over A then.

   Not taken: E2 (no consumer today), A (an inferred switch), D (parked).

   Workload of the letter: objectui S.

   Execution: objectstack-ai/objectui#12961 filed in this act; this card leaves needs-user-decision and closes completed pointing at it.
7. objectstack-fleet

   removed

   needs-user-decisionBlocked on a maintainer decision — do not dispatch; decision cards only, never on a PRBlocked on a maintainer decision — do not dispatch; decision cards only, never on a PR

   on Oct 18, 2026
8. objectstack-fleet commented on Oct 18, 2026

   

   objectstack-fleetBot

   on Oct 18, 2026

   ContributorAuthor

   More actions

   Closed completed · ruled E1 at 6249771678 (batch #365 item 1, the maintainer's 「24277 E」 then 「E1」) · director seat (summon #43 continuation 5, session_01QJC7i981TSs9L1CGJK59Ax) · 2026-10-18T12:14Z

   Execution: objectstack-ai/objectui#12961 (the ⋯ menu's red band honours variant: 'danger'; p2 pm:queue). No spec change. E2, D and A stay on this record for a second many-action object. cloud#2916 and cloud#3001 are unaffected.
9. objectstack-fleet

   closed this as completedon Oct 18, 2026