The Where vocabulary and its lowering; the filter module retyped

[borisno2]

Parent

#1123 — build spec 3 of the Prisma 8 architecture spec. Lands on the prisma-8 integration branch, not main.

What to build

.where() and .orderBy() accept the closed Where vocabulary — equals, not, in, notIn, lt, lte, gt, gte, contains; AND/OR/NOT; some/every/none on any relation — lowered onto Prisma's lambda in one place, total or throwing including under sudo; contains is engine-escaped and case-insensitive; equals: null lowers to IS NULL; a relation predicate ANDs the related list's query access inside the EXISTS, denied meaning empty; orderBy is scalar-only. The filter module's condition type becomes a vocabulary value, query validation gains the operator check, and the count-filter marker, resolvers and label pass-through are deleted.

Acceptance criteria

• Each operator lowers and returns the expected rows on the Test context; contains: '50%' matches a literal percent sign
• An unknown key or operator throws a validation error naming the list and key, under sudo too
• A predicate naming a field the session cannot read throws identically to a nonexistent field
• some over a related list the session cannot query is false; none/every true
• The filter module imports nothing from the ORM; the deleted count-filter symbols are gone

Blocked by

• The opaque wrapper with all() and first(): operation access, the Access Filter as a filter entry, Silent failure #1146

---

Generated by Claude Code

[borisno2]

Carried forward from the code review of PR #1216 (issue #1146), 2026-09-06.

The equality-only lowerPredicate seam this ticket replaces has a non-total lowering: if (condition === undefined) continue. The Access Filter goes through the same seam, so an access rule spelled

({ session }) => ({ authorId: session?.userId })

lowers to {} for an anonymous caller and matches every row, while the explicit { equals: undefined } spelling of the same rule is refused. Two spellings, opposite behaviour — and the widening one is the idiomatic spelling.

This is Prisma-parity and pre-existing, so it was not fixed in #1216; the docblock there was corrected and a test pins the current behaviour of both spellings. This ticket's "total or throwing, sudo included" requirement is what closes it.

• The Where vocabulary lowering is total: an undefined condition is refused, not skipped, on both spellings
• The Access Filter cannot lower to a widening predicate
• The behaviour-pinning tests added in The opaque wrapper with all() and first(): operation access, the Access Filter as a filter entry, Silent failure #1216 are updated deliberately as part of this change

---

Generated by Claude Code