Introduction
jevlish brings Jev judgments into ordinary TypeScript business logic. Use given to judge one value and from to filter or rank a collection.
The official Jev SDK is shaped like an LLM SDK: build a request, send it, and read the response. That is useful when the response goes to a person. In application logic, the response usually decides what code does with a value it already has—whether a ticket escalates, which rows a query keeps, or who gets assigned.
jevlish expresses those operations as conditions, filters, rankings, and choices. Exact checks remain TypeScript functions. Semantic checks remain plain-language Jev questions.
- given,- from, and the question builders create a lazy expression. Building it sends nothing.
- .plan()shows the state and questions that would leave the process.
- awaitor- .run()folds code predicates, compiles the remaining Noul, Score, and Choice questions, and asks Jev.
- The acceptance policy turns model probabilities and confidences into decidedoruncertainjudgments.
- The result retains the requests, answers, local predicate outcomes, usage, cache status, and policy as evidence.
means(...) defines a reusable Noul question with an explicit boundary. given(ticket) supplies the subject. .seenAs(...) controls what leaves the process; predicates and handlers still receive the complete Ticket.
The branch has three outcomes. do handles true, otherwise handles false, and whenUncertain handles an answer that did not meet the policy. A false code predicate under and settles the condition locally, so a closed ticket sends no request.
- A string condition or means(...)compiles to a Jev Noul question.
- A scalecompiles to a Score question.
- chooseFromcompiles to a Choice question and maps the answer back to one of your objects.
- asksends related Noul, Score, and Choice questions about one subject together.
- A Sense is a configured set of given,from, andgradeverbs bound to one runtime.
Jevlish uses the TypeSafe/Jev SDK. That is why the environment variable is TYPESAFE_API_KEY and the default transport is TypeSafeClient.
- Install and configure gets a key into the process and explains the shared Sense.
- Quickstart builds one decision and one ranked query line by line.
- Support desk runs the same domain as a complete pipeline.
- The guides cover each verb in turn, starting with Judging one thing.
- The Reference is generated from the root package entry point. Advanced subpath APIs are introduced in the Runtime, Testing, and Running guides.