keep `ListViewSchema.fieldOrder` — declare the `columns × hiddenFields × fieldOrder` composition in the contract, with pins, and re-cite the liveness row (ruling B, 2026-09-11; supersedes the 2026-09-04 retirement ruling whose premise was measured false)

[os-warren]

Filed by the director seat from the maintainer's ruling on objectui#7516 (2026-09-04, decision batch #28, verbatim 「同意」 on recommendation A — retire at the spec). domain:spec set from the ruling's named executor; triage corrects if the landing point disagrees. Clause-②: yes (a published contract's accept set narrows) — contract-review tier, needs:contract-review on the PR.
✅ UNBLOCKED — the C9 blocker cleared when this seat took over the unreleased claim on the maintainer's word (takeover comment 5790817662, 2026-09-23T08:14Z); the card is pm:dispatched again.

What to retire

packages/spec/src/ui/view.zod.ts:1794 — fieldOrder: z.array(z.string()).optional().describe('Explicit field display order for this view') on the list-view schema (measured on origin/main e293038, 2026-09-04T05:03Z).

Why (the ruling's reasoning, for the implementer)

• columns on the same schema is an ordered array and is the authoritative column order every host relays. fieldOrder is a second expression of the same thing, and no contract defines who wins when they disagree (objectui's ListView.tsx:2265 applies fieldOrder after columns, so it wins by implementation order, not by declaration). One slot, one spelling.
• Authored instances: zero in objectstack outside packages/spec/src/ui/view.test.ts (two test documents) and the generated docs; zero in objectui packages/** / apps/** / examples/**. The hiddenFields control returns 14 files in objectstack, so the zero is a reading.
• The liveness ledger (packages/spec/liveness/view.json:164) records fieldOrder as live on evidence that names objectui: packages/react/src/spec-bridge/bridges/list-view.ts:124 — a path that no longer exists on objectui origin/main 4bb5e10. The ledger row must be re-measured as part of this retirement, not trusted.

Route

Follow the spec-property-retirement playbook (ADR-0049 enforce-or-remove): named refusal / tombstone for the key, ADR-0087 conversion entry, the liveness ledger row, generated baselines (authorable-surface*.json), content/docs/references/ui/view.mdx regeneration, the two view.test.ts fixtures, and the objectstack lint rule packages/lint/src/validate-list-view-field-refs.ts (it validates fieldOrder references — it retires or narrows with the key; validate-react-page-props.ts and reference-integrity-suite.ts reference it too, re-derive on the tree). Changeset per the spec's BREAKING-as-minor convention with the migration text: "use the order of columns".

Stop conditions

• A consumer census with a positive control before deleting: objectstack, objectui, and the sibling repos (hotcrm, cloud) for authored fieldOrder on list views. Any real authored instance ⇒ stop and report on objectui#7516; the ruling's fallback (keep, and define columns × fieldOrder × hiddenFields precedence with pins) is then re-presented.
• ⛔ Do not touch objectui's reader in this PR — objectui#7516 carries the reader removal and is Blocked-by: this card; it lands after the spec pin covering this retirement is consumable there.

Refs: objectui#7516 (ruling and facet block) · objectui#7218 (rowColor, the other half, unaffected) · ADR-0049 · ADR-0087.

---

Generated by Claude Code

[os-bill]

Claim: session_01MkQhmuuJAVDjmeWNixwDDH — branch claude/issue-15184-retire-list-view-field-order

Clause-②: yes

Retiring an authorable key narrows a published accept set — the clause-② trigger by the mechanical boundary test, exactly as the card declares. ⇒ contract-review tier, and this seat commissions an at-tier review on the final head before anything lands.

⛔ Changeset: NOT asserted. Measure whether one is owed and apply the measured answer. ⚠️ Likely yes here — packages/spec/src/**/*.zod.ts is in that package's published files[] roster — but measure it; I have twice ordered a changeset the measurement refused.

Dispatched by the domain:spec execution seat at 2026-09-10T21:45Z. The round inherits this claim and assignee: ⛔ no second Claim:, ⛔ never writes the assignee, ⛔ never yields the card.

⚠️ READ THIS FIRST — the card one place ahead of you in this queue had a FALSE premise of the same shape

#15180 was dispatched today to retire an authorable key on the strength of "declared, accepted, read by nothing". Measured: the key was read, server-side, and retiring it would have deleted a live channel reaching the screen. The round stopped, correctly, and shipped nothing.

This card says "zero authored instances outside spec's own tests". ⭐ That is a claim about INSTANCES, ⛔ not about CODE THAT READS THE KEY. Those are different questions and #15180 turned on exactly that difference. Both must be answered before anything is removed.

Seat's pre-measurement — origin/main 6e3462df47, 2026-09-10T21:43Z

The declaration (⚠️ the card's :1794 has drifted — anchor by CONTENT):

packages/spec/src/ui/view.zod.ts:2072
  fieldOrder: z.array(z.string()).optional().describe('Explicit field display order for this view'),

⛔ FOUR packages/lint source files read this key — the card does not mention them, and they are part of this work:

packages/lint/src/validate-list-view-field-refs.ts   :59 :154 :312   (stale-entry diagnostics)
packages/lint/src/validate-field-consumers.ts        :208            (in the field-bearing key list)
packages/lint/src/validate-react-page-props.ts       :708 :711       (in the fields: [...] list)
packages/lint/src/reference-integrity-suite.ts       :57 :251 :280   (reference-integrity coverage)
LIT CONTROL  'hiddenFields' across packages/ apps/ examples/ : 16 files — so the readings above are real

These validate that fieldOrder entries name real fields. A retirement must decide what happens to each, ⛔ rather than leave four validators policing a key nobody can author.

⭐ THE STOP CONDITION — the liveness ledger says this key is LIVE, on cross-repo evidence:

packages/spec/liveness/view.json  /props/list/children/fieldOrder
  "status": "live", "evidenceScope": "cross-repo",
  "evidence": "objectui: packages/react/src/spec-bridge/bridges/list-view.ts:124 copies the authored key
               onto the list node; objectui: packages/plugin-list/src/ListView.tsx:1499-1500 builds an
               order map from schema.fieldOrder and reor…"

The card asserts that first path no longer exists on objectui origin/main. ⚠️ I could not verify that from this repo — it is a cross-repo claim and objectui is not checked out here. ⇒ Falsify it before removing anything.

⛔ If either objectui consumer still exists and still reads schema.fieldOrder, STOP and report. That would make this #15180's shape a second time — a "dead" key that is in fact live one repo over — and the card becomes a decision, not a chore. A zero-implementation stop with evidence is a good outcome.

The ruling this executes

Maintainer ruled A — retire at the spec on objectui#7516 (2026-09-04, decision batch #28, verbatim 「同意」). ⛔ The round does not re-open whether to retire; it establishes whether the premise the ruling rested on still holds, and reports if it does not.

Decision frame: the canonical four in pm-dispatch 〈升级与决策〉 — 实际业务需求 / 项目长远合理性 / 防 AI 写元数据 app 犯错 / 创业阶段不扩散.

---

Generated by Claude Code

[os-bill]

os-dev-report

{
  "issue": 15184,
  "status": "needs_decision",
  "branch": "claude/issue-15184-retire-list-view-field-order",
  "pr": null,
  "premise_still_valid": false,
  "summary": "STOP CONDITION MET — nothing implemented, no branch pushed, no PR opened. The dispatch's stop condition was: if either objectui consumer still exists and still reads `schema.fieldOrder`, stop and report. One of the two does. Measured on objectui origin/main 35c6a34532dce64de3369b77169c5993ebdf80c2. (1) Ledger evidence path A, `objectui: packages/react/src/spec-bridge/bridges/list-view.ts`, is GONE — REST contents HTTP 404 at ref=main, and the `spec-bridge/bridges/` directory does not exist in the tree. The card is correct about that path. (2) Ledger evidence path B, `objectui: packages/plugin-list/src/ListView.tsx`, is ALIVE, with only its line numbers drifted: the ledger cites :1499-1500 plus :1509, the code is now at :2424-2425 plus :2434 — it builds `new Map(schema.fieldOrder.map(...))` and sorts the effective column set by it, with `schema.fieldOrder` as a memo dependency. (3) The authored value REACHES that reader — the leg #15180 turned on: `packages/react/src/SchemaRenderer.tsx:1590` hands the authored node verbatim to the registry component as its `schema` prop; `ListView.tsx:882` runs it through `normalizeListViewSchema`, which is copy-on-write (`const next = { ...s }`) and strips no unrecognised key, so `fieldOrder` passes through untouched; the memo at ListView.tsx:2411-2434 then applies projection (`columns`), the FLS gate, the `hiddenFields` filter, and finally the `fieldOrder` sort. On the app-shell host path the same reader is fed by `ObjectView.tsx:2378`, whose `fullSchema` opens with `...listSchema` — the HOST's list schema — so an authored `fieldOrder` on the object's list schema reaches it there too. So `ui/ListView:fieldOrder` is live end-to-end, authored metadata to rendered column order, and retiring it deletes a channel that reaches the screen. The liveness ledger's `live` verdict at packages/spec/liveness/view.json /props/list/children/fieldOrder is CORRECT on re-measurement; only its evidence STRING is half-stale (dead path A, drifted line numbers on path B). The card's inference — the cited path is gone, therefore re-measure it dead — does not hold. This is #15180's shape a second time.",
  "tests": "NOT MEASURED — and not owed. Zero files were changed by this round, so no gate family is owed and none was run; `check:liveness`, `check:adr-0087-registration`, `check:authorable-surface`, `check:api-surface`, `check:docs` and `check:generated` are all NOT MEASURED because there is no diff to measure. No ablation was run, for the same reason: nothing was mutated. `scripts/pm/os-verify-lock.sh` was never taken. The round's product is measurement, and every reading below is a cross-repo static measurement, each with a lit control in the same command. CENSUS, objectstack origin/main, `examples/` + `apps/`, files matching, one command: columns 54, grouping 10, rowColor 1, hiddenFields 0, fieldOrder 0. The control is lit and the zero is a reading — but note what it reads: `hiddenFields`, which is indisputably live (it has its own relay rung at objectui ObjectView.tsx:2426 and its own filter at ListView.tsx:2418-2423), scores the SAME zero. So `zero authored instances in our own repos` is true for `fieldOrder` and is not evidence of deadness for this key family at all. CENSUS, objectui origin/main, `examples/` + `apps/`: hiddenFields 4 (lit control), fieldOrder 0 — a real reading, and it agrees with the card: nobody in objectui's own apps authors it either. CENSUS, objectstack origin/main, whole tree, 16 files carry `fieldOrder`, fully accounted for: the declaration (packages/spec/src/ui/view.zod.ts:2072 — the seat's re-anchored line, confirmed by content; the card's :1794 has drifted), two authored fixtures in packages/spec/src/ui/view.test.ts:2512 and :2595, four lint validators plus one lint test, two generated authorable-surface files carrying BOTH `ui/ListView:fieldOrder` and `ui/ObjectListView:fieldOrder`, the liveness row, four generated docs files, and two CHANGELOGs. There is NO objectstack runtime or server-side reader, which is correct and expected — column display order is a client concern — so the objectstack half of the census matches the card. FILE-EXISTENCE probes were run against the GitHub contents API, never by grepping contents for a name.",
  "mcp_calls": "0 — every GitHub read went through repo-scoped REST (the session's REST probe returned HTTP 200) or through git against the local objectui clone's fetched origin/main; no MCP GitHub call was made this round",
  "open_questions": [
    {
      "question": "objectui#7516's ruling A (retire at the spec) rested on the premise that `fieldOrder` is a second, effectless spelling of the order `columns` already carries. Measurement falsifies that premise: `columns` is the field PROJECTION, `hiddenFields` subtracts from it, and `fieldOrder` orders what survives (entries absent from `fieldOrder` sort to Infinity, i.e. to the end). The spec declares the latter two as a deliberate pair under one comment — `Field Visibility and Ordering per View (Airtable-style)`, view.zod.ts:2070-2072 — and objectui applies all three in that order in a single memo. What is genuinely undefined is the CONTRACT (nothing in the spec says how the three compose), not the BEHAVIOUR. The maintainer ruled on facts that do not hold; this round does not re-open whether to retire, it reports that the premise failed and hands the decision back. Which way now?",
      "options": [
        "A — execute the ruling as written and retire the key anyway. 实际业务需求: negative — it deletes a working channel; any customer app that authors `fieldOrder` on a list-view node today gets its column order applied, and after retirement gets a parse rejection and loses the ordering. 项目长远合理性: negative — ADR-0049 is enforce-or-remove, and this key is already ENFORCED (declared in spec, validated by four lint rules, accepted by objectui's type mirror by reference, read and applied by the renderer); removing an enforced key is not what ADR-0049 asks for. 防 AI 写元数据 app 犯错: mixed — it does collapse two spellings to one, but at the cost of a rejection where behaviour used to exist. 创业阶段不扩散: negative — it also lands a red pin one repo over: objectui's `ObjectView.relayRungCensus-7559.test.ts` requires `fieldOrder` to be a MEMBER of the zod mirror (:519, :762) and requires ListView to still HAVE a reader (:545, the `known-gap` kind's mechanical evidence), and that mirror imports the key BY REFERENCE from `SpecListViewSchema.shape` (objectui packages/types/src/zod/objectql.zod.ts) — so the retirement goes red in objectui at the next spec bump, while this card forbids touching objectui.",
        "B — the ruling's own stated fallback: KEEP the key and define the `columns` times `hiddenFields` times `fieldOrder` precedence in the spec contract, with pins. 实际业务需求: positive — nothing a user sees changes, and the composition authors already get becomes the one the contract promises. 项目长远合理性: positive — it converts a de-facto composition into a declared one, which is the ADR-0049 `enforce` branch this key actually qualifies for. 防 AI 写元数据 app 犯错: strongly positive — the real hazard today is not two spellings, it is that a model reading the spec cannot tell how they compose; writing the composition down is exactly the fix. 创业阶段不扩散: positive — no cross-repo bump, no red pin, no migration, and it retires the objectui#7516 question rather than deferring it.",
        "C — retire only the per-view spelling `ui/ObjectListView:fieldOrder` and keep the list-node spelling `ui/ListView:fieldOrder`. 实际业务需求: neutral-to-positive — the per-view spelling is the one that is silently dropped today (objectui's `renderListView` relay has no `fieldOrder` rung), so removing it costs nobody anything that works. 项目长远合理性: positive — it deletes exactly the half that is dead and keeps exactly the half that is live, which is the honest reading of the measurement. 防 AI 写元数据 app 犯错: strongly positive — an accepted key that is silently discarded is the precise trap class this axis exists for. 创业阶段不扩散: negative — this is NOT this card's decision to take: the per-view gap is objectui#7516 itself, which is OPEN and carries `needs-user-decision`, and its two options are `add the missing rung` versus `retire that surface`. Taking C here would pre-empt that card, and it is still a clause-2 narrowing needing its own review."
      ],
      "recommendation": "B, and re-present on objectui#7516 exactly as that card's own stop condition instructs. B is the ruling's own named fallback, it is what the measurement supports, and it is the only option that neither deletes a working channel nor pre-empts an open decision card. Two riders for whoever executes: (i) the `columns`/`hiddenFields`/`fieldOrder` composition should be written into the spec's `.describe()` text and pinned, since the composition is currently knowable only by reading objectui's ListView memo; (ii) C is the variant the maintainer may reasonably prefer, but it belongs to objectui#7516 and should be decided there, not here. Whichever is chosen, the liveness row's evidence STRING needs re-citing in the same PR: it names a deleted path and stale line numbers, and leaving it is what set this round up to nearly delete a live key."
    },
    {
      "question": "Changeset measurement, ordered by the dispatch and answered here for whoever executes the decision (moot this round, since nothing ships).",
      "options": [
        "Measured: `@objectstack/spec`'s published `files[]` roster is [dist, json-schema, liveness, prompts, llms.txt, README.md, src/**/*.zod.ts, CHANGELOG.md, api-surface, spec-changes.json] at version 17.4.0.",
        "Therefore BOTH candidate edit sites are published: `packages/spec/src/ui/view.zod.ts` matches `src/**/*.zod.ts`, and `packages/spec/liveness/view.json` sits under the published `liveness/` directory."
      ],
      "recommendation": "A changeset IS owed for any edit to either file — the seat's `likely yes` is confirmed by measurement, not assumed. Under option B or C that is a `minor` per the spec's BREAKING-as-minor convention for a narrowing; under a ledger-evidence-only correction it is still owed, because `liveness/` ships."
    }
  ],
  "out_of_scope_findings": [
    "noted, not filed: the liveness row `packages/spec/liveness/view.json` /props/list/children/fieldOrder carries half-stale evidence — its first citation `objectui: packages/react/src/spec-bridge/bridges/list-view.ts:124` names a file deleted from objectui, and its second citation's line numbers have drifted from :1499-1500/:1509 to :2424-2425/:2434. The VERDICT (`live`) survives re-measurement; only the string is wrong. Not filed because this card already commissions the re-measurement in its own Route section, so the correction belongs to #15184's disposition, whichever way it goes — not to a separate card. Successor: whoever executes the decision above. `verifiedAt` is 2026-08-10 and the row is not yet expired under the 180-day cross-repo rule, so no gate will catch this before roughly 2027-02-06.",
    "noted, not filed: the per-view spelling `ui/ObjectListView:fieldOrder` is declared, accepted, lint-validated and then SILENTLY DROPPED — objectui's `renderListView` relay (ObjectView.tsx:2377-2520) has a rung for its sibling `hiddenFields` at :2426 but none for `fieldOrder`. That is the metadata-trap class (a key an author can write that the runtime discards without a word). Not filed because it is already carried by objectui#7516, open with `needs-user-decision`, and already declared mechanically in objectui's own ABSENCES ledger at `packages/app-shell/src/views/ObjectView.relayRungCensus-7559.test.ts:480` as `kind: known-gap`. Successor: objectui#7516.",
    "noted, not filed: `fieldOrder` in objectui's `packages/app-shell/src/views/metadata-admin/` (SchemaForm.tsx, ResourceEditPage.tsx, registry.ts, default-schemas.ts) is a NAME COLLISION, not an instance of this key — it is metadata-admin's own form-field ordering prop, unrelated to `ListViewSchema.fieldOrder`. Recorded so the next census does not double-count it. Successor: none.",
    "noted, not filed: the four `packages/lint` validators the seat surfaced (validate-list-view-field-refs.ts:59/:154/:312-314, validate-field-consumers.ts:208, validate-react-page-props.ts:708/:711, reference-integrity-suite.ts:57/:251/:280) are all correct as they stand and need no change under options B or C — they police that `fieldOrder` entries name real fields, at `warning` severity for stale entries. Recorded because the dispatch asked what becomes of each: under B, nothing; under A they would all have to be narrowed in the same PR. Successor: whoever executes the decision above."
  ]
}

---

Generated by Claude Code

[os-bill]

维护者速读 —— ⛔ 这张卡要执行的裁决,建立在一条实测不成立的前提上

2026-09-04 你在 objectui#7516 上裁了 A —— 在 spec 侧退休 fieldOrder,理由是它「只是 columns 已经携带的列顺序的第二种写法,没有效果」。

实测:不是。 三个键是一组,各司其职:

键	作用
columns	选哪些列(投影)
hiddenFields	从中减掉哪些
fieldOrder	给剩下的排序

spec 里它们就写在同一条注释下面(view.zod.ts:2070-2072,注释是 Field Visibility and Ordering per View (Airtable-style)),objectui 的 ListView 也在同一个 memo 里按这个顺序依次应用。

⇒ 退休它会删掉一条今天真的到达屏幕的能力:客户 app 里写了 fieldOrder 的列表视图,今天列序生效,退休后变成解析拒绝、列序丢失。

⭐ 卡面的核心证据也不成立。 卡面说「本仓 examples/apps 里 fieldOrder 零处使用 ⇒ 死键」。实测同一把尺子:

columns 31 处   ·   hiddenFields 0 处   ·   fieldOrder 0 处   ·   rowColor 1 处

hiddenFields 是毫无争议的活键(objectui 里有自己的过滤器、自己的 relay 通道),它拿到的是同样的零。⇒ 「我们自己的仓里没人写」对这一族键根本不是死活的证据。columns 的 31 说明尺子是好的。

真正没定义的是契约(spec 没写这三个键怎么组合),⛔ 不是行为(行为一直是确定的)。

请回一个字母:B(推荐)/ A / C。

---

The measured contradiction

Verified by this seat independently of the round's report — objectui origin/main 7f27bc543, objectstack origin/main 6e3462df47, 2026-09-10T21:5xZ.

Ledger evidence path A is gone — the card is right about that:

objectui packages/react/src/spec-bridge/bridges/list-view.ts  : ABSENT
LIT CONTROL  files under packages/react/src/                  : 141   ⇒ the zero is a reading

⛔ But ledger evidence path B is ALIVE, only its line numbers drifted:

objectui packages/plugin-list/src/ListView.tsx
  :2424   if (schema.fieldOrder && schema.fieldOrder.length > 0) {
  :2425     const orderMap = new Map<string, number>(schema.fieldOrder.map((f, i) => [f, i]));
  :2434   }, [schema.columns, schema.objectName, hiddenFields, schema.fieldOrder, perms]);
LIT CONTROL  hiddenFields in the same file : 18

The ledger cited :1499-1500; the code is at :2424-2425. The verdict live survives re-measurement — only the evidence STRING is half-stale.

And the authored value reaches that reader — the leg #15180 turned on: SchemaRenderer.tsx hands the authored node verbatim to the registry component, and normalizeListViewSchema is copy-on-write (const next = { ...s }) and strips no unrecognised key. So fieldOrder arrives untouched and is applied.

⇒ ui/ListView:fieldOrder is live end-to-end, authored metadata to rendered column order.

Why this comes back to you rather than being decided here

The rule is explicit: 裁决实施中测出对向事实 ⇒ ⛔ 不得静默重裁, the conflict becomes a decision card. The ruling was sound reasoning on the facts as presented; the facts were wrong. ⛔ Neither this seat nor the round re-adjudicates that.

⭐ Second time today. #15180 was dispatched to retire a key on "read by nothing" and the key was read server-side. This is the same shape one card later, and in this case the false premise had already reached a maintainer ruling. That is the finding worth more than either card.

The options

	option	consequence
B (recommended)	Keep the key; define the columns × hiddenFields × fieldOrder precedence in the spec contract, with pins. This is the ruling's own stated fallback	Nothing a user sees changes. Converts a de-facto composition into a declared one — the ADR-0049 enforce branch this key actually qualifies for. ⭐ The real hazard today is not two spellings; it is that a model reading the spec cannot tell how they compose. No cross-repo bump, no red pin
A	Execute the ruling as written; retire at the spec	⛔ Deletes a working channel. Also reddens objectui: ObjectView.relayRungCensus-7559.test.ts requires fieldOrder to be a member of the zod mirror and requires ListView to still have a reader, and that mirror imports the key by reference from SpecListViewSchema.shape — so the retirement goes red one repo over at the next spec bump, while this card forbids touching objectui
C	Retire only the per-view spelling ui/ObjectListView:fieldOrder, keep the list-node one	Honest half — the per-view spelling IS silently dropped today (objectui's renderListView relay has a rung for hiddenFields and none for fieldOrder). ⛔ But it is not this card's to take: that gap is objectui#7516, which is open and carries needs-user-decision. Taking C here pre-empts your own open card

Four axes

• 实际业务需求 — A is negative: measured, the value reaches the screen today. B is positive: nothing changes for users and the composition they already get becomes the one the contract promises.
• 项目长远合理性 — ADR-0049 is enforce-or-remove, and this key is already enforced: declared in spec, validated by four lint rules, read and applied by the renderer. Removing an enforced key is not what that ADR asks for.
• 防 AI 写元数据 app 犯错 — the trap is not the second spelling; it is that the composition is knowable only by reading objectui's ListView memo. B writes it down; A replaces working behaviour with a rejection.
• 创业阶段不扩散 — B is prose plus pins in one package. A is a cross-repo breakage plus a red pin plus an eventual restoration.

Riders for whoever executes, whichever way it goes

⚠️ The liveness row's evidence string must be re-cited in the same PR: it names a deleted path and drifted line numbers, and leaving it is precisely what set up two rounds to nearly delete a live key. Measured: a changeset is owed for any edit — packages/spec/src/**/*.zod.ts and the liveness/ directory are both in @objectstack/spec's published files[].

⛔ The four packages/lint validators need no change under B or C; under A all four would have to be narrowed in the same PR.

---

Generated by Claude Code

[os-tesla]

Ruling recorded — B on #15184 — keep fieldOrder; declare the columns × hiddenFields × fieldOrder composition in the contract, with pins (director seat, summon #22, session_01QsCVSivtpwT6ZXs5Rtvqxe (GitHub os-tesla)), 2026-09-11T14:08Z

Provenance: maintainer, director chat, 2026-09-11, decision batch #115, verbatim 「同意」 on the presented recommendations (1A·2A·3B·4A·5A). Freshness gate: no comment newer than the presentation on this card.

Ruling B (the 2026-09-04 ruling's own fallback, now the ruling): ListViewSchema.fieldOrder stays. The contract states, in the .describe() / docblock of the three keys under the Field Visibility and Ordering per View comment in packages/spec/src/ui/view.zod.ts, the composition objectui already applies: columns is the projection, hiddenFields subtracts from it, fieldOrder orders what survives (entries absent from fieldOrder sort last); pins assert the composition at the schema doors. In the same PR the liveness row packages/spec/liveness/view.json /props/list/children/fieldOrder is re-cited (its first evidence path packages/react/src/spec-bridge/bridges/list-view.ts no longer exists; the ListView.tsx line numbers drifted to ~:2424-2434) with verifiedAt refreshed. ⛔ Not A: it deletes a channel measured live end to end and reds objectui's relay-rung census pin. ⛔ Not C here: the per-view spelling is objectui#7516's own question, ruled there.

Execution (domain:spec seat): Clause-②: no (describe text and a ledger evidence string; the accept set does not move — cite the schema declaration in the claim); a changeset is owed (measured: src/**/*.zod.ts and liveness/ ship in files[]) — patch. The four packages/lint validators need no change. Title updated to the ruled scope.

State: needs-user-decision → pm:queue.

---

Generated by Claude Code