Filed by the domain:ui execution seat (session session_012wwHa4aaFybxXrfmfHioDM) out of #6896's delivery. ⛔ Not adjudicating: declaring these keys is a widening of a published surface, which is the human floor. Recorded with the measurement so the ruling is one read rather than a re-derivation.
The gap, stated plainly
#6896 retires ChartDataSeries.data and its tombstone tells authors what to use instead: the chart-level data plus xAxisKey. That remedy is accurate — it is what normalizeChartSchema actually reads.
⚠️Neither key is declared on ChartSchema. Both survive only through BaseSchema's [key: string]: any index signature.
⇒ So the published migration note now names two undeclared keys as the supported replacement. An author following the tombstone writes a document the type system cannot check, into a shape nothing enforces.
Why this is the same defect one level out
#6896's whole subject is declared-but-unread. This is its mirror: read-but-undeclared. The de-facto contract — chart-level data + per-series dataKey, which the ruling itself called "the de-facto contract" — rides an index signature, so:
ChartSchema literals are not excess-property-checked, so a misspelled xAxiskey or datas type-checks green and renders an empty chart;- the zod mirror does not model it either, so
safeValidateSchema cannot refuse it; - ⇒ the one shape the platform actually supports is the one shape an AI author gets no feedback on.
What was measured, and by whom
Measured by the #6896 dev while implementing the ruling (report on that card): normalizeSeries reads nine keys and data is not among them; rows come from the chart-level data; the category axis comes from xAxisKey / xAxis. Independently, #7112 records five documentation and example sites that author the documented model and therefore render an empty chart today.
⛔ Not measured here: the exact shape chart-level data should be declared as, and whether xAxis (the sibling spelling normalizeChartSchema also accepts) is intended, an alias, or drift. That is part of what a ruling has to settle.
The decision
Should ChartSchema declare the data model it actually reads?
| option | note |
|---|
| A | Leave undeclared | The remedy text stays accurate about behaviour; the gap persists and the retirement's migration target remains uncheckable |
| B | Declare chart-level data and xAxisKey (and settle xAxis) on ChartSchema and its zod mirror | Makes the model the retirement migrates authors to enforceable rather than merely documented. ⚠️ A published-surface widening ⇒ human floor + needs:contract-review |
| C | Declare them inside #6896's PR | ⛔ Explicitly rejected by that card's dev and by this seat: it would put a widening and a narrowing into one review, and the ruling authorised the narrowing only |
四维分析
① 实际业务需求 —— 拉动是实测的,不是推测:这两个键就是渲染器今天读的东西,#7112 记录的五处 doc/example 站点全都在教另一个(已退役的)模型,今天渲染出空图。⇒ 需求不在「要不要支持」——已经支持了;在于「支持的东西要不要可检查」。
② 项目长远合理性 —— B 是 contract-first 的读法。#6896 关掉了「声明了却没人读」的一半,留下「读了却没声明」的另一半;两半是同一个 ADR-0049 形状。⚠️ 只关一半,等于把作者从一个不可检查的模型迁移到另一个不可检查的模型。
③ 防 AI 写错 —— 这一轴最硬,而且决定问题。ChartSchema 字面量不做多余属性检查(靠 BaseSchema 的索引签名),所以 xAxiskey 拼错、data 给错类型,tsc 绿、zod 绿、渲染出空图。这正是「AI 声明一个运行时不兑现的能力」的反向:AI 写对了意图、拼错了键,而平台一声不吭。B 让它在作者期响亮。
④ 创业阶段不扩散 —— ⚠️ 这一轴指向克制,必须诚实呈现:B 是加宽已发布面,而本轮的裁决刚刚以「zero users 不建新机制」为由退役了另一半。⇒ 但 B 不新增能力,它把已经在跑的能力写成声明;这与「扩散需求」不同,更接近 declared = enforced 的恢复。判断权在维护者。
推荐:B,弱持。①②③ 同向,④ 是真实的反对但性质是「写下既有事实」而非「新增能力」。⛔ 四棱非同向 ⇒ 不代裁。
⚠️不占工期:#6896 的 PR 不等这张卡,它已按裁决完成并停在契约复审前(另因 fable 额度受阻)。
Related
#6896(退役,已交付)· #7112(五处 doc/example 站点教已退役模型)· ADR-0049 enforce-or-remove
Filed by the
domain:uiexecution seat (sessionsession_012wwHa4aaFybxXrfmfHioDM) out of #6896's delivery. ⛔ Not adjudicating: declaring these keys is a widening of a published surface, which is the human floor. Recorded with the measurement so the ruling is one read rather than a re-derivation.The gap, stated plainly
#6896 retires
ChartDataSeries.dataand its tombstone tells authors what to use instead: the chart-leveldataplusxAxisKey. That remedy is accurate — it is whatnormalizeChartSchemaactually reads.ChartSchema. Both survive only throughBaseSchema's[key: string]: anyindex signature.⇒ So the published migration note now names two undeclared keys as the supported replacement. An author following the tombstone writes a document the type system cannot check, into a shape nothing enforces.
Why this is the same defect one level out
#6896's whole subject is declared-but-unread. This is its mirror: read-but-undeclared. The de-facto contract — chart-level
data+ per-seriesdataKey, which the ruling itself called "the de-facto contract" — rides an index signature, so:ChartSchemaliterals are not excess-property-checked, so a misspelledxAxiskeyordatastype-checks green and renders an empty chart;safeValidateSchemacannot refuse it;What was measured, and by whom
Measured by the #6896 dev while implementing the ruling (report on that card):
normalizeSeriesreads nine keys anddatais not among them; rows come from the chart-leveldata; the category axis comes fromxAxisKey/xAxis. Independently, #7112 records five documentation and example sites that author the documented model and therefore render an empty chart today.⛔ Not measured here: the exact shape chart-level
datashould be declared as, and whetherxAxis(the sibling spellingnormalizeChartSchemaalso accepts) is intended, an alias, or drift. That is part of what a ruling has to settle.The decision
Should
ChartSchemadeclare the data model it actually reads?dataandxAxisKey(and settlexAxis) onChartSchemaand its zod mirrorneeds:contract-review四维分析
① 实际业务需求 —— 拉动是实测的,不是推测:这两个键就是渲染器今天读的东西,#7112 记录的五处 doc/example 站点全都在教另一个(已退役的)模型,今天渲染出空图。⇒ 需求不在「要不要支持」——已经支持了;在于「支持的东西要不要可检查」。
② 项目长远合理性 —— B 是 contract-first 的读法。#6896 关掉了「声明了却没人读」的一半,留下「读了却没声明」的另一半;两半是同一个 ADR-0049 形状。⚠️ 只关一半,等于把作者从一个不可检查的模型迁移到另一个不可检查的模型。
③ 防 AI 写错 —— 这一轴最硬,而且决定问题。
ChartSchema字面量不做多余属性检查(靠BaseSchema的索引签名),所以xAxiskey拼错、data给错类型,tsc 绿、zod 绿、渲染出空图。这正是「AI 声明一个运行时不兑现的能力」的反向:AI 写对了意图、拼错了键,而平台一声不吭。B 让它在作者期响亮。④ 创业阶段不扩散 ——⚠️ 这一轴指向克制,必须诚实呈现:B 是加宽已发布面,而本轮的裁决刚刚以「zero users 不建新机制」为由退役了另一半。⇒ 但 B 不新增能力,它把已经在跑的能力写成声明;这与「扩散需求」不同,更接近 declared = enforced 的恢复。判断权在维护者。
推荐:B,弱持。①②③ 同向,④ 是真实的反对但性质是「写下既有事实」而非「新增能力」。⛔ 四棱非同向 ⇒ 不代裁。
Related
#6896(退役,已交付)· #7112(五处 doc/example 站点教已退役模型)· ADR-0049 enforce-or-remove