Small decisions. Interesting possibilities.Submit contentSubmit

How it uses Jev

The PostgreSQL extension sends row batches in a shared state with one yes/no Noul question per row, then exposes judgments as SQL predicates, probabilities, Choice results, or Score values.

What Jev decides

Support ticket teamExample answers · not a recorded Jev response · Source ↗
Question 1 · r0
YOUR APP
INSTRUCTION

For this record: which team should handle this?

STATE

A support-ticket row is included in the rows batch; Jev receives the row fields and the query as shared state.

JEV · CHOICE
  1. billing
  2. technical
  3. sales

App workflow

  1. Write a SQL expression

    Use `jev`, `jev_prob`, `jev_choice`, or `jev_score` with a row and plain-language condition or rubric.

  2. Read ahead and batch rows

    Stream eligible table rows and group them into shared Jev requests with one question per row.

  3. Return typed row results

    Map returned judgments to booleans, probabilities, labels, scores, or full JSON results.

  4. Compose with PostgreSQL

    Filter, order, group, join, and limit using the resulting SQL values.

Why it is interesting

It makes semantic row filtering and classification composable with normal SQL operations, while batching, read-ahead, caching, and concurrency handle query execution.