#19188 split: 145 top-level zod-only keys need a RECORDED REASON, never a form row — and none can be recorded until the ledger learns a root path

[os-litant]

Blocked-by: #19329
Path: none | 账本记录 145 个键的不授理由 | 先决条件 #19329

The bucket group

145 keys of #19188's 274 need a recorded reason, ⛔ never a form row. Offering a control for any of them would itself be the defect. Four sub-buckets, by why they are not authored:

sub-bucket	count	criterion	what it needs
ADR-0010 provenance / lock overlay	132	in the liveness gate's own FRAMEWORK_FIELDS set — 7 underscore keys on all 17 forms (119) plus protection on 13	ONE recorded reason covering the whole overlay, ⛔ never 132 rows
platform-written, never authored	4	the schema's own description says the value is not authored (console round-trip state, or machine-managed)	a recorded reason
deprecated / legacy alias	4	the description carries a bracketed DEPRECATED or LEGACY ALIAS marker	a ledger omit row of the shape the gate already uses — page.interfaceConfig.sourceView is the precedent
declared, deliberately not enforced yet	5	the liveness ledger verdict is planned or experimental	no offer until it is enforced; the ruling belongs to the enforcement card, ⛔ not to this gate

Examples: object._lock · field._provenance · view.columnState · view.isPinned · object.titleFormat · view.drawerWidth · object.externalSharingModel · action.onSuccess.

⚠️ This card is blocked in practice, and by what

Every one of these 145 needs the ledger to accept a top-level coordinate, which it does not — see the prerequisite card filed alongside. ⇒ this card cannot record its first reason until that lands. It is filed now so the 145 keys are not lost, ⛔ not because it is ready.

One key whose machine-written status is spelled only in prose

app._unpublished is underscore-prefixed and described as 「Machine-managed … Never authored」, but it is NOT in the liveness gate's FRAMEWORK_FIELDS overlay set and instead carries an ordinary live row. Nothing is broken by it today (no gate reads that set for authorability), but it is the one key here whose status no machine reads. Whoever writes the platform-written reason should say what it is.

Dedup words

recorded reason not offered · FRAMEWORK_FIELDS overlay reason · ledger omit row precedent · planned experimental no offer · app._unpublished framework field

---

Origin: the #19188 census round, report comment 5749550902 (2026-09-20T11:37Z), base 596090efbe7. Its numbers were re-derived by the dev with the reconciliation gate's OWN helper block sliced verbatim (sha256 f6729dae2829…), ⛔ not by grepping source, with a lit control (name, offered by 17 of 17 forms) and a dark control (a fabricated key, 0) asserted inside the probe.
Filed-by: session_01LvwGppdonww4zGLWZo5rho (domain:spec execution seat 1), as the split triage asked for at 5747751499 — 「the claiming seat's first deliverable is the split, not the fix」. ⛔ Not graded and ⛔ not routed by this seat.

---

Generated by Claude Code

[os-justin]

UNLOCKED — Blocked-by: #19329 is satisfied, and the body's key figure is corrected

domain:spec seat 5 (session_01Sfe5YjBLwB9J3y8fvm2xq1), 2026-09-22T04:54Z. pm:blocked → pm:queue in the same act.

The unlock, judged by CONTENT rather than by card state

⛔ 「the blocker card is closed」 is not the judge — what this card waits on is the ledger actually learning a root path. All four readings taken here:

reading	value
card #19329	closed / state_reason: completed
its PR #19639 on origin/main	3a9b07f3b, single parent
the capability itself	packages/spec/src/system/metadata-form-zod-reconciliation.test.ts:139 — const ROOT_PATH = '(root)';
control, same instrument and file	censusRefusals / nestedLists ⇒ 16 hits, so the grep is reading the file

⇒ the root coordinate exists on main. This card's own words — 「none can be recorded until the ledger learns a root path」 — are satisfied.

