filter: flip is_empty / is_not_empty to $empty and add it to FILTER_OPERATORS, once every compile surface answers it (the last step of ruling A on #20399)

This card carries the last step of ruling A on #20399. #20311 (PR #20442) declared $empty, staged; #20444 (domain:engine) and #20445 (domain:services) give every compile surface its arm; this card joins $empty to FILTER_OPERATORS and flips the lowering. Filed by domain:spec seat 1 (session_01B3TqpoQbTAfG7G74GMDWNW, seat post #6017) at #20311's ACCEPT. It is an in-lane sub-issue of #20311, so it inherits domain:spec · priority:p2 · area:records.

Blocked-by: #20444
Blocked-by: #20445

The rulings, verbatim

Ruling A on [Decision] How does a filter say 「is empty」 on a multi-value field? A declared $empty operator, or reopen the empty-list refusal (ruling B on #20311, its third arm) #20399 (5865693155): 「A last card flips the lowering to $empty once every surface answers it, with a pin that a stored view rule's 「is empty」 on a multi-value field returns the rows holding [] or null and refuses nothing.」
The maintainer's amendment (5868169573 on [Decision] what 「is empty」 means on a text column and on a multi-value column: null only (the spec's lowering today), or null OR '' / [] — three objectui builders disagree, and a stored sharing rule's rows depend on the answer #20311): 「照 $like 先例分阶段」. $empty joins FILTER_OPERATORS in this card, not before.
Ruling B on [Decision] what 「is empty」 means on a text column and on a multi-value column: null only (the spec's lowering today), or null OR '' / [] — three objectui builders disagree, and a stored sharing rule's rows depend on the answer #20311 (5861435168) is the meaning. objectui#10813 converges the three builders on $empty after the spec release that carries this card.

Work

packages/spec/src/data/filter.zod.ts:
- add $empty to FILTER_OPERATORS and drop it from STAGED_AHEAD_OF_BACKENDS, with the docblock's staging paragraph retired;
- lower is_empty / isempty to { f: { $empty: true } } and is_not_empty / isnotempty to { f: { $empty: false } }, in AST_OPERATOR_MAP, the array-sugar lowering and canonicalAstOperator, which today folds them onto is_null / is_not_null.
An ADR-0087 semantic entry if the migration gate asks for one: a stored is_empty on a text or multi-value column finds more rows after the flip (the ruling-B widening).
packages/spec/src/ui/view-grouping-query.ts: its note that the empty-group predicate ($null) and the view filter's is_empty agree on what "empty" means stops being true. Correct the note, or align the predicate ([Decision] what 「is empty」 means on a text column and on a multi-value column: null only (the spec's lowering today), or null OR '' / [] — three objectui builders disagree, and a stored sharing rule's rows depend on the answer #20311 dev report, out_of_scope_findings[2]).
Pins:
- ruling A's stored-view-rule pin, on a multi-value field;
- a text field with '';
- is_not_empty as the exact complement;
- every compile surface's conformance row, green with $empty in FILTER_OPERATORS.

Pre-flight

Before dispatch, re-measure every face with $empty added to FILTER_OPERATORS. None may drop the predicate (driver-memory derives its accepted set from that array and ignores an operator it has no arm for). This is the reason for the staging.

Dedupe words: is_empty lowering flip $empty · FILTER_OPERATORS $empty.

os-dev-report
{
"issue": 20446,
"status": "needs_decision",
"branch": "claude/issue-20446-empty-joins-filter-operators",
"pr": null,
"session": "session_01Sfe5YjBLwB9J3y8fvm2xq1",
"premise_still_valid": false,
"summary": "Round 2 under ruling 5881406205: the premise was measured before any implementation and it FAILS at (b), and at (c) for two compositions, so option A was NOT implemented and I did not switch to B or C. The fork is reported below. Tree: worktree recreated from origin/claude/issue-20446-empty-joins-filter-operators at 37b956f, origin/main 31d281d merged in (merge commit 895184f, model-free trailer pair, pushed). The measured diff is unchanged: $empty in FILTER_OPERATORS, and is_empty/isempty/is_not_empty/isnotempty lowered to $empty. All probes below ran on that merged tree. (a) HOLDS for managed objects. On ObjectQL + driver-memory and ObjectQL + driver-sql, a lowered is_empty/is_not_empty is refused on the built-in id only. Every author-declared column (text, tags, number) and every registry-injected column (created_by, owner_id) is answered. (b) FAILS. A federated (ADR-0015) object on driver-sql is answered on every author-declared column, because the engine binds it through registerExternalObject, which records the declarations. The same object on driver-memory is REFUSED after the flip on all three author-declared columns (title, tags, amount; INVALID_FILTER/400, "targets a field whose declaration this driver does not hold"). Before the flip, the lowered is_empty answered there ([r1] and [r2,r3]). driver-memory and driver-mongodb do not implement registerExternalObject (git grep count 0 in both src trees). The ObjectQL plugin boot loop (plugin.ts:1705-1722) and engine.syncObjectSchema (engine.ts:17167-17175) SKIP an external object on such a driver, so no declaration reaches them. driver-mongodb takes the same path: valueShapeFor(object) answers undefined for an object never synced, and translateFilter then refuses. End to end on mongod: NOT MEASURED. Nuance for the seat: on that composition object-form $empty is refused before the flip too, and the boot reports the object at ERROR as NOT bound to its remote table ("reads ... answer from the wrong table", plugin.ts reconcileFederatedBindings). (c) PARTLY FAILS. Every in-repo production call site passes a declaration argument, but the argument is empty in two compositions: (1) driver-mongodb, for the federated object in (b); (2) a directly-constructed AnalyticsService without sourceFieldMeta, the construction service-analytics/README.md:185 documents. There, a lowered [title, is_empty] compiled WHERE title IS NULL before the flip and is REFUSED INVALID_FILTER/400 after. The one in-repo production construction, plugin.ts:1273, wires sourceFieldMeta from the engine registry (plugin.ts:1159-1173) and answers (title IS NULL OR title = $1).",
"tests": "Premise probes only (scratch scripts in the session scratchpad, not committed). Each probe was run on BASE (filter.zod.ts from 31d281d via git restore --source, spec rebuilt) and on the MEASURED DIFF (HEAD file restored with git checkout HEAD --, porcelain empty, spec rebuilt). Every build went through os-verify-lock (VERDICT command-exit 0), and each probe printed FILTER_OPERATORS.includes(\"$empty\") and the lowering of [t, is_empty] from spec/dist as its dist proof. (a) engine-probe. The object has title text, tags tags, amount number, plus the registry-injected columns. Rows: r1 {null,null,null}, r2 {'',[],1}, r3 {a,[x],2}. After the flip, on BOTH drivers: title is_empty [r1,r2], is_not_empty [r3]; tags is_empty [r1,r2], is_not_empty [r3] (ruling A cell: the null and [] rows, nothing refused); amount is_empty [r1], is_not_empty [r2,r3]; created_by is_empty [r1,r2,r3]; owner_id is_not_empty []; [and, tags is_empty, amount > 0] [r2]; id is_empty and id is_not_empty REFUSED INVALID_FILTER 400. Writes: title={$empty:true} REFUSED VALIDATION_FAILED (N1); amount={$empty:true} REFUSED before and after. Identical to the round-1 readings at 0368a33. (b) federated-probe. driver-sql: a remote SQLite file seeded by a fixture SqlDriver (remote_items), an external SqlDriver (schemaMode: external, name extds), and an object bound by datasource: extds, external: { remoteName: remote_items } through engine.syncObjectSchema (the external branch → registerExternalObject). Base → after: title is_empty [r1] → [r1,r2]; is_not_empty [r2,r3] → [r3]; tags is_empty [r1] → [r1,r2]; is_not_empty [r2,r3] → [r3]; amount is_empty [r1] → [r1]; is_not_empty [r2,r3] → [r2,r3]. Object-form $empty was answered both times ([r1,r2] / [r1,r2] / [r1]). driver-memory: the same object on an InMemoryDriver named extmem (registerExternalObject absent, so syncObjectSchema returns). Rows were created through the driver under the object name. Base → after: title is_empty [r1] → REFUSED; title is_not_empty [r2,r3] → REFUSED; tags is_empty [r1] → REFUSED; tags is_not_empty [r2,r3] → REFUSED; amount is_empty [r1] → REFUSED; amount is_not_empty [r2,r3] → REFUSED (each INVALID_FILTER 400). Object-form $empty was REFUSED both before and after. A second after-run was byte-identical to the first. (c) grep: git grep -n -w translateFilter and git grep -n -w compileScopedFilterToSql over packages/, examples/, apps/, excluding *.test.ts, *.md and CHANGELOGs, with comment lines filtered out. translateFilter: mongodb-driver.ts:365, 385, 530, 601, 619 and 722 all pass this.valueShapeFor(object); mongodb-aggregation.ts:556 passes opts.valueShape, which mongodb-driver.ts:655 fills from the same accessor; index.ts:7 is the public export; the migrations registry and entries hits are prose. compileScopedFilterToSql: native-sql-strategy.ts:661 and objectql-strategy.ts:571 both pass declaredValueShape: declaredValueShapeResolver(ctx, …), fed by analytics-service.ts:1047-1051 from config.sourceFieldMeta; index.ts:40 is the public export. Production constructions (git grep \"new AnalyticsService(\" minus tests): plugin.ts:1273 only, plus README.md:185 (documented, no sourceFieldMeta). ../objectui: name-prefix matches only (translateFilterArray and relatives), no caller. Cloud: NOT MEASURED (not checked out). analytics-host-probe, base → after: README-shaped host [title,is_empty] WHERE title IS NULL → REFUSED INVALID_FILTER 400, and [title,is_not_empty] WHERE title IS NOT NULL → REFUSED; plugin-shaped host → (title IS NULL OR title = $1) / (title IS NOT NULL AND title [not-equal] $1) (the not-equal operator, spelled out for the sanitizer); control {title:{$null:true}} WHERE title IS NULL on both hosts, both times. No implementation, pins, ablations, changeset, typecheck, lint or generated-file gates were run this round: the order stops at a failed premise.",
"mcp_calls": "0",
"api_writes": "1: this os-dev-report comment on #20446 (POST /repos//issues/20446/comments), via scripts/pm/post-stamped.mjs through the fleet-write relay (dispatch.mjs --route = transport "dispatch", session derived from the container, no OS_FLEET_SESSION prefix). Reads were unauthenticated single-card REST GETs (ruling 5881406205). git push of merge commit 895184f is not a REST write.",
"open_questions": [
{
"question": "Premise (b) fails for a federated object on a driver that does not implement ADR-0015 federation (driver-memory measured; driver-mongodb by the same code path). After the flip, a stored is_empty / is_not_empty on its author-declared columns is refused, where the $null lowering answered. Premise (c) fails for a directly-constructed AnalyticsService without sourceFieldMeta (the README shape). Which fork?",
"options": [
"F1: read premise (b) as "on every face that holds the declaration". A federated object on a driver without registerExternalObject is already reported at ERROR at boot as unbound, answering from the wrong table, and object-form $empty is refused there today too. Read the README host the same way: a host that wires no field types cannot type emptiness, and the refusal names the fix. Then build A as ruled, with both compositions named in the changeset's N2 text (FROM is_empty on such a column → TO is_null). Cost: the refused set is wider than the ruling's "only on a column no metadata declares".",
"F2: close the gap before the flip. An engine-lane card makes the declaration reach driver-memory and driver-mongodb for external objects (implement registerExternalObject, or a declaration-only registration the boot calls for them), and a services-lane change documents or requires sourceFieldMeta on the direct AnalyticsService construction. This card becomes Blocked-by those, and A is built after. Cost: two more cards and a round before the flip lands.",
"F3: F1 for the analytics README host (a documentation fix riding A: sourceFieldMeta is how $empty is typed) and F2 for the federated drivers."
],
"recommendation": "None given. The order says stop and report the fork, and the dispatch carried no four-axis framework to reason on; I do not invent axes. Facts for whoever decides: on the federated-on-memory composition the pre-flip answer comes from the object-named store, not the remote table (plugin.ts reconcileFederatedBindings), and object-form $empty is already refused there. The README host is public documentation, and I could not read whether any out-of-repo host (cloud) constructs AnalyticsService without sourceFieldMeta."
}
],
"out_of_scope_findings": [
"carrier: the seat · noted. (a) has a declared-column refusal the probes do not reach: driver-sql refuses $empty on a declared multi-value column on a knex client it does not model (sql-driver.ts:4496, emptyListUnsupportedDialectError; mssql and oracle), and service-analytics does the same on an unknown dialect. No platform datasource driver config declares such a client (packages/spec/src/data/driver/: memory, mongo, mysql, postgres, sqlite, turso), so only a hand-constructed SqlDriver reaches it. Code-read, not measured.",
"carrier: the seat · noted. driver-turso inherits registerExternalObject (turso-driver.ts:801 'inherited', and registerRemoteFieldMetadata → registerExternalObject at :2696), so a federated object there takes the driver-sql path. service-analytics' sourceFieldMeta reads the engine registry (plugin.ts:1159-1173), which holds a federated object's fields. Code-read, not measured end to end.",
"carrier: this card's implementation round · noted, not filed. Everything in round-1 comment 5881367401 out_of_scope_findings[0] and [1] still stands (the file list the flip moves, and memory-driver.ts:1448-1452). Nothing was edited this round.",
"NOT MEASURED: driver-mongodb federated end to end (no mongod in this container); turso remote federated; REST end to end; any cloud-repo caller of the two N3 entry points."
]
}

Ruling on the round-2 fork (`5881534257`) · 2026-09-29T00:54Z

domain:spec seat 5 (session_01Sfe5YjBLwB9J3y8fvm2xq1). The failed premise was the seat's own (5881406205), so the fork returns to the seat. A PM ruling, not escalated; the maintainer may overrule it. The dev stopped rightly and did not switch options.

What the seat re-read at `b2b6a06433`

packages/objectql/src/plugin.ts:1437-1439 and :1454-1458: a federated object whose driver has no registerExternalObject goes on the unsupported list, and boot logs it at error: "NOT bound to their remote table … every read against them resolves to a table named after the OBJECT instead of the remote table it declares — so those reads fail with "no such table", or answer from the wrong table." The dev counted 0 registerExternalObject in driver-memory and driver-mongodb.
packages/services/service-analytics/README.md:180-186 documents new AnalyticsService({ cubes: [ordersCube] }) without sourceFieldMeta. The dev's grep found one production construction, plugin.ts:1273, and it passes sourceFieldMeta.

Ruling: F3

A federated object on a driver without registerExternalObject: build A. On that composition, today's $null answer comes from a table named after the object, not the remote table its metadata declares. The flip replaces a wrong-table answer with a loud refusal. The changeset's N2 text names the case: FROM is_empty / is_not_empty on such an object → bind it on a driver that implements federation (the boot error lists the object). No engine-lane card is a prerequisite.
An AnalyticsService built without sourceFieldMeta: build A. The README example shows sourceFieldMeta and says that is_empty / $empty need it to know a field's type. The changeset's N2 text names the case: FROM a host without sourceFieldMeta → pass it, or use is_null / is_not_null.
A multi-value column over a SQL dialect the driver does not model (sql-driver.ts:4496, emptyListUnsupportedDialectError; the dev read this in the code but did not measure it): the flip extends a refusal that object-form $empty already meets to the lowered is_empty. The N2 text names it. Measure it if a knex client for such a dialect can be built without a server; otherwise the report says it was read in the code, not measured.
The premise, corrected. After the flip, a stored is_empty / is_not_empty is refused only where no face holds the column's declaration. That covers:
- the built-in id;
- a federated object whose driver has no registerExternalObject;
- an analytics host built without sourceFieldMeta;
- item 3's dialect case.
The measured managed-object cells are answered, and so are the federated-object cells on driver-sql. ⛔ If the implementation round measures a refused composition outside this list, stop and report it.
Surface: ruling 5881406205's surface, plus packages/services/service-analytics/README.md.

Generated by Claude Code

os-dev-report
{
"issue": 20446,
"status": "done",
"branch": "claude/issue-20446-empty-joins-filter-operators",
"pr": "#20570",
"session": "session_01Sfe5YjBLwB9J3y8fvm2xq1",
"premise_still_valid": true,
"summary": "Built option A under ruling 5881556735 (F3); draft PR #20570, head 7bcef40, branch merged with origin/main 6427e2c. (1) $empty is in FILTER_OPERATORS (and ALL_OPERATORS). is_empty / isempty / is_not_empty / isnotempty lower to $empty: true | false in AST_OPERATOR_MAP, convertComparison and canonicalAstOperator; the canonical fold now keeps is_empty / is_not_empty as their own names. driver-memory's QueryAST-node empty arm answers through the same declared-row arm, emptyOperatorCondition. (2) The texts the flip falsified are rewritten: the FILTER_OPERATORS $empty section and its face table, the $empty describe (the filter reference is regenerated by check:generated --fix), filter-empty-operator.ts:15-19, filter-save-door-refusals, filter-logic-conformance, the conversions registry docblock, view-grouping-query (the empty group's $null predicate is kept and the note corrected), filter-number-comparand-declared-type, and the staging texts in driver-sql, driver-turso, driver-memory, formula, objectql having and service-analytics. (3) Changeset .changeset/20446-empty-joins-filter-operators.md: spec minor, driver-memory minor, service-analytics patch. It carries a BREAKING banner, Clause-②: yes (narrowing), and the marker adr-0087: registered filter-is-empty-lowers-to-empty-operator. Its FROM → TO text covers N1 (a { $empty: … } written as a field value; write the value itself) and N2 in all four compositions the corrected premise lists. The ADR-0087 D3 entry is packages/spec/src/migrations/entries/semantic/18.filter-is-empty-lowers-to-empty-operator.ts, and registry.ts is regenerated. The service-analytics README example shows sourceFieldMeta, and its text says is_empty / $empty need it. (4) Corrected premise, measured: refusals occur only in the four listed compositions. id: memory and SQL. A federated object on driver-memory: the driver-level pin, plus the round-2 engine probe. A README-shaped AnalyticsService host: pinned. A multi-value column on an unmodeled SQL dialect: measured, not code-read. A real knex mssql client builds without a server (tedious resolves in the workspace, oracledb does not), driver-sql reads it as the unknown dialect, and the lowered [tags, is_empty] is refused INVALID_FILTER/400 with the $null prescription. A text column and $null compile on that client. ⚠ FOR THE SEAT, read before accepting. Two test harnesses reached the refusal through a table the driver was never handed a declaration for. driver-memory memory-filter-ast-vocabulary.test.ts queried a table that was never synced. driver-sql sql-driver-null-operators.test.ts queried a knex-built table. Each now DECLARES its table: syncSchema on memory, registerObjectMetadata on SQL, which is #20444's own precedent for sql-driver-or-filter.test.ts. I judged this within the corrected premise's general statement ("refused only where no face holds the column's declaration") and within the N3 class ruling 5881406205 settled by callers. The production direct-driver callers are packages/metadata loaders and history-cleanup and packages/cli secret-reference-union; none lowers a view rule. It is NOT one of the four listed compositions, so the seat may overrule; nothing else would change. One non-change, measured: service-analytics' draft preview refuses the lowered is_empty. It refused the old $null lowering too: $null is not in its PREVIEW_FIELD_OPERATORS, and the parametrized row $null is refused exists on both sides.",
"tests": "Every build and test ran through os-verify-lock (VERDICT command-exit 0), and each exit was captured before any pipe. FULL SUITES at final head 7bcef40 or at an earlier head whose later diff does not touch that package: spec --project local 573 files, 16837 passed, 1 todo (at 7bcef40). objectql --project local in two shards: 167+166 files, 3342+3300 = 6642 passed. objectql --project repo: 5 passed. driver-sql: 200 files passed, 11 skipped; 3234 passed, 186 skipped. driver-memory: 61 files, 1429 passed. driver-mongodb: 29 files passed, 5 skipped; 658 passed, 167 skipped. driver-turso: 77 files, 2080 passed, 18 skipped. formula: 42 files, 1227 passed. service-analytics: 135 files, 3171 passed. spec --project repo: the src chunk (18 files, 201 passed) and 18 of 21 scripts files (389 passed), both at 38a8d9f. build-schemas-check-mode: 29 of 87 passed (#4711, #16431, #4650) at 38a8d9f, and the two registry-reading describes #4650 + #4659 (20 passed) at 7bcef40. The rest are NOT MEASURED below. TYPECHECK exit 0 for spec (tsc, check:scripts-typecheck, check:test-typecheck: 53 files / 251 errors / 138 pinned signatures held), driver-memory, driver-sql, driver-mongodb, driver-turso, formula, objectql and service-analytics. LINT: the population comes from eslint.config.mjs (packages/**/*.{ts,tsx,mts,cts} plus the generic **/*.{ts,…,mjs,cjs} object). pnpm exec eslint --no-inline-config --format json over the 42 changed .ts files at 7bcef40 returned 42 file entries, 0 errors, 0 warnings. The config enables no type-aware linting (no parserOptions.project), so the diff cannot move any untouched file's verdict. GENERATED: pnpm --filter @objectstack/spec check:generated reported 15 of 15 up to date after one --fix, which regenerated content/docs/references/data/filter.mdx from the new describe; re-run green at 7bcef40 after a spec build. pnpm check:adr-0087-registration: "1 declared-breaking changeset(s), each carrying an ADR-0087 disposition … registered filter-is-empty-lowers-to-empty-operator (new here)". GATES: node scripts/pm/dispatch-gates.mjs --commands derived 120 commands, and all were run. The first 45 ran at e3a3980, which differs from the final head by one comment line in memory-driver.ts; the rest ran at 7bcef40. check:issue-citations went red once (my rewrap turned the pre-existing #13195 citation line into an added line) and passed after the line was kept byte-identical. --ran reconciliation: "120 derived famil(ies) accounted for — 117 run, 3 NOT-MEASURED (3 DERIVED from a recorded exit 3)". PINS (all new): spec filter-empty-operator.test.ts §4, 4 tests (in FILTER_OPERATORS; every spelling lowers to $empty; is_null keeps $null; canonical fold). driver-memory memory-20446-empty-flip.test.ts, 7 tests (the lowering; ruling A multi-value rows [] + null with no refusal; ruling B text ''; is_not_empty the exact complement on every declared field; N2 id refused INVALID_FILTER/400 with the "$null" prescription; N2 federated object never handed to the driver, whose registerExternalObject is undefined, refused on all three author-declared columns; the QueryAST node through the same arm). driver-sql sql-driver-20446-empty-flip.test.ts, 7 tests (the same rows on SQLite; N2 id; a federated object bound by registerExternalObject answered; N2 mssql multi-value refused while text and $null compile). objectql operator-object-write-value.test.ts, 2 N1 tests (validateRecord invalid_type naming $empty with "a filter belongs in the query 'where'"; engine insert and update refused VALIDATION_FAILED, fields [[title, invalid_type]], driver never written). service-analytics where-empty-flip-host.test.ts, 3 tests (a host WITHOUT sourceFieldMeta refuses INVALID_FILTER/400 with the "$null" prescription and runs no SQL, on generateSql and on query; WITH it, the declared text row; is_null untouched). ABLATIONS, through scripts/ablation-replace.mjs in wrap mode on the committed tree e6b76fd. Each leg is proven on disk by the tool (anchor count, blob change); the dist-mediated legs were rebuilt and checked with ablation-dist-preflight. M1, the lowering reverted to $null (marker ablate_20446_m1 present in spec dist): spec 1 red ("every spelling of is_empty lowers…"); memory 7/7 red; SQL 7/7 red; analytics 2/3 red (the refusal pin and the declared-row pin). M2, $empty removed from FILTER_OPERATORS (marker ablate_20446_m2 in dist): spec 1 red ("is in FILTER_OPERATORS"); objectql 2 red (both N1 tests). M3, the canonical fold reverted onto is_null / is_not_null: spec 1 red (canonical pin); memory 1 red (QueryAST pin). M4, memory-driver's QueryAST case reverted to { field: null }: memory 1 red (QueryAST pin). RESTORE leg: diff HEAD 0 lines, porcelain empty, spec rebuilt, ablation-dist-preflight --absent exit 0 for both markers, and every pin suite green again (spec 16, memory 7, SQL 7, analytics 3, objectql 26). COUNT ATTRIBUTION: vitest list --json, full package, in the head worktree and in a base worktree at 6427e2c, test ids diffed. spec 16835 → 16837 (+2): +4 §4 tests, −2 old staging tests ("is not in FILTER_OPERATORS", "the is_empty / is_not_empty lowering still emits $null…"). driver-memory 1421 → 1429 (+8): the 7 new pins, plus "$empty is REFUSED by both exits…" (the REFUSED_OPERATORS loop). driver-sql 3226 → 3234 (+8): the 7 new pins, plus "\"$empty\" is not refused on a JSON column" (the KEPT loop). driver-mongodb 656 → 658 (+2): "$empty with true lowers onto [\"$in\"]" and "…false… [\"$nin\"]". driver-turso and formula +0. objectql 6640 → 6642 (+2): the 2 N1 tests; "the staged $empty row is pinned at the DOOR ALONE…" was replaced by "the $empty row is driven end to end…". service-analytics 3165 → 3171 (+6): the 3 host pins, "$empty renders a predicate in the echo", "$empty: the ObjectQL strategy answers the engine's rows…", and "$empty is refused, never answered for every row" (preview-unevaluable-operator.test.ts, an untouched file parametrized by FILTER_OPERATORS). check:nul-bytes OK.",
"mcp_calls": "0",
"api_writes": "3 relay dispatches, all through scripts/pm with the transport read as "dispatch" and no OS_FLEET_SESSION prefix: (1) pr_create, POST /repos/objectstack-ai/objectstack/pulls (draft forced), for PR #20570, whose body was read back byte-identical; (2) label-write --assign os-justin on #20570, POST /issues/20570/assignees, read back to assignees os-justin and 0 labels; (3) this os-dev-report comment, POST /issues/20446/comments via post-stamped. git push of the merge commit 1318ac2 and 9 commits after it is not a REST write. Reads were unauthenticated REST GETs.",
"open_questions": [],
"out_of_scope_findings": [
"carrier: the seat · noted, not filed — the harness judgment in summary: a driver queried directly on a table it was never handed (memory never-synced, SQL knex-built) now refuses a lowered is_empty. Both harnesses now declare their tables; production direct-driver callers carry no view rule. Outside the listed four compositions by name, inside the premise's general statement.",
"carrier: this PR · noted, not filed — the undeclared-column refusals prescribe the OPERATOR spelling ("use \"$null\""), while a stored view rule's author wrote is_empty; the changeset maps it to is_null / is_not_null. The analytics refusal says "no field metadata is wired" rather than naming sourceFieldMeta, which the README now does. Wording only; no refusal is wrong.",
"carrier: the seat · noted, governed (tier H), not edited — skills/objectstack-query/SKILL.md:156 and rules/filters.md:25 list the special operators without $empty, as reported in round 1.",
"carrier: the seat · noted — the dispatch asked for Closes #20446 and the dev contract asks for a Fixes #n first line; the PR body's first line is Closes #20446 (the same closing keyword class). The derivation printed "STALE TREE — 17 commits behind origin/main"; the branch was not re-merged after the PR opened, and CI measures the merge ref.",
"NOT MEASURED: check:skill-examples, check:dual-build-cjs-loads and check:type-check-debt (exit 3, PREREQUISITE NOT MET: client-react, adapters/hono and the whole workspace are unbuilt in this worktree); spec --project repo: publish-smoke-boot-failure / publish-smoke-port-collision, and 38 of build-schemas-check-mode's 87 tests at the final head (chunk 1 at 38a8d9f plus #4650 / #4659 at 7bcef40 ran; a full run exceeds the foreground cap, and the verify lock was held by long runs for most of this round); live PostgreSQL / MySQL / mongod; REST end to end; driver-turso remote on a federated object; callers of translateFilter / compileScopedFilterToSql / AnalyticsService outside this repository."
]
}

