Jev in production › SQL and data pipelines
DuckDB extension whose jev_choice, jev_score, jev_noul and jev_ask SQL functions send each row's text to Jev with constant criteria and return a typed column: an ENUM, a DOUBLE score or probability, or a STRUCT.

Ask a question about every row of a table, in SQL, and get a real SQL type back. A DuckDB extension over Jev, TypeSafe's model for typed answers instead of text.
The data you want to ask about already sits in a table or a Parquet file, and SQL is the query language everyone has. So ask the question where the data is, instead of pulling it out, wrapping an API in a script and writing the answer back.
Jev picks from a set you define instead of writing an answer you then check. The result is typed by construction, not by validation, and not generating is what makes it cheap enough to run on every row.
For the project's own README, linking back here: