Jev returns structured judgments that an application can inspect. is-jodd uses one of those judgments to ask whether an integer is odd.
Jev is TypeSafe’s model for turning supplied context into typed judgments. You give it information and a question with a defined answer shape. Your application receives a value it can inspect, rather than a conversational explanation. TypeSafe calls this approach System One. This is an independent explanation from the publisher of is-jodd, not official TypeSafe documentation. TypeSafe introduction
Start with the decision your program needs
Imagine an application reviewing incoming messages. One part of the program needs to know whether a message asks to reschedule an appointment. Another needs a category such as scheduling, billing, or something else. Those are different decisions, even though they concern the same message.
The useful design exercise is to write the receiving code first. Will it branch on a yes/no answer, select one route, or rank something along a rubric? A precise receiving interface makes it easier to notice when the proposed question actually contains several unrelated requirements. It also gives you something concrete to test before connecting any model.
Understand the three pieces
The input is called the state. The questions describe what should be judged. The answers preserve the question identifiers, so the application can find each result. TypeSafe documents Noul for yes/no judgments, Choice for selecting an option, and Score for a rubric. Question primitives
Here is an original planning example, not a recorded API result:
State: a visitor's appointment message
Question: does the visitor request a different date?
Application action: offer the rescheduling screen
Fallback: leave the existing appointment unchanged
Notice that the proposed action is deliberately limited. Recognizing a request and actually changing an appointment are separate responsibilities. The surrounding application should still check the appointment identifier, authorization, and available dates.
Where is-jodd fits
is-jodd is a joke package that sends a safe integer to Jev and asks whether it is odd. Its implementation converts a Noul value above 0.5 into true. It demonstrates a small asynchronous interface, but mathematical parity already has an exact local solution: n % 2 !== 0 for a validated safe integer.
That mismatch is the joke. The interesting engineering questions concern request design, error handling, and honest measurement, not whether a remote model is necessary to recognize the number three. The package also has a restrictive custom JODD-1T license requiring $1 trillion and written permission before use unless separate terms are granted.
Read the API quickstart to examine the request shape, or use the parity calculator when you simply need an answer. Our benchmark article explains what we measured without turning one experiment into a performance promise.