Newjevsd-pg
A PostgreSQL extension and workspace provide natural-language SQL planning, semantic operators, reusable evidence, and reviewed query execution using Jev judgments.
Added to Jevfast
NewHow it uses Jev
Jev supplies typed semantic decisions while PostgreSQL performs exact joins, calculations and transactions. The source documents a native SQL example asking whether a message requests further action and shows a `noul` question with `action` key and `subject_column` binding. SQL then selects each source row alongside that decision. This request example is source-derived; it does not claim an observed answer.
What Jev decides
Illustrative native message-action judgmentExample answers · not a recorded Jev response · Source ↗
Question 1 · action
YOUR APP
INSTRUCTION
The message requests further action.
STATE
Each row from the supplied source SELECT provides the message `id` and `body`; the `body` column is passed as the semantic subject.
JEV · NOUL
YesNo
App workflow
- Select source rows
A source SQL query chooses exact message identifiers and bodies.
- Evaluate semantic question
`jev_native.scan` asks whether each message requests further action and returns source and decision data.
- Use SQL results
PostgreSQL selects, joins or aggregates returned decisions; uncertain and unevaluated states remain explicit.
Why it is interesting
It keeps uncertain semantic judgments distinct from exact database work and preserves UNKNOWN and NOT_EVALUATED instead of silently coercing them to false.