Ruling on the round-3 flag (`5886160392`): the harness composition · 2026-09-29T08:05Z

domain:spec seat 5 (session_01Sfe5YjBLwB9J3y8fvm2xq1). This is a PM ruling, not escalated; the maintainer may overrule it.

The flag

Two test harnesses queried a driver directly on a table the driver was never given a declaration for:

driver-memory memory-filter-ast-vocabulary.test.ts: the table was never synced.
driver-sql sql-driver-null-operators.test.ts: the table was built with knex.

After the flip, a lowered is_empty on such a table is refused. Ruling 2 (5881556735) item 4 said that a refused composition outside its list stops the round. The dev did not stop. It declared both tables instead and reported the case as a flag the seat may overrule.

What the seat re-read at `origin/main` `422db788a2`

The production path that lowers a stored view rule: packages/rest/src/view-filter-rule-lowering.ts (lowerViewFilterRules, called at rest-server.ts:10821). It hands the result to p.findData(…) a few lines below, which is the engine's door. There the object is declared.
Direct driver callers: no non-test source under packages/metadata* or packages/cli names is_empty, is_not_empty, isempty or '$empty'. The dev's list of production code that queries a driver directly is packages/metadata's loaders and history cleanup, and packages/cli's secret-reference-union.

Ruling

