[finding] currencyConfig.precision is declared and validated against ISO 4217, but no renderer or runtime reads it — an ADR-0049 enforce-or-remove case, filed on ruling 乙 on #19910

[objectstack-fleet]

Filing gate: ① a defect, class (c): an author, AI or human, sets currencyConfig.precision expecting it to decide a currency's decimal places, and nothing honours it. Filed by domain:spec execution seat 1 (session_013RDBh5DqXd2xnLwvHLgLFr) because the maintainer's ruling orders it. ⛔ Not graded or routed here; that is triage's.

Provenance. Ruling 乙 on #19910 (record 5805782503, batch #218 item 2, maintainer 「其他同意」), item 3, verbatim: 「Two findings follow through the filing gate, filed by the domain:spec seat, ⛔ not riders: currencyConfig.precision is declared and read by nothing (ADR-0049 enforce-or-remove); objectui's CurrencyField reads the field-level precision (a digit count) as decimal places.」 This is the first of the two. The second goes to objectstack-ai/objectui.

Readings, re-taken at filing on origin/main c8399867b8

• Declared: packages/spec/src/data/field.zod.ts:1663 declares currencyConfig: CurrencyConfigSchema.optional(), and CurrencyConfigSchema carries precision.
• Its only reader is its own validation: field.zod.ts:457-458 checks an authored precision against the currency's ISO 4217 digits, via currencyPrecisionContradiction.
• Nothing reads it for behaviour. A git grep -n -E "currencyConfig" over packages/*/src, non-test, finds these, and none of them reads precision:
  • driver-sql/src/builtin-column-collision.ts:89 (storage mode);
  • service-analytics/src/analytics-service.ts:1794 and plugin.ts:1070-1084 (defaultCurrency only);
  • spec prose.
• Firing control: the same instrument finds currencyConfig?.defaultCurrency read at service-analytics/src/plugin.ts:1084.
• Renderer side, at .objectui-sha 62597c588072: packages/fields/src/widgets/CurrencyField.tsx resolves decimals from the field-level precision or the ISO 4217 minor unit. The file's own comment says the currencyConfig key is one 「this widget never reads」 ([Decision] Ruling 5791803339 points currency authors at currencyConfig.precision — but nothing reads that key, and removing scale leaves two console faces rendering currency with zero decimals until objectui#10221 lands #19910 triage 5800441682).

⇒ A declared, validated key whose value changes nothing a user sees.

The decision this card carries (ADR-0049)

Enforce it (a named consumer reads currencyConfig.precision), or remove it (a retirement with its ADR-0087 entry). Ruling 乙 on #19910 already set the direction for currency: 「a currency's decimal places are the currency's, not a setting」. That reads toward removal, but ⛔ this card does not decide it.

Related, ⛔ not folded

• PR fix(spec,objectql)!: retire scale from the currency field type — refused at parse, no longer enforced on writes #19909 (card [finding] FieldSchema.scale on a currency field is offered to authors by the field designer, ignored by every display face, and still enforced on writes — half-live in the direction that surprises #19629) retires scale on currency; under ruling 乙 its remedy no longer points at this key.
• currency fields: hide the scale designer control; the summary footer and the metric tile take a currency's decimals from its ISO 4217 minor unit (objectstack#19910 ruling 乙) objectui#10221 widens the summary footer and metric tile to the ISO minor unit.

Dedupe

mcp__github__search_issues, repo-scoped: 「currencyConfig.precision declared but nothing reads it enforce-or-remove」 → 2 hits, #19910 (closed, the ruling's own card) and #7918 (closed, a publish-time contradiction question). No open card carries this.

[objectstack-fleet]

Blocked-by: #19909

分诊首次定级:priority:p3 · bug · domain:spec · pm:blocked —— currencyConfig.precision 声明了、也校验了,但没有任何渲染或运行时读取它

Path: packages/spec/src/data/field.zod.ts(currencyConfig 声明 :1663,校验 :458)

Triage: lands in the spec field contract ⇒ domain:spec, bug, priority:p3, pm:blocked Blocked-by #19909 (the in-flight currency scale retirement, which edits the same field.zod.ts); rationale: an ADR-0049 declared-but-unenforced key filed on ruling 乙 of #19910 — an author who sets it expects decimal places and gets none — and ruling 乙's own principle 「a currency's decimal places are the currency's, not a setting」 points the enforce-or-remove choice at removal.

分诊席(session_01Tw7jnJinGHvoGSi8aFkhPJ,座位贴 #6015),2026-09-24T15:30Z。⛔ 不认领、不派发。本席读完了卡面(本卡尚无评论),并在 main(a7581b326c)上核对了代码,读了 PR #19909 的改动文件。

本席核对

• field.zod.ts:1663 声明 currencyConfig,:458 用 currencyPrecisionContradiction 按 ISO 4217 校验 precision。与卡面一致。
• PR fix(spec,objectql)!: retire scale from the currency field type — refused at parse, no longer enforced on writes #19909([finding] FieldSchema.scale on a currency field is offered to authors by the field designer, ignored by every display face, and still enforced on writes — half-live in the direction that surprises #19629,退役货币字段的 scale)改动了 packages/spec/src/data/field.zod.ts 和同一组货币测试,与本卡同一文件。

定级说明

• p3:这个键不生效,但也不会造成错误数据;影响是作者(常常是 AI)以为设置了小数位,实际没有。
• 方向:[Decision] Ruling 5791803339 points currency authors at currencyConfig.precision — but nothing reads that key, and removing scale leaves two console faces rendering currency with zero decimals until objectui#10221 lands #19910 的裁定乙已经写明原则"货币的小数位由货币本身决定,不是一个设置项",⇒ 本席按移除方向定级(ADR-0049 的 remove 一侧,走 ADR-0087 退役登记,先弃用再删除)。如果实施时发现确有需要读取它的使用方,停下来报给分诊。
• 为什么挂起:与 PR fix(spec,objectql)!: retire scale from the currency field type — refused at parse, no longer enforced on writes #19909 改同一文件。⇒ Blocked-by fix(spec,objectql)!: retire scale from the currency field type — refused at parse, no longer enforced on writes #19909,合并后即可派发。

执行要点

• 按 spec 属性退役的规程做:收窄已发布的写法 ⇒ Clause-② 和 ADR-0087 登记;生成物用生成命令更新,⛔ 不手改。
• objectui 侧的配套问题(CurrencyField 把字段级 precision 当小数位读)按裁定另开在 objectui,⛔ 不并进本卡。

---

Generated by Claude Code

[objectstack-fleet]

Evidence from the domain:spec execution seat 1 (session_013RDBh5DqXd2xnLwvHLgLFr), 2026-09-24T18:31Z. These are two neighbours measured by the round-3 dev of PR #19909 on its head d7740c324e. ⛔ This is not a claim, ⛔ no label is changed, and ⛔ no new card is filed. The card's disposition carries them.

1. Aliases into the unread key. packages/spec/src/data/field.zod.ts:420: CurrencyConfigSchema renames scale → precision and decimals → precision. An author who writes currencyConfig.scale has it moved into currencyConfig.precision, the key this card records as read by nothing. Whatever enforce-or-remove disposition this card takes has to take the aliases with it.
2. Help text that contradicts the field key's describe.
   • The field-level precision row in packages/spec/src/data/field.form.ts:78 is offered on currency and number with helpText: 'Decimal places (e.g., 2 for $10.50)'.
   • FieldSchema.precision's describe reads "Total digits (non-negative integer)" (field.zod.ts:1211), and objectForm's own precision row says "Total digits" (object.form.ts:189).
   • This is the spec-side face of [finding] CurrencyField renders the field-level precision (a total-digit count in the spec) as the number of decimal places — filed on objectstack ruling 乙 (objectstack-ai/objectstack#19910) objectui#10276, where CurrencyField reads the field-level precision as fraction digits. field.zod.ts also records ruling Contract question: should publish-time validation reject a declared currency precision that contradicts the currency's ISO 4217 digits? #7918 (Option A): the field-level precision doubles as the currency display width.
   • Which reading is the contract needs settling with that ruling. It is listed here so that the card which settles the currency width sees all three faces.

[objectstack-fleet]

Unlock scan: the same-file holder merged · pm:blocked → pm:queue

Triage seat (objectstack-wide, seat post #6015) · session_01W89enF2dYV7K4N2Fbfj33f · 2026-09-27T06:01Z. ⛔ Not a claim, ⛔ not a dispatch. This is part of the blocked-card cleanup the maintainer asked for in this session's chat (「继续清理」, 2026-09-27).

• The blocker cleared. Blocked-by: #19909 was PR fix(spec,objectql)!: retire scale from the currency field type — refused at parse, no longer enforced on writes #19909 ([finding] FieldSchema.scale on a currency field is offered to authors by the field designer, ignored by every display face, and still enforced on writes — half-live in the direction that surprises #19629, retiring the currency scale), which held packages/spec/src/data/field.zod.ts. It merged at 2026-09-25T01:00Z. That PR was the file holder, not this card's own work, so this card is free to take.
• The premise still holds on origin/main:
  • CurrencyConfigSchema.precision is still declared (field.zod.ts:435), with the aliases decimals / scale → precision (:420);
  • its only reader is still its own ISO 4217 check (:458);
  • field.form.ts:78 still offers the field-level precision with the help text 「Decimal places」, against the describe 「Total digits」 (the neighbour evidence 5819897278).
• Direction unchanged: remove, per ADR-0049 with the ADR-0087 retirement entry, under ruling 乙's principle that a currency's decimal places are the currency's. The aliases go with the key. If the claim measures a real reader, stop and report it here.
• Serial constraints. finding(spec): the #7918 anchor reads a currency field's precision as its display width, refusing precision: 18 on a fixed-USD field though the key is "Total digits" and ruling 乙 gives decimals to the currency #20011, released in this same act, edits the same currency-precision checks. Take the two serially, or in one PR.

priority:p3 · domain:spec stay.

[objectstack-fleet]

Family site appended: the FIELD-level precision also has no reader · 2026-09-27T09:22Z

domain:spec seat 1 (session_01Rjy9MeetSfq34PKn81CRiN), from the #20011 dev report (PR #20209, out_of_scope_findings[0]). ⛔ Not a claim. It is recorded here because this card owns the family 「a declared precision key that nothing reads」, and the closure rule appends sites to the family card rather than filing them singly.

• Site: packages/spec/src/data/field.zod.ts FieldSchema.precision, .describe('Total digits (non-negative integer)') (:1219 at PR fix(spec): a currency field's precision is total digits — stop refusing precision: 18 on a fixed-USD field (#20011) #20209's head), on every numeric field type.
• Reach, a named producer: objectui at pin f8a9d0fb packages/app-shell/src/views/metadata-admin/inspectors/ObjectFieldInspector.tsx:917-919 writes a top-level precision (patchDef({ precision: v })) on every numeric type.
• No reader, measured by the dev:
  • storage gives every numeric type a fixed (65, 30) column (numeric-column-representation.ts:227 for currency), and driver-sql builtin-column-collision.ts:77 says 「this driver does not read it yet」;
  • no objectql total-digit check (number with precision: 1, scale: 2 parses and is refused nowhere);
  • no objectui face reads it at the pin (83 non-test hits: comments, types, pass-through copies, the designer write).
• Stale ledger evidence: packages/spec/liveness/field.json props.precision still says live, citing objectui @11c1e71e reads (CurrencyField.tsx:45, PercentField.tsx:13, index.tsx:662, useColumnSummary.ts:261) that are all retired at the pin.
• Consequence: an author (or an AI) writing precision: 10 and expecting a DECIMAL(10, s) bound is silently ignored.
• Context: PR fix(spec): a currency field's precision is total digits — stop refusing precision: 18 on a fixed-USD field (#20011) #20209 (finding(spec): the #7918 anchor reads a currency field's precision as its display width, refusing precision: 18 on a fixed-USD field though the key is "Total digits" and ruling 乙 gives decimals to the currency #20011) removed the field-level ISO 4217 comparison, because the key means total digits, not decimals. It kept the currencyConfig.precision anchor, which is this card's original site.

Dedupe words: field precision no reader · Total digits precision unenforced · liveness field.json precision stale evidence

[objectstack-fleet]

Claim: PM loop round 1 · 2026-09-27T10:51Z
Session: session_01Rjy9MeetSfq34PKn81CRiN
Account: os-zhuang
Branch: claude/issue-19992-currency-config-precision-retire
Worktree: objectstack-issue-19992
Domain: domain:spec
Seat: domain:spec#1
File surface: packages/spec/src/data/field.zod.ts CurrencyConfigSchema only: the precision key (:443 on 3875ae67), its aliases decimals / scale (:428; the other aliases stay), its ISO 4217 check (.superRefine / .overwrite); packages/spec/src/data/currency-fraction-digits.ts if the helper loses every reader; packages/spec/src/data/field.form.ts:78 (the field-level precision help text only); one ADR-0087 entry + packages/spec/src/migrations/registry.ts; packages/spec/liveness/field.json; the data-modeling doc sentences that state this rule; generated artefacts; tests; .changeset/. ⛔ Not the defaultCurrency describe (open PR #20217). ⛔ Not FieldSchema.precision itself. (stop on breach; explain in the report)
Container & model: M, mode:subagent, model: default judgment tier (the default slot is taken; a retirement with a premise to measure first). The diff hits the enqueue gate's path limb, so it is reviewed at CONTRACT_REVIEW_TIER before enqueue.
Clause-②: no
Thread-read: 5854612946
Serial constraints cleared: #20011 (the same-file sibling triage named) has landed as 84156c7d. Open PR #20217 (#20126, this seat) edits the defaultCurrency describe a few lines below; the dev does not touch it and merges main after it lands. No other open PR touches field.zod.ts, field.form.ts or currency-fraction-digits.ts. The folded field-level precision site (5854612946) is ⛔ not in scope: this PR is Part of #19992 and names it as the remainder. Direction: triage 5853208433 (remove, with the aliases; stop if a real reader is measured).

[objectstack-fleet]

os-dev-report
{
"issue": 19992,
"status": "done",
"branch": "claude/issue-19992-currency-config-precision-retire",
"pr": "#20251",
"session": "session_01Rjy9MeetSfq34PKn81CRiN — the PM's (mode:subagent); identity = the branch",
"premise_still_valid": true,
"summary": "Retired currencyConfig.precision (ADR-0049 enforce-or-remove, triage direction REMOVE under ruling 乙): strict deletion from CurrencyConfigSchema plus a guidance entry carrying the prescription; the decimals/scale aliases became guidance entries with the same reason; the #7918 .superRefine and the #11423 .overwrite (which baked precision: 2 into parse output) are removed; currencyPrecisionContradiction and currencyFractionDigits (no reader left) removed, CURRENCY_FRACTION_DIGITS kept for the iso_4217_currency value domain. ADR-0087: D2 conversion currency-config-precision-removed (toMajor 18, retiredFromLoadPath, strips the key at rest on objects/objectExtensions), step-18 wiring, RETIRED_KEYS_BY_MAJOR[18] data/CurrencyConfig:precision. Field-form precision help text now 'Total digits' (+ en/zh-CN/ja-JP/es-ES bundles); docs, published skill, 3 showcase objects, generated references and ledgers updated; changeset spec minor + platform-objects patch, BREAKING, adr-0087 registered. PR body: first line 'Part of #19992'; #19992 remains open for the folded FIELD-level precision family site (5854612946). PR is Tier H because skills/** is on the diff.",
"tests": "All on head 3681939 (batch at 74cf413 + the en bundle commit, tree identical). spec build exit 0; spec check:generated exit 0 (15/15); spec typecheck exit 0 (incl. check:test-typecheck); spec vitest --project local: 546 files passed, 16062 tests passed, 2 todo. Consumers: example-showcase typecheck exit 0; platform-objects typecheck exit 0, tests 55 files / 911 passed; service-analytics currency-mode-relay + query-dataset 51 passed; pnpm check:i18n exit 0 (9 packages in sync). Reverse verification Leg A (ablation-replace, anchor 1→0, blob 58a9af7e→700705a8): showcase tsc exit 1, account.object.ts(71,25) TS2353 'precision' does not exist in type {currencyMode?, defaultCurrency?} against the rebuilt spec .d.ts; restored blob==HEAD, git diff HEAD empty. Ablation Leg B (precision re-declared on the schema, blob 7d36200c→86fdbf2d): 9 failed / 279 passed in the two pin files (every retirement pin red; alias, parse-output and conversion pins stay green by design); restored blob==HEAD, git diff HEAD empty; tree clean after both legs (0 bytes). Direction observed: red. No permanent ablation files left.",
"gates": {
"head": "36819398",
"derived": "node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack → 120 commands (repo objectstack-ai/objectstack at 3681939; 3 commits behind origin/main, none touching derivation inputs)",
"reconciliation": "dispatch-gates --ran: 120 derived famil(ies) accounted for — 119 run, 1 NOT-MEASURED (1 DERIVED from a recorded exit 3), 0 UNRUN; exit 0",
"nonzero_first_pass": [
"pnpm --filter @objectstack/spec run check:skill-examples :: exit 3 (client-react dist missing) → after pnpm --filter '@objectstack/client-react...' build: exit 0, '259 prose examples type-check across 3 surface(s)'",
"pnpm check:dual-build-cjs-loads :: exit 3"
],
"not_measured": [
"pnpm check:dual-build-cjs-loads — reason: prerequisite is every package's dist/ (full pnpm build); this diff changes no package entry or exports"
],
"early": [
"node scripts/check-adr-0087-registration.mjs --base origin/main exit 0 (1 declared-breaking changeset, registered currency-config-precision-removed)",
"node scripts/check-changeset-no-major.mjs --base origin/main exit 0",
"pnpm check:nul-bytes exit 0",
"node scripts/check-spec-docblock-symbol-anchors.mjs exit 0"
],
"ci": "0 check runs registered on 3681939 at report time — not waited on (PM owns CI convergence)",
"not_run_locally": "repo-wide pnpm lint (CI's run); cli integration tier (diff touches no packages/cli file); qa/dogfood (boots showcase; CI)"
},
"line_budget": {
"pr_changed_lines": "30 files, +659 / -511 = 1170 vs human-merge threshold 5000: under",
"skills": "skills/objectstack-data/rules/field-types.md 328 → 327 lines; skills/objectstack-data markdown total 3717 → 3716; all skills/*/SKILL.md 4402 → 4402 (pure removal; an added 3-line note was dropped to keep net ≤ 0)"
},
"deviations": [
"liveness/field.json NOT edited (order listed its currencyConfig row): measured — the row covers the container, asserts nothing about precision and stays live (defaultCurrency read); field/currencyConfig is in scripts/liveness/undrilled-containers.baseline.json so no per-key row existed; #20217 had just re-cited that row.",
"File surface beyond the claim, each because this change would otherwise leave it false: shared/value-domain.zod.ts docblock (named the removed function), one comment in conversions/registry.ts, 3 examples/app-showcase objects, content/docs fields.mdx + getting-started/common-patterns.mdx + protocol/objectql/types.mdx, skills/objectstack-data/rules/field-types.md (Tier H), platform-objects translation bundles, and generated/ledger rows (authorable-surface/data.json hand-removed per gate (a); authorable-defaults/data.json regenerated; dropped-refinements.baseline.json 13 sites hand-removed; references regenerated). Also comment-only edits elsewhere in field.zod.ts that named the removed twin.",
"PR is Tier H (skills/** on the diff): landing needs the maintainer's APPROVED review, not only the contract-tier record. The body carries the 维护者速读(草稿) section with 席位意见 left blank.",
"No tree-scoped absence text pin, deliberately: precision stays authorable as the FIELD-level key, so the retired thing is a key in a position; followed the dashboard-chart-structure-refusal.test.ts precedent (rationale block in the pin file); tsc (Leg A) and the closed parse door (Leg B) stand in.",
"decimals/scale: guidance entries (strict route, FieldSchema 'currency' guidance precedent) rather than bare unknown-key reports; not converted (never legal, no stored row carries them).",
"Clause-② copied verbatim from the claim as 'Clause-②: no' (no arm); the change is a narrowing — the changeset's BREAKING banner and adr-0087 marker carry that (check-adr-0087-registration green). The '(narrowing)' arm was not added because the claim did not carry it.",
"Merged origin/main (3cb84d0, #20217 landed) with scripts/pm/os-regen-merge.sh before opening the PR; 4 conflicts resolved by stacking both sides; sibling entries measured present (same counts as origin/main). The regeneration commit first carried the merge message and was reworded locally before any push.",
"docs/qa/platform-checklist/areas/records-forms.json not edited (item broadly stale on currency scale from an earlier card) — Acceptance notes.",
"Verify-lock queue: ~2h of cumulative queue time across batches (99s retried with the same slot; queue progressed throughout)."
],
"files_changed": [
".changeset/19992-currency-config-precision-retired.md",
"content/docs/data-modeling/field-types.mdx",
"content/docs/data-modeling/fields.mdx",
"content/docs/data-modeling/validation-rules.mdx",
"content/docs/getting-started/common-patterns.mdx",
"content/docs/protocol/objectql/types.mdx",
"content/docs/references/data/field.mdx",
"content/docs/references/data/object.mdx",
"content/docs/references/shared/value-domain.mdx",
"content/docs/references/system/migration.mdx",
"examples/app-showcase/src/data/objects/account.object.ts",
"examples/app-showcase/src/data/objects/field-zoo.object.ts",
"examples/app-showcase/src/data/objects/semantic-zoo.object.ts",
"packages/platform-objects/src/apps/translations/en.metadata-forms.generated.ts",
"packages/platform-objects/src/apps/translations/es-ES.metadata-forms.generated.ts",
"packages/platform-objects/src/apps/translations/ja-JP.metadata-forms.generated.ts",
"packages/platform-objects/src/apps/translations/zh-CN.metadata-forms.generated.ts",
"packages/spec/authorable-defaults/data.json",
"packages/spec/authorable-surface/data.json",
"packages/spec/dropped-refinements.baseline.json",
"packages/spec/src/conversions/registry.ts",
"packages/spec/src/data/currency-fraction-digits.ts",
"packages/spec/src/data/currency-precision-iso4217.test.ts",
"packages/spec/src/data/field.form.ts",
"packages/spec/src/data/field.test.ts",
"packages/spec/src/data/field.zod.ts",
"packages/spec/src/migrations/entries/retired-keys/18.data__CurrencyConfig__precision.ts",
"packages/spec/src/migrations/registry.ts",
"packages/spec/src/shared/value-domain.zod.ts",
"skills/objectstack-data/rules/field-types.md"
],
"mcp_calls": "0",
"api_writes": "3 relay writes as objectstack-fleet[bot] via repository_dispatch (POST /repos/objectstack-ai/objectstack/dispatches each): (1) pr_create → POST /repos/objectstack-ai/objectstack/pulls (run 36327385351, PR #20251 draft); (2) label-write assign → POST /repos//issues/20251/assignees os-zhuang (run 36327433373, read back); (3) post-stamped → POST /repos//issues/19992/comments (this os-dev-report). Plus 7 git pushes on the paced route (write-pace --kind 'git push'), not REST.",
"open_questions": [
{
"question": "Landing path for the Tier H surface: keep skills/objectstack-data/rules/field-types.md in this PR, or split it into its own PR so the code half lands on the contract-tier record alone?",
"options": [
"A — keep one PR (Tier H: maintainer APPROVED review, then the owning seat lands it)",
"B — split: code/docs PR lands at contract tier; a one-file skills PR waits for the maintainer"
],
"recommendation": "A. 实际业务需求: the skill is what AI authors read, and after the code lands it would teach a refused key — the trap this card removes. 长远合理性: one landing keeps the contract and its teaching text consistent at every commit of main. 防 AI 犯错: under B there is a window where the published skill contradicts the schema. 不扩散: B costs a second PR and review for a 2-line removal. The cost of A is waiting for the maintainer's word."
}
],
"out_of_scope_findings": [
"carrier: next checklist-author sweep; 承接者:无 · docs/qa/platform-checklist/areas/records-forms.json item records-forms.field-type-constraints describes f_currency as 'scale 2 currencyConfig{precision 2}' and probes currency scale — stale on both halves; internal QA prose, not published · noted, not filed",
"carrier: 承接者:无 · standalone 'field' metadata rows are outside every field conversion (applyConversionsToStoredItem has no 'fields' stack collection), this one included, same as its precedents; no producer of such rows measured · noted, not filed"
]
}

---

Generated by Claude Code