You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Filing gate: ③ a maintainer-directed task, and a ④ child of #5930. The maintainer's words, verbatim: 「5930 v18 启动」. They rule the order of work in ruling 5902355785 on #5930: "(4) per-face deletions, one card per lane, queued as each seam lands, ⛔ no open tail".
Reader: the domain:engine execution seat 1 (session_01DEvba2nBuD4tWzfq8r8NFY, os-support-ai), which claims it once it is queued. It filed this card at the fire after step 2 landed, as that landing record said. ⛔ Filed bare: routing and grading belong to triage. ⛔ Not a claim.
Why now
Step 2 (#5930, PR #20794, cfa931535) put lowerFilterCondition in @objectstack/spec/data. It runs once at every engine filter position, after the doors and token resolution, and at the RLS compile seam. The engine-fed faces now receive the lowered filter. Each still carries its own copy of the meaning the lowering already applied, "until its deletion card" (landing record on #5930). This is this lane's deletion card.
Direct callers are measured first (review 5903065983, open question 2: "one grep and one probe per step-4 card, no gate"). A caller that reaches the face without passing a seam, such as F7's explain engine or a direct driver call, is named with its answer before and after.
Under ruling D4 (b), such a caller is routed through the seam: "drivers receive the seams' lowered input; no permanent local guards on faces that bypass a seam".
If routing it changes an answer, that face stops and is reported.
The face's existing suites stay green before and after the deletion, with an ablation (design §S5).
⛔ No open tail: the card closes when every face above is deleted or reported. It may land as several PRs (one per face or per group, Part of #N until the last).
Recorded gaps (from the ruling): a live remote Turso server and a real mongod were not measured by the design.
Dedupe
mcp__github__search_issues, repo-scoped, open and closed, in the act that filed this card:
Filing gate: ③ a maintainer-directed task, and a ④ child of #5930. The maintainer's words, verbatim: 「5930 v18 启动」. They rule the order of work in ruling 5902355785 on #5930: "(4) per-face deletions, one card per lane, queued as each seam lands, ⛔ no open tail".
Reader: the
domain:engineexecution seat 1 (session_01DEvba2nBuD4tWzfq8r8NFY,os-support-ai), which claims it once it is queued. It filed this card at the fire after step 2 landed, as that landing record said. ⛔ Filed bare: routing and grading belong to triage. ⛔ Not a claim.Why now
Step 2 (#5930, PR #20794,
cfa931535) putlowerFilterConditionin@objectstack/spec/data. It runs once at every engine filter position, after the doors and token resolution, and at the RLS compile seam. The engine-fed faces now receive the lowered filter. Each still carries its own copy of the meaning the lowering already applied, "until its deletion card" (landing record on #5930). This is this lane's deletion card.Not this card:
where/ preview door, the read scope) and the memory cube face's door, with the F5 / F11 output vocabulary #20810), and their deletion cards follow it;Scope (from the design's census,
docs/design/predicate-compilation-convergence.md§S5; re-measure first)driver-sqlassertDefinedComparands, thecalendarDay*Rewritecalls (5 sites)FILTER_LOGIC,FILTER_TEXT,TEMPORAL,FILTER_COMPARAND_TYPEon SQLite, plus the PostgreSQL / MySQL live matrixdriver-tursoremotetoRemoteFilter's$between/ whole-day arms (3 sites), the transport's polarity copy (69 lines)driver-memoryquerydriver-memoryreference matcherdriver-mongodbformulalteBound(2 sites)havingAcceptance, per face:
Part of #Nuntil the last).Recorded gaps (from the ruling): a live remote Turso server and a real
mongodwere not measured by the design.Dedupe
mcp__github__search_issues, repo-scoped, open and closed, in the act that filed this card:$emptyby the field's declared type (driver-sql and heirs, turso remote, driver-memory, driver-mongodb, formula, objectql having) — ruling A on #20399 #20444, [finding] driver-memory analytics: a cubewhere$ltebare day on a declareddatetimefield drops the rest of that day —comparandsForconverts to storage form before the whole-day rule runs #20661, [finding]$newith an array comparand splits across backends: driver-sql and driver-memory refuse (400), driver-mongodb answers, formula matches every row — and both shared faces pass it #19886, objectqlhavinganswers an array in the equality slot by JS coercion (having: { total: [5] }is true) — the one face ruling 乙 closes "for every driver at once" that no gate reaches #19974, driver-memory's reference matcher matches a NULL-VALUED row against a well-formed bounded$between— the live mingo path excludes it, so one package answers one filter two ways #13549 and others), none a deletion card.where/ preview door, the read scope) and the memory cube face's door, with the F5 / F11 output vocabulary #20810 (open) is step 3, the analytics seams. [finding] driver-memory analytics: MemoryAnalyticsService runs neither shared comparand door, so a cube where {d: undefined} answers the null rows instead of a 400 #20734 (open) is F5's door finding, in #5930 step 3: the shared filter lowering at the analytics seams (the analyticswhere/ preview door, the read scope) and the memory cube face's door, with the F5 / F11 output vocabulary #20810's scope. [finding] 仓内存在 5 个独立的过滤器→谓词编译器,每次语义裁决成本 ×5 —— 值得立「谓词编译收敛」调查程序(#5298 成本清单副产品) #5930 is the umbrella. None is step 4.Dedupe words:
5930 step 4 per-face deletion engine lane·delete hand-copied filter meaning lowered filter·retire driver-memory reference matcher D6Generated by Claude Code