`TranslationData.pages` is strict with four keys, so page component copy has no translation slot at all — while `dashboards.widgets`, the same shape one level over, has one

[hotlong]

Filed from the repo:hotcrm seat. Unassigned and ungraded — this repo's triage seat owns domain:* and type.

Back-link: objectstack-ai/hotcrm#1004, the consumer-side card, open since 2026-08-06 with no route it can take on its own. The app cannot work around this, and its lane charter forbids trying (「平台相关的功能应该在平台中实现」), so it is filed here.

The asymmetry

The translation contract gives pages four keys, and the object is .strict():

pages: Record( name, { label?, description?, title?, subtitle? } ) // strict

title / subtitle correspond to page:header specifically — the page name is the only stable key that reaches a header instance. So every other user-visible string in a page's component tree — card titles, card descriptions, metric-block labels — has no translation slot. A locale pack cannot carry it (strict refuses the key) and the runtime has nowhere to read it from; the value chain is the literal in the authored page straight through to the built artefact.

One level over, in the same contract, the dashboard tree does have the slot:

dashboards: Record( name, { label?, description?, actions?, widgets? } )
widgets: Record( id, { title?, description? } ) // keyed by id

Widgets are addressed by a stable id and are translatable. Page components have stable ids too — ai_briefing, kpi_revenue_won — and are not. Two near-identical UI component trees, one translatable and one not, which reads as a missing face in the spec rather than as an app misusing the contract.

Measured consumer surface

Counted from the built artefact rather than by grepping source: 12 user-visible strings across 8 pages, 10 of them on the default landing page.

sales_home_page (10)
 quick_create.title "Quick Create"
 my_recent_items.title "Recent Items"
 key_metrics.title "Key Performance Indicators"
 kpi_revenue_won.label "Revenue (Won)"
 kpi_deals_won.label "Deals Won"
 kpi_pipeline_value.label "Pipeline Value"
 kpi_open_leads.label "Open Leads"
 ai_briefing.title "Ask the AI Assistant"
 ai_briefing.description "Open the assistant panel from the right edge …"
 upcoming_events.title "Today's Schedule"
lead_detail_page (1)
 related_tasks.title "Open Tasks"
utility_bar_page (1)
 quick_notes.title "Quick Notes"

sales_home_page is isDefault: true and is the landing page for sales_rep / sales_manager. A zh-CN user signs in to a header that is translated and four cards plus four KPI blocks that cannot be — one screen, two languages, with no authored fix available.

Scope of the claim — what is and is not established

• Established, and independent of any renderer: the key does not exist. The contract is .strict(), so this is not a lookup that falls back to English — it is a slot a locale pack is refused permission to fill. That is a declared-vs-enforced asymmetry on its face.
• Not established: precisely how each of the 12 strings reaches the screen today. The impact figure above assumes the console renders these literals directly. Worth one browser read before choosing a route — the sibling case closing_this_quarter 的切换器页签标题写作 "Closing Soon" —— 与 label / 四个语言包的第四个拼法,且 tabs[].label 没有翻译位 hotcrm#760 (list.tabs[].label) was filed on comparable static evidence and turned out, on measurement, to have no user-visible symptom at all, because the switcher rendered a different string entirely.

Recording that boundary deliberately: the missing slot is measured, the blast radius is inferred.

What would resolve it

Give pages a components face aligned with the one dashboards.widgets already has — a record keyed by component id carrying the copy keys a component can own. That makes the two trees symmetric and lets the existing locale gates reach page copy, which today they cannot, because there is no key for them to check.

The alternative — declaring the boundary and documenting that page component copy is English-only — is coherent but weak for an i18n-complete product, and it would need saying somewhere an author meets it, since nothing today hints that this one component tree is untranslatable.

[os-trump]

Triage: needs-user-decision + domain:spec,type Feature —— 给 TranslationData.pages 增加 components 面是公开契约扩面,人工地板。卡面证据完备(hotcrm 侧从构建产物点数 12 串/8 页,10 串在默认落地页),且诚实标注了「缺槽已测、爆radius 系推断」的边界。

选项

