Clarity logo JEV / DECISIONS AT MACHINE SPEED
Recorded demo · no API callsSEPTEMBER 2026

01 / Meet the model

Intelligence
as a decision.

JEV reads application state and answers focused questions with typed outputs and probabilities. Your code keeps control of the workflow.

ChoiceNoulMany questions, one call

Press → or click Next to walk through the story.

J
STATE INTYPED ANSWERS OUTPROBABILITIES

02 / A familiar support workflow

One billing email.
Four LLM decisions.

Customer email“I was charged twice for September. Please refund the extra payment. When will it return to my card?”
01 / INPUT
✉

Ticket arrives

The email and support note enter the workflow.

02 / CHECK
?

Refund requested?

Answer: yes.

LLM CALL
03 / CLASSIFY
▦

Primary issue?

Answer: billing.

LLM CALL
04 / SCORE
◉

How urgent?

Routine; no stated deadline or blocker.

LLM CALL
05 / ASK
◈

What does policy say?

5–7 business days after issue.

LLM CALL

Code routes the billing ticket to billing support and gives the reply writer the policy answer. The refund itself has not been issued.

03 / Find the decision points

Choice. Route. Question.

The same customer email yields answers the support workflow can use.

01 / CHOICE▦

Classify

What is the primary issue?

billing · technical · scheduling · other
→ billing
02 / ROUTE↗

Choose the path

Use the category to select a queue; show urgency alongside it.

billing + routine → billing support
03 / QUESTION?

Check and ask

Was a refund requested? What timeframe does the note support?

yes · 5–7 business days after issue

04 / The same ticket with JEV

Four typed questions.
One JEV request.

Same customer email“I was charged twice for September. Please refund the extra payment. When will it return to my card?”
01 / INPUT
✉

Ticket + note

Same email and example support note.

02 / NOUL
?

Refund requested?

Probability of yes.

JEV
03 / CHOICE
▦

Primary issue?

Select billing.

JEV
04 / SCORE
◉

How urgent?

Position on three ordered levels.

JEV
05 / CHOICE
◈

Policy answer?

Select the supported timeframe.

JEV
Run this ticket through JEV

Noul, Choice, Score, and Choice evaluate independently in one request. Code maps billing to the billing support queue.

05 / Recorded comparison

Head to head: Noul.

One yes/no question. JEV returns P(yes); GLM 5.3 Flash returns a JSON boolean. Replay one measured local run.

01 / NOUL

06 / Recorded comparison

Head to head: classify.

One Choice question selects a label from a closed set. The LLM receives the same four options and returns JSON.

02 / CHOICE

07 / Recorded comparison

Head to head: ask.

For the duplicate-charge customer, ask what the example support note says. JEV and the LLM select from the same answer options.

03 / EVIDENCE + CHOICE

08 / Parallel illustration

15 requests. One race.

Fifteen example tickets illustrate concurrent classification. The animation does not measure time or cost.

15 + 15 ILLUSTRATION
JEV0 / 15 shown · illustration
GLM 5.3 Flash0 / 15 shown · illustration
#Support requestJEV · ChoiceGLM · JSON
#Support requestJEV · ChoiceGLM · JSON

Illustrative fan-out. No provider requests are sent by this public version.