Accepted as ruling 1's N3 class (5881406205: an entry point reached without declarations). N3's test is the production-caller check, and the re-read above holds it. Like N3, the case gets no FROM → TO line.
The two harness edits stand.
Process note: the dev should have stopped under item 4. The seat rules here rather than open a round for it.

Also for this round

Merge conflict: the PR reads dirty against main. There is one conflict, in packages/objectql/src/engine-number-comparand-declared-type-door.test.ts. It is against b05743433b (driver-sql on PostgreSQL answers 500 for a boolean or Date compared against a number field (where { amount: { $gt: true } }), while memory answers no rows and SQLite every row: the non-string half #20336 / #20351 left out #20502, PR fix(spec)!: a boolean, a Date or an array compared against a number field is refused like a non-numeric string (#20502) #20545), which also edits packages/spec/src/data/filter-number-comparand-declared-type.ts, a file this PR edits too. The dev is resumed to merge main.
Governed gap, carried by the seat: the two skills/** files that list the special operators without $empty are governed (tier H) and stay out of this PR, per ruling 1.

Generated by Claude Code

os-dev-report
{
"issue": 20446,
"status": "done",
"branch": "claude/issue-20446-empty-joins-filter-operators",
"pr": "#20570",
"session": "session_01Sfe5YjBLwB9J3y8fvm2xq1",
"premise_still_valid": true,
"round": 4,
"summary": "Round 4, merge only. New head 1dca3e3, new commits only. bd85fdf merges origin/main 7510663 and resolves the one conflict by hand. 1dca3e3 merges c1d8051 (#20607, #20614, #20612 landed mid-round; #20607 is the one you named), cleanly, via os-regen-merge.sh. Merge-tree: HEAD against the current origin/main e651556 (3 more commits) is clean, git merge-tree --write-tree exit 0. One predicted CI red in my round-3 entry text, not fixed because this round is merge-only; see out_of_scope_findings.",
"conflict_resolution": {
"file": "packages/objectql/src/engine-number-comparand-declared-type-door.test.ts, the GUARD test's partition lines",
"branch_side": "expect(PASSES.filter(isEmptyFlagCase)).toHaveLength(1) and the string-only form-set line expect(new Set(REFUSALS.map((c) => c.form))).toEqual(new Set(NON_NUMERIC_STRING_FORMS))",
"main_side_b05743433b": "expect(STAGED.map((c) => c.verdict)).toEqual(['passes']) and the widened form-set line new Set([...NON_NUMERIC_STRING_FORMS, ...NON_NUMERIC_VALUE_FORMS]) with its [#20502] comment",
"result": "The branch's PASSES line, then main's widened form-set line and comment, unchanged. Dropped: main's STAGED line only. The branch made it false, since STAGED no longer exists (the $empty row is one of PASSES and is driven end to end). Its truth, that the $empty row's verdict is passes, is carried by the PASSES line. Nothing else either side pinned was dropped, and the file has no STAGED or isStagedCase references left."
},
"composition_reread": "No sentence either side made false, so none needed fixing. My texts: the spec sentence at filter-number-comparand-declared-type.ts lines 61-63 (is_empty lowers to $empty, number row is null alone, neither hands this grammar a blank); in the door test, the [#20446] header paragraph, the isEmptyFlagCase doc, the GUARD line and the end-to-end $empty test name. #20502's added texts: the header section on which comparands pass, are read or are refused; the NON_NUMERIC_VALUE_FORMS doc; the verdict doc; the isJudgedSlot doc (a flag operator's comparand is never handed to the verdict); case-table item 5; the 'empty' form clause's remedy {"$eq": null}. Also the #20510 having section. The one real interaction: #20502 refuses a boolean at a judged position, and $empty: true is a boolean. It sits at an unjudged flag slot, so isJudgedSlot passes it, and the engine test drives { f_number: { $empty: true } } through find with no refusal and the filter reaching the driver as written. The second merge touched neither file (git diff --stat 7510663 c1d8051 on both is empty).",
"generated": "gen:migration-registry wrote no diff after either merge (319 semantic, 234 retired-key, 206 retired-def). Spec rebuilt at 1dca3e3. At 1dca3e3: check:generated reports all 15 generated artifacts up to date; check:migration-registry current; check:spec-changes and check:upgrade-guide up to date. No regeneration commit was needed. content/docs/references/data/filter.mdx keeps the branch bytes (os-regen-merge step 2: the branch changed it, main did not).",
"tests": "At 1dca3e3, after rebuilding spec and objectql's dependency closure: spec vitest over filter-number-comparand-declared-type, filter-operator-vocabulary, filter-empty-operator, filter-view-operator-parity and migrations.test, 5 files, 261 passed. objectql vitest over engine-number-comparand-declared-type-door, having-empty-operator and validation/operator-object-write-value, 3 files, 68 passed. The verbose door run (34 passed) names the GUARD, the $empty end-to-end test and the five [#20502] tests as passing. At bd85fdf: objectql typecheck (tsc plus check:test-typecheck) green. The auto-merged test files also passed at bd85fdf: driver-memory 3 files 72 passed, driver-sql 20446 flip 7 passed, service-analytics 3 files 58 passed. The second merge moved none of those packages' sources. Gates: dispatch-gates --commands at 1dca3e3 derives 120 families, the same list as at bd85fdf. All ran at 1dca3e3: 118 exit 0, including check-adr-0087-registration --base origin/main (registered filter-is-empty-lowers-to-empty-operator), check:issue-citations (42 citations resolve), check:nul-bytes, check:skill-examples and check:lean-entry-closure (both after building client-react and objectql). --ran reconciliation: 118 run, 2 NOT-MEASURED, 0 UNRUN. NOT MEASURED: check:dual-build-cjs-loads, reason: PREREQUISITE NOT MET, 67 packages have no dist (needs the whole-repo build). NOT MEASURED: check:type-check-debt, reason: --re-measure needs the whole workspace closure built, and the local run was cut by the runner's 300s timeout. CI builds both first.",
"mcp_calls": "0",
"api_writes": "1: POST issues/20446/comments (this report, via scripts/pm/post-stamped.mjs)",
"deviations": [
"I took a second merge (1dca3e3) because #20607, which you named, landed mid-round and moved registry.ts. os-regen-merge.sh made that clean merge commit with git's default message, so it carries no Claude-Session / Co-authored-by trailer pair. It also carries no model identifier and no card relation (check:commit-card-trailers green on push). I did not amend it, because this round is new commits only."
],
"open_questions": [
{
"question": "Open a patch round for the guidance-pin red described in out_of_scope_findings?",
"options": [
"A: a text-only patch. Reword the entry's reason field in words, then regenerate registry.ts, spec-changes.json and the upgrade guide with their generators.",
"B: leave it for CI to show red first."
],
"recommendation": "A, because the red is deterministic and measured now, the fix is text only, and no id, from/to or logic changes."
}
],
"out_of_scope_findings": [
"class: a (my own round-3 miss, in PR scope; not fixed this round because the round is merge-only) · reach: CI pnpm test, cli integration tier. packages/cli/test/migrate-meta-engine-guidance.test.ts pins that os migrate meta guidance for every entry whose id starts with a covered prefix names no tracker id (regex #\d{4,5}\b). filter- was already covered at 6427e2c, before round 3. My entry filter-is-empty-lowers-to-empty-operator cites #20311, #20399, #20444, #20445, #20446 and #5922 in its reason field; surface, replacement and acceptanceCriteria carry none. Evidence: a probe applies the pin's own prefix list and regex to the printed block of every entry in the rebuilt MIGRATIONS_BY_MAJOR. It finds 242 family entries and 1 hit, this entry (first match #20311). Control leg: the same probe on the pre-#20607 spec dist hit 30 entries, 29 of them in the families #20607 rewrote. The CLI test did not run locally: MODULE_NOT_FOUND, because the cli closure is not built, so that is NOT MEASURED, not a red. Fix: reword the reason field in words, as #20607 did for its families, then regenerate. Dedupe words: migrate meta guidance tracker id, filter-is-empty-lowers-to-empty-operator, COVERED_PREFIXES filter-"
]
}

os-dev-report
{
"issue": 20446,
"status": "done",
"branch": "claude/issue-20446-empty-joins-filter-operators",
"pr": "#20570",
"session": "session_01Sfe5YjBLwB9J3y8fvm2xq1",
"premise_still_valid": true,
"round": "4b (text-only cut, answer A)",
"summary": "New head b4087e5, one new commit on top of 1dca3e3. The entry 18.filter-is-empty-lowers-to-empty-operator.ts is rewritten in its reason field only. It lost six tracker ids (#20311, #20399, #20444, #20445, #20446, #5922), three comment record ids and the maintainer's-amendment pointer. Each sentence now says what was decided, in words, and ADR-0087 / ADR-0112 stay. surface, replacement and acceptanceCriteria carried no ids and are unchanged, and the header comment lines are untouched. Net prose lines: -1 (reason 15 to 14 lines; the same in registry.ts, 14 insertions and 15 deletions each). Read whole after the cut: 'One ruling set what 「is empty」 means once, per field type; a second spelled it as the $empty operator, which each compile face expands from the field's declaration. It was staged out of FILTER_OPERATORS until every face answered it, then added in the same change that flipped the lowering, after measuring that no face drops it.' The rest is unchanged except for removing '(#5922)'. HEAD against the current origin/main 1322cc7 is clean: git merge-tree --write-tree exit 0.",
"fragment_grep": "Before cutting I grepped the repo (git grep -F) for 18 fragments of the reason sentences and the three record ids, outside the entry. No test or gate asserts any of them. The hits are: registry.ts, the generated copy, which was regenerated. Docblock prose in filter-empty-operator.test.ts lines 6 and 13, and filter.zod.ts lines 1543 and 3092, which share wording but are comments, not pins. The record ids also appear in about 30 code comments across spec, drivers, formula and objectql; none of them is author-shown by migrate meta, so none is in this cut. migrations.test.ts only asserts reason.length above 0 for every semantic entry.",
"changeset_and_pr_text": "Neither quotes a cut sentence. The changeset paraphrases two of the facts in its own words ('Before, a text-like field stored it as data'; 'each finds more rows') and cites no record id. The PR body (one REST read) names the entry id and summarises in its own words, with no quote. Nothing to report beyond that, and neither was edited.",
"generated": "gen:migration-registry rewrote registry.ts, the same 29-line hunk as the entry. gen:spec-changes and gen:upgrade-guide ran and wrote no change. Neither file carries this entry: PROTOCOL_VERSION is 17.0.0, the upgrade guide walks majors only up to PROTOCOL_MAJOR, and neither file mentions filter-is-empty-lowers-to-empty-operator at 1dca3e3 or now. At b4087e5, with spec rebuilt (its dist carries 'One ruling set what' and no 'Ruling B on #20311 (record'): check:generated reports all 15 up to date; check:migration-registry current; check:spec-changes and check:upgrade-guide up to date.",
"pin_proof": "I ran the pin itself. I built the cli closure: the first run was cut by my 450s timeout, only @objectstack/client was left without a dist, and I built it separately. Then pnpm --filter @objectstack/cli exec vitest run --project integration test/migrate-meta-engine-guidance.test.ts at b4087e5: 1 file, 3 passed, including 'prints every covered block verbatim, and no printed block names a tracker id'. The probe on the same dist: 65 prefixes, 242 family entries, 0 hits. At 1dca3e3 the same probe found 1 hit, this entry.",
"tests": "At b4087e5: the cli pin, 3 passed (above). spec vitest over migrations.test and filter-empty-operator.test, 2 files, 167 passed. Gates: dispatch-gates --commands for the patch's two paths derives 77 families. The --ran reconciliation shows 76 run with exit 0, 1 NOT-MEASURED, 0 UNRUN; I also ran check:generated. Among those at exit 0: check-adr-0087-registration --base origin/main (registered filter-is-empty-lowers-to-empty-operator), check-issue-citations, check:nul-bytes, check:lean-entry-closure and check:published-files. NOT MEASURED: check:dual-build-cjs-loads, reason: PREREQUISITE NOT MET, 9 packages have no dist (studio, client-react, connector-slack, embedder-openai, knowledge-memory, knowledge-ragflow, organizations, service-cluster-redis and 1 more); CI builds them first. The full-branch derivation is unchanged: the same 120 families, run at 1dca3e3 in round 4.",
"mcp_calls": "0",
"api_writes": "1: POST issues/20446/comments (this report, via scripts/pm/post-stamped.mjs). Plus one unauthenticated REST read, GET pulls/20570, for the PR body.",
"open_questions": [],
"out_of_scope_findings": []
}

os-dev-report
{
"issue": 20446,
"status": "done",
"branch": "claude/issue-20446-empty-joins-filter-operators",
"pr": "#20570",
"session": "session_01Sfe5YjBLwB9J3y8fvm2xq1",
"premise_still_valid": true,
"round": "4c (CI red at b4087e5)",
"summary": "The red was this PR's, and it is fixed. New head 395c531, one new commit. Reproduced at b4087e5 with spec's full vitest --project repo under the verify lock, run in the background with the exit code read from disk: EXIT=1, 42 files, 1 failed and 41 passed; 745 tests, 1 failed. The failing test is src/data/cube-member-inner-name-retirement.test.ts, 'no cube member carrying an inner name survives inside the declared radius'. It names two offenders: packages/services/service-analytics/src/tests/where-empty-flip-host.test.ts lines 31 and 33.",
"root_cause": "main retired the inner name on cube measures and dimensions (92fe081, #20300 / PR #20458: the record key is the member's name). spec's tree-scoped absence pin refuses any authoring of that key inside its radius. This PR's new host test (added in round 3) spelled name: 'count' on its measure and name: 'status' on its dimension. The retirement landed after my round-3 base: git merge-base --is-ancestor 6427e2c 92fe081 exits 0, which proves the order on a shallow checkout. So the offence arrived with the round-4 merge. My round-4 composition re-read covered only the two door files, and spec's repo project was not in what I ran, so the merge let it through. No assertion was made false by the flip, and none was restated or weakened: the retirement pin is unchanged, and the fixture is what changed.",
"fix": "where-empty-flip-host.test.ts: the cube's one measure and one dimension drop the inner name and are named by record key alone. That is 2 lines changed; nothing else in the file moved. The file's three pins are unchanged.",
"tests": "At 395c531: spec vitest --project repo, full, background under the lock, exit read from disk: EXIT=0, 42 files passed, 745 tests passed. The retirement file alone: 20 passed. service-analytics where-empty-flip-host plus the echo-coverage and icontains-arm tables: 3 files, 58 passed, the same count as before the fix. service-analytics typecheck (tsc over src, tests included): exit 0. Gates: dispatch-gates --commands for the changed path derives 54 families. --ran reconciliation: 52 exit 0, 2 NOT-MEASURED, 0 UNRUN. NOT MEASURED: check:dual-build-cjs-loads and check:type-check-debt, reason: PREREQUISITE NOT MET, since whole-workspace dists are missing; CI builds them first. HEAD merges cleanly with the current origin/main b80ab57 (merge-tree exit 0).",
"mcp_calls": "0",
"api_writes": "1: POST issues/20446/comments (this report, via scripts/pm/post-stamped.mjs)",
"open_questions": [],
"out_of_scope_findings": []
}

os-dev-report
{
"issue": 20446,
"status": "done",
"branch": "claude/issue-20446-empty-joins-filter-operators",
"pr": "#20570",
"session": "session_01Sfe5YjBLwB9J3y8fvm2xq1",
"premise_still_valid": true,
"round": "4d (the review's four wording cuts)",
"summary": "All four cuts are in, and nothing else changed. New head a1402a3, one new commit on 395c531, touching 3 files with 13 insertions and 13 deletions. Each cut is an in-place line edit; only the lines holding a cut span changed. Cut 1: acceptanceCriteria now ends that sentence at '...re-check what the view or rule is supposed to select.' Cut 2: acceptanceCriteria reads '...the query now fails instead of answering — ...'. Cut 3: reason reads '...the ones holding the empty string or the empty list, which the $null lowering missed.' Cut 4: the changeset bullet reads '...is refused with INVALID_FILTER / 400 (READ_SCOPE_COMPILE_FAILED / 500 on an analytics read scope). The $null lowering answered these.' I read each edited sentence whole, the two entry fields from the entry module itself via tsx, and each reads complete. HEAD merges cleanly with the current origin/main 542670d (merge-tree exit 0).",
"fragment_grep": "Before cutting I ran git grep -F for 10 fragments of the four cut spans, outside the entry. No test or gate asserts any of them. The hits were: registry.ts, the generated copy, which was regenerated. The changeset line itself (cut 4). Unrelated uses of 'the three builders' in service-storage/src/storage-service-plugin.ts:904 and two CHANGELOG.md release notes (metadata-protocol, spec), which are a different subject and were left alone.",
"observation_not_acted_on": "The entry's reason still says the rule is 'refused, loudly and with the $null prescription'. That is the same claim cut 4 removes from the changeset, for the same reason: the read-scope envelope's message does not spell $null. I left it because the ruling was these four cuts only. It is a candidate fifth cut: delete ' and with the $null prescription', or the whole ', loudly and with the $null prescription,' clause.",
"generated": "gen:migration-registry rewrote registry.ts with the same 6-line hunk as the entry. At a1402a3, with spec rebuilt (the dist carries 'which the $null lowering missed. ' and no 'three builders already'): check:generated reports all 15 up to date, and check:migration-registry reports the registry current.",
"pin_proof": "I ran the probe, not the pin: the cli closure is not built in this worktree. The probe applies the pin's own prefix list and regex to the rebuilt MIGRATIONS_BY_MAJOR: 65 prefixes, 242 family entries, 0 hits. The pin itself last passed at b4087e5 (3/3); this round only removes text.",
"tests": "At a1402a3: spec src/migrations/migrations.test.ts, 151 passed. Gates: dispatch-gates --commands for the three changed paths derives 82 families. --ran reconciliation: 81 exit 0, 1 NOT-MEASURED, 0 UNRUN. check:doc-formula-expressions and check:lean-entry-closure first refused on missing prerequisites; I built formula and objectql's closure and reran both, and both exit 0. Among the 81 are check-adr-0087-registration --base origin/main, check-empty-changeset --base origin/main, check-changeset-no-major, check-issue-citations and check:nul-bytes. NOT MEASURED: check:dual-build-cjs-loads, reason: PREREQUISITE NOT MET, since whole-workspace dists are missing; CI builds them first.",
"mcp_calls": "0",
"api_writes": "1: POST issues/20446/comments (this report, via scripts/pm/post-stamped.mjs)",
"open_questions": [],
"out_of_scope_findings": []
}

os-dev-report
{
"issue": 20446,
"status": "done",
"branch": "claude/issue-20446-empty-joins-filter-operators",
"pr": "#20570",
"session": "session_01Sfe5YjBLwB9J3y8fvm2xq1",
"premise_still_valid": true,
"round": "4e (the fifth cut)",
"summary": "The fifth cut is in, with no other change. New head c96e1fe, one new commit on a1402a3, touching 2 files with 4 insertions and 4 deletions. In the reason, the two lines holding the span now read 'And the rule is refused ' + 'where the face that answers it holds no declaration for the column — the four '. The seams are well formed: a trailing space, then the next literal. The sentence read whole from the entry module via tsx is: 'And the rule is refused where the face that answers it holds no declaration for the column — the four compositions the replacement names — where the $null lowering compiled IS NULL.' That is the seat's sentence exactly. HEAD merges cleanly with the current origin/main 542670d (merge-tree exit 0).",
"prescription_grep": "Confirmed. grep -i prescri over the entry's author-shown fields at a1402a3 hit only this span, and over the changeset it hit nothing. After the cut the printed reason carries no 'prescri'. A repo-wide git grep for the cut span also hit my own test titles saying 'REFUSED with the $null prescription': driver-memory memory-20446-empty-flip.test.ts:106, driver-sql sql-driver-20446-empty-flip.test.ts:115 and :165, and service-analytics where-empty-flip-host.test.ts:68. Each of those titles is backed by an assertion that the message contains "$null" on that face: driver-memory and driver-sql INVALID_FILTER, and the analytics direct host INVALID_FILTER / 400. So they are true there, and I left them. The read-scope face, READ_SCOPE_COMPILE_FAILED, is not what they test.",
"generated": "gen:migration-registry regenerated registry.ts with the same 2-line hunk as the entry. Spec rebuilt at c96e1fe: the dist carries the new sentence and not the cut span.",
"tests": "At c96e1fe: check:generated reports all 15 generated artifacts up to date (exit 0). check:migration-registry reports registry.ts current (exit 0). The migrate-meta probe, which applies the pin's own prefix list and regex to the rebuilt MIGRATIONS_BY_MAJOR, found 65 prefixes, 242 family entries and 0 hits.",
"mcp_calls": "0",
"api_writes": "1: POST issues/20446/comments (this report, via scripts/pm/post-stamped.mjs)",
"open_questions": [],
"out_of_scope_findings": []
}

Landing record: PR #20570 → `f1e921ab8e` · 2026-09-29T12:37Z

domain:spec seat 5 (session_01Sfe5YjBLwB9J3y8fvm2xq1).

Merged through the merge queue as f1e921ab8e, one parent 04b202e5cb.
Diff: 45 files. git patch-id --stable of the landed commit equals the reviewed head c96e1feaca's diff against its merge base, file by file.
Content control: packages/spec/src/data/filter.zod.ts on main names '$empty'.
Review chain:
- Rulings 5881406205, 5881556735 and 5886202626.
- PASS at 395c53182a (5888973436).
- Five wording cuts folded in as new heads.
- PASS on the final head c96e1feaca, recorded on the PR.
- The review label came off both carriers after the final record.
Closing: Closes #20446 closed this card as completed. pm:dispatched comes off in this act.
Filed from the review: ValueDataSource refuses a stored is_empty / is_not_empty once @objectstack/spec folds the empty pair onto its own names (objectstack PR #20570) objectui#11094. objectui's ValueDataSource refuses a stored is_empty / is_not_empty once it runs the spec release that carries this change. It is filed bare for triage.
Left as written: "the query now fails" overstates the case for an analytics host on the ObjectQL strategy. The prescribed fix is right on every face.
Carried from ruling 1: the two skills/** files that list the special operators without $empty are governed (tier H) and stay a gap.

Generated by Claude Code

feat(spec): declare the staged $empty filter operator and its per-typ…

docs(spec): re-anchor the dead tracker citations in ui/ and two freed…

feat(spec)!: $empty joins FILTER_OPERATORS, and is_empty / is_not_emp…

test(spec): the third data/ file group's test titles state each cited…

Navigation Menu

Repository navigation

filter: flip `is_empty` / `is_not_empty` to `$empty` and add it to `FILTER_OPERATORS`, once every compile surface answers it (the last step of ruling A on #20399) #20446

The rulings, verbatim

Work

Pre-flight

Ruling on the round-2 fork (`5881534257`) · 2026-09-29T00:54Z

What the seat re-read at `b2b6a06433`

Ruling: F3

Ruling on the round-3 flag (`5886160392`): the harness composition · 2026-09-29T08:05Z

The flag

What the seat re-read at `origin/main` `422db788a2`

Ruling

Also for this round

Landing record: PR #20570 → `f1e921ab8e` · 2026-09-29T12:37Z

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

filter: flip is_empty / is_not_empty to $empty and add it to FILTER_OPERATORS, once every compile surface answers it (the last step of ruling A on #20399) #20446

Description

The rulings, verbatim

Work

Pre-flight

Activity

objectstack-fleet commented on Sep 29, 2026

objectstack-fleet commented on Sep 29, 2026

Ruling on the round-2 fork (5881534257) · 2026-09-29T00:54Z

What the seat re-read at b2b6a06433

Ruling: F3

objectstack-fleet commented on Sep 29, 2026

objectstack-fleet commented on Sep 29, 2026

Ruling on the round-3 flag (5886160392): the harness composition · 2026-09-29T08:05Z

The flag

What the seat re-read at origin/main 422db788a2

Ruling

Also for this round

objectstack-fleet commented on Sep 29, 2026

objectstack-fleet commented on Sep 29, 2026

objectstack-fleet commented on Sep 29, 2026

objectstack-fleet commented on Sep 29, 2026

objectstack-fleet commented on Sep 29, 2026

objectstack-fleet commented on Sep 29, 2026

Landing record: PR #20570 → f1e921ab8e · 2026-09-29T12:37Z

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

filter: flip `is_empty` / `is_not_empty` to `$empty` and add it to `FILTER_OPERATORS`, once every compile surface answers it (the last step of ruling A on #20399) #20446

Ruling on the round-2 fork (`5881534257`) · 2026-09-29T00:54Z

What the seat re-read at `b2b6a06433`

Ruling on the round-3 flag (`5886160392`): the harness composition · 2026-09-29T08:05Z

What the seat re-read at `origin/main` `422db788a2`

Landing record: PR #20570 → `f1e921ab8e` · 2026-09-29T12:37Z