⚠️ The sibling prerequisite the split also named, the ADR-0010 framework-field skip, landed in the same PR and is scoped to the root coordinate only (offerableKeysAt: the filter is reachable only when path === ROOT_PATH). So the overlay is skipped at the root and nowhere else, which is the shape this split assumed.

⭐ The 145 in this card's title and body is WRONG — it is 142

Measured on 744a0a3f1 by the dev of #19329, with the reconciliation gate's own helper block sliced verbatim, a lit control (name, offered by 17 of 17 forms) and a dark control (fabricated key ⇒ 0):

top-level authorable keys not offered   274
of those, the ADR-0010 overlay          132
274 − 132                             = 142     ⛔ not 145

⇒ the card's 274 / 132 / 145 cannot all be readings of one population — the arithmetic does not close. Every other figure in the split reproduced. The dev reported the divergence instead of bending its measurement to the card, which is the right call, and this seat verified the reasoning rather than the count being merely asserted.

Whoever takes this card re-derives the population on the tree of that day and uses what it prints — ⛔ do not inherit 145, and ⛔ do not inherit 142 either: both are readings of trees that will have moved. The title still says 145 and is left alone; correcting a title is not worth a second write against a number that must be re-measured anyway.

⛔ No grading and no routing from this seat — priority:p3 and domain:spec stand as triage set them.

---

Generated by Claude Code

[os-justin]

本轮到达本卡、⛔ 未取 —— 落点被三张开着的 PR 占着,读数写明免得下轮重推

domain:spec seat 5(session_01Sfe5YjBLwB9J3y8fvm2xq1,座位贴 #19357),2026-09-22T11:43Z。⛔ 不是认领、⛔ 不是改判、⛔ 未写任何标签。本卡本轮排在取卡序前列 —— 前置(北极星第 3 条)过了,阻塞也确实已由本席在 5771402501 解除,卡在占位上。

取卡前置,现读

开放 priority:p0 = 4(#12243 · #11663 · #11632 · #2714,全 pm:epic / tracking,⛔ 无一在本车道);开放 priority:p1 = 33,其中 domain:spec 且可取 = 0。第 3 条拦的是 p2/p3 的工具卡、契约卫生卡;本卡 priority:p3 不带 tooling 标签 ⇒ 按可执行的那份判据不被拦。

占位普查 —— 24 张开着的 PR 的文件清单,逐条

本卡的 142(⛔ 不是 145,见 5771402501)个键横跨 object.* · field.* · view.* · action.* · app.*,账本是按元数据种类分文件的 packages/spec/liveness/<kind>.json。现读:

落点	被谁占着
packages/spec/liveness/README.md	PR #19659 · PR #19657 · PR #19618(三张)
packages/spec/liveness/object.json	PR #19618
packages/spec/liveness/view.json	PR #19598
packages/spec/liveness/state-counts.md	PR #19618
packages/spec/liveness/connector.json	PR #19657
packages/spec/src/system/metadata-form-zod-reconciliation.test.ts	空

⇒ 本卡至少要写 object.json 与 view.json,两张都有主;它几乎必然还要重生成 state-counts.md,也有主。⛔ 不派。

解冻条件,写死免得凭感觉判

上表里 object.json · view.json · state-counts.md 三条同时无主。⇒ 盯 PR #19618(占三条里的两条)与 PR #19598(占 view.json)落地,两张一落本卡即可派。

⚠️ 与 #19334 的自相串行,一并记下

#19334(同为 #19188 拆卡)要写的正是 packages/spec/liveness/view.json。⇒ 本卡与 #19334 不可并派;今天两张都被 PR #19598 挡着,所以这条串行暂时是空谈,但 PR #19598 一落它就是真的。先派本卡(它把 132 个键收进一条记录理由,产出密度高得多),#19334 排其后。

⛔ 本条不改本卡的定级、车道或状态。

---

Generated by Claude Code