See the decision. Then call it.

Jev 1.13 Text state 3 of 8 decisions

This result is recorded. Editing the state and running sends a new request to Jev.

Two different problemsYes / No
What a cheap model would dropScore
Which modelChoice

Recorded Jev result

Which model

Strong · 99%

The cheap model is the default for one topic. This ticket has two.

Probability breakdown
Human1%Strong99%Balanced0%Fast0%

Two different problems

Yes · 92%

The ticket reports an SSO failure and a different invoice amount.

What a cheap model would drop

2.99 / 3

Filing this as only an access ticket drops the $600 gap.

Probability breakdown
Only a filename, and it can be renamed again.0%One label, and a person can see it the same day.0%Two files can disagree with each other.0%One of two disagreeing problems is dropped, or the task itself asks for a refund or an email.100%
Example notes

Use the strong model

This ticket is both an SSO outage and a $600 billing gap. A cheap one-topic route could drop one of them.

  • SSO has failed for 120 seats since Friday.
  • The invoice is $4,800 and the contract is $4,200.
  • The only tool on this route is queue.add.

Request

POST /api/v1/call

API Call the same request from your code.

MCP Use the same decision from Cursor, Claude Code, or Codex.

POST /api/v1/call

{
  "model": "typesafe/jev-1.13",
  "state": "Task: File this ticket. The cheap model is the default when a ticket has one topic.\n\nTicket, Wednesday 30 September 2026, from lena@northline.example:\n\"SSO has failed for 120 seats since Friday's Okta certificate rotation. Email login still works. The audit is Monday 5 October.\nInvoice 4419's PDF shows $4,800. The contract is $4,200.\"\n\nTools on this route: queue.add\nThere is no refund tool and no email tool.\nFiling this as only an access ticket drops the $600 gap before Monday.",
  "questions": {
    "conflict": {
      "type": "noul",
      "instructions": "Does the input contain two problems that are not the same job, such as an access failure and a different invoice amount?",
      "criteria": {
        "true": "It contains two problems that are not the same job.",
        "false": "It is one file change, one topic, or two files that must match, with no second disagreeing problem."
      }
    },
    "miss": {
      "type": "score",
      "instructions": "If the cheap model treats this as one simple step, what is lost?",
      "criteria": [
        "Only a filename, and it can be renamed again.",
        "One label, and a person can see it the same day.",
        "Two files can disagree with each other.",
        "One of two disagreeing problems is dropped, or the task itself asks for a refund or an email."
      ]
    },
    "route": {
      "type": "choice",
      "instructions": "Which model should handle this task?",
      "criteria": {
        "fast": "One already-specified file change, with no second problem in the input. The cheap model is enough.",
        "balanced": "Two named files must change together, and the input does not contain two problems that disagree.",
        "strong": "The input contains an access problem and a different money problem. Treating it as one topic would drop one of them. Do not use the cheap model.",
        "human": "The task asks for a refund or an email to be sent."
      }
    }
  }
}