NJev Primitive

Jev Noul

Jev Noul answers a single yes/no question about a state. It is the binary gate of the Jev toolkit — use it when you need to check whether something passes a judgment that is hard to express as clean rules.

What Noul does

You define a yes/no question — for example, "Does this reply need human review?" You give Jev the input (the reply text, the context). Jev evaluates it and returns either yes or no.

The return value is a boolean. Your code branches on it directly: if yes, queue for review; if no, send automatically. No parsing, no probability threshold to calibrate.

When to use Noul

  • Human review gates. Should this output be reviewed before sending?
  • Escalation checks. Should this case be escalated to a senior team?
  • Approval gates. Should this action be approved automatically?
  • Safety checks. Does this content need to be flagged?
  • Completeness checks. Is this input sufficient to proceed?

When not to use Noul

  • More than two outcomes. If the answer has three or more options, use Choice or Score.
  • Deterministic rules. If you can express the check as code (amount > threshold), do that.
  • Open-ended questions. If the answer is not yes/no, Noul is the wrong shape.
  • Rating or ranking. Use Score for ordered scales.

Writing the criteria

A Noul decision needs clear criteria for what counts as "yes" and what counts as "no." Write these as part of your Decision Spec. The criteria should be specific enough to test — "yes if the reply contains uncertain claims or apologizes without resolving the issue" is better than "yes if the reply seems risky."

On low confidence: route to a qualitative fallback — human review, an LLM fallback, asking for more information, or doing nothing. Do not hard-code a confidence cutoff.

Example: needs human review?

An LLM drafts a reply to a customer. Before sending, you want to check whether a human should review it. Jev Noul reads the reply and returns yes or no.

Decision Spec (excerpt)Noul
{
  "type": "noul",
  "question": "Does this reply need human review?",
  "input": { reply_text: draft.body },
  "yes_criteria": [
    "Contains uncertain claims",
    "Apologizes without resolving",
    "Offers compensation without authority"
  ],
  "fallback": "yes → human review queue"
}

Noul in a Decision Spec

A Noul Decision Spec includes the question, the input fields, the criteria for "yes" and "no," and the fallback. Jev Fit + Builder generates this as editable JSON, so you can refine the criteria before generating code.

The code shape

TypeScript
const result = await jev.noul({
  question: "Does this reply need human review?",
  input: { reply_text: draft.body },
});

if (result.value) {
  queueForReview(draft);
} else {
  sendReply(draft);
}

Choice, Noul, or Score?

Try it on your workflow

Describe a review or gating task and the analyzer will identify Noul steps.

Analyze a review workflowWhen to use Jev
FAQ

Frequently asked questions

It's a Jev primitive that answers a single yes/no question about a state. It returns one binary decision.

Still have questions?

Contact support@jevmodel.co →