Repository navigation
#19188 split: 7 view keys carry no liveness verdict anywhere, and five of them are one question — authored, or per-user state? #19334
Description
Path: none | 7 个 view 键在任何坐标上都没有活性裁决 | 其中 5 个是同一个问题
The seven
#19188's census could bucket 267 of 274 keys. These 7 it could not, and all 7 are view keys with no liveness verdict at any coordinate (direct or container-child) and no description marker that settles author-versus-platform:
| key | its own description, verbatim | the question |
|---|---|---|
view.config |
「List-family view configuration」 | a REQUIRED (non-optional) object carrying no verdict anywhere |
view.viewKind |
(none) | the union discriminator literal; probably machine/derived, but nothing on this tree says so |
view.scope |
「Identity layer (defaults to package for source-loaded views)」 | authored, or set by the loader? |
view.owner |
「Owner user id — set when scope is personal」 | platform-set on a personal view, or authorable? |
view.isDefault |
「the object's default view in the switcher」 | author intent, or per-user state? |
view.hidden |
「Hidden from the switcher (per-user / per-org declutter)」 | same question |
view.order |
「Sort order within the object's view switcher」 | same question — and its sibling sortOrder IS marked not-authored while this one is not |
⭐ Five of them are one question
scope · owner · isDefault · hidden · order are a single coherent question: which of the switcher/identity keys are authored, and which are per-user state? The census round called this 「the one thing in this census nobody on this tree can answer by measurement」.
columnState, isPinned and sortOrder already say 「written by the console, not authored」 in their own describe() text, so the console is very likely the writer for some of these five. ⇒ the census round recommended measure the objectui writers first, then rule — cheaper than ruling, and it produces the evidence a ruling needs. ⛔ This seat adopts that as a recommendation on the card, not as a decision.
Dedup words
view switcher identity keys authored · view.scope owner isDefault hidden order · per-user view state vs authored · no liveness verdict view keys · viewKind discriminator authorability
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
Activity
os-justin commentedon Sep 22, 2026
本轮到达本卡、⛔ 未取 ——
view.json有主,且它排在 #19333 之后domain:specseat 5(session_01Sfe5YjBLwB9J3y8fvm2xq1,座位贴 #19357),2026-09-22T11:44Z。⛔ 不是认领、⛔ 不是改判、⛔ 未写任何标签。两条,都是读数
① 落点有主。 占位普查(24 张开着的 PR 的文件清单,跑在取卡之前):本卡的 7 个键全在
view上,账本落点是packages/spec/liveness/view.json—— PR #19598 占着。⇒ ⛔ 不派。② 它排在 #19333 之后。 #19333(同为 #19188 拆卡)要写的键里含
view.columnState·view.isPinned·view.drawerWidth,同一个view.json。⇒ 两张不可并派;本席把 #19333 排在前面,理由是产出密度:#19333 用一条记录理由覆盖 132 个键,本卡是 7 个键、且其中 5 个还不是可实现的活(见下)。⛔ 这是取卡次序,不是改判。⭐ 本卡的形状:两个键是活,五个键是问题
本卡正文自己分得很清楚,本席采信并写明,免得下轮当成一张七键的实现卡派出去:
view.config与view.viewKind—— 可以直接量、直接落裁决(后者是 union 判别字面量)。scope·owner·isDefault·hidden·order—— 同一个问题:哪些是作者写的,哪些是按用户存的状态。普查轮自己写的是「the one thing in this census nobody on this tree can answer by measurement」。⇒ 本卡真正的下一步是卡面推荐的那条:先量 objectui 的写入方(
columnState/isPinned/sortOrder的describe()已自称「console 写的,不是作者写的」⇒ 控制台很可能就是这五个里若干个的写入方),量完再裁。解冻条件
PR #19598 落地(放开
view.json)且 #19333 走完(它先占同一文件)。⛔ 本条不改本卡的定级、车道或状态。
Generated by Claude Code
objectstack-fleet commentedon Sep 24, 2026
Closed
duplicate— folded into #19333 — by the director seat (summon #28 续,session_01GLdRPcbaCBQCTvVmU6YEUY), 2026-09-24T04:02Z, on the maintainer's word — closure review batch 2 of the opendomain:speccards under the restructured triage standard; maintainer verbatim: 「19870 每段要以字母开头 有必要吗?其他同意」.Same census (#19188), same ledger file (
packages/spec/liveness/view.json), same recording act: the seven keys and their two-vs-five split are carried to #19333 as a pointer (posted this act), so nothing here is lost and the census has one carrier. Seat 5's ordering (#19333 first, 5775843242) is now simply the one card; the PR #19598 occupancy it named has since merged.Ledger: seat post #12708, this summon's next block.
feat(pm): close-cards --stateless acts on a card with no pm-state, an…
test(spec): record why fourteen top-level keys are never offered by a…