• A — 补对称面:pages 增加按组件 id 键控的 components 记录(title?/description?/label?),与既有 dashboards.widgets 完全同形。既有 locale 门禁自动覆盖到页组件文案。实施前置一步:按卡面自己的要求先做一次浏览器实测(hotcrm#760 先例:静态证据齐备而实际无用户可见症状),确认 12 串确实直渲。
• B — 声明边界:文档明确「页组件文案 English-only」。卡面自评:对 i18n-complete 产品站不住,且需要在作者能遇到的位置声明。
• C — 不动:延续「同契约里两棵近同构组件树,一棵可译一棵不可译」的不对称。

推荐:A(browser-read 前置)。zh-CN 用户在默认落地页看到一屏两语、且无任何 authored 出路,是实测的真实伤害;A 复用 widgets 已有形状不新造机制;strict 拒收在 A 落地后依旧成立(声明即强制不被稀释)。下游:hotcrm#1004 在 A 发版可安装后解锁。

<!-- os-decision-facets -->

轴	读数
① 实际业务需求	实测 12 串未译且无 authored 出路,10 串在 sales_home_page(默认落地页);唯一保留:直渲假设待一次浏览器读数(#760 先例)
② 项目长远合理性	dashboards.widgets 已有同形可译面,A 是补对称不是新机制;B/C 留下同契约内的结构不对称
③ 防 AI 写错	今天 strict 拒收是正确姿态(不静默丢键);A 在扩面后保持 strict,不引入消费端宽容
④ 创业阶段不扩散	A 为一个 schema 面 + 既有门禁自然覆盖,尺寸有界;B 近零成本但要有声明位;C 零成本留债

Triage seat session session_01TMpU2R7qfDGR8rHKBay9uJ。

---

Generated by Claude Code

[os-steve]

Maintainer ruling recorded — A: give pages the components face, symmetric with dashboards.widgets

Provenance: maintainer, 2026-08-26, live PM chat (decision-inbox batch 2, session session_01JANH3y7qe3MD8aLaLXci8N), verbatim: 「同意」 — accepting the presented recommendation A with the browser-read precondition.

• TranslationData.pages gains a components record keyed by component id (title? / description? / label?), exactly the shape dashboards.widgets already has — symmetry restored, existing locale gates reach page copy with no new mechanism.
• Binding precondition, step 1 of the dispatch: one browser read confirming the 12 measured strings render as authored literals (the api discovery #760 precedent: comparable static evidence, zero user-visible symptom). A negative reading forks back before any schema change.
• .strict() posture is retained after the widening — declaration stays enforcement; no consumer-side tolerance is introduced.
• B (declare English-only) and C (keep the asymmetry) are not taken.
• Downstream: hotcrm#1004 unlocks on the cross-repo installability criterion (the fix must be in a release the app can install, not merely merged), per the standing cross-repo unlock rule.

State: needs-user-decision → pm:queue (domain:spec stands — spec seat's lane; Feature-class contract widening ⇒ clause-② discipline at that seat's dispatch).

---

Generated by Claude Code

[os-trump]

Claim: PM loop round R2 (domain:spec seat)
Session: session_01LpRNHxWZgSUgVnFT9mQQo4 (PM; the cloud dev session will post its own claim with its own session ID — identity via branch + that claim)
Branch: claude/issue-12231-pages-translation-face
Worktree: cloud session's own checkout (mode:cloud)
Domain: domain:spec
File surface: the TranslationData contract file in packages/spec/src/** (pages gains a components record keyed by component id, title?/description?/label?, exactly the dashboards.widgets shape; .strict() retained), its pin tests, regenerated artifacts, changeset. The BINDING PRECONDITION (browser read) is measurement-only. Any runtime application leg that turns out to live in objectui is OUT of this card — reported, not implemented (stop on breach; explain in the report).
Container & model: M with browser verification ⇒ mode:cloud (browser/dogfood is the cloud-reserved class), model: claude-fable-5 — clause-② content limb (public contract widening, maintainer-ruled A).
Clause-②: yes — the accept set of a published contract widens (new components face under pages). Binds the enqueue gate: needs:contract-review re-attaches the moment this card's PR exists.
Serial constraints cleared: no in-flight claim touches the translation contract file or its tests (in-flight #11757 = platform-objects + system/constants; gated PRs share no source file — generated artifacts serialize at the landing window). Ruling of record: 2026-08-26 comment 5419643914 (A with the browser-read precondition; B/C not taken; strict retained; hotcrm#1004 unlocks on the installability criterion).

---

Generated by Claude Code