Task guide

Should I use Jev for my task?

Each page takes one common task, shows the verdict that jev-fit gives for a sample idea, and explains how to shape the task and where the traps are.

Verdict: Jev

• Should I use Jev for support ticket routing?Ticket routing is the standard Jev task: text in, one team out, high volume. How to write the options, and the trap with overlapping queues.
• Should I use Jev for sentiment and tone detection?Tone detection fits Jev well: one judgment per message, a probability out. Write score levels as situations, and watch for sarcasm.
• Should I use Jev for RAG relevance filtering?Jev can filter retrieved passages before your LLM reads them. It is a filter, not a replacement for retrieval. One passage per question.
• Should I use Jev to check shell command safety?Jev can sort an agent's shell commands into read-only, reversible and irreversible. It must sit behind a deny-list, never in front of it.
• Should I use Jev for log and CI failure triage?Jev can label a log event or a CI failure by cause. Counting and time windows stay in code. Send the error, not the whole log.
• Should I use Jev for resume screening?Jev can check a resume against written requirements, one at a time. It must not reject people. Keep a person in the decision.
• Should I use Jev for claim and citation verification?Jev can check if a source passage supports a claim. It cannot know if the claim is true. Give it the evidence and ask one claim at a time.

Verdict: Jev, with a review band

• Should I use Jev for spam and content moderation?Jev fits policy checks on user content when you write the policy down. Why definitions beat labels, and why you need a review queue.
• Should I use Jev to pick the next UI action?Jev can choose the next element to tap from an accessibility tree. The LLM sets the goal, Jev takes the step, and code keeps the history.

Verdict: plain code

• Should I use Jev for invoice totals and arithmetic?No. Sums, tax and totals belong in plain code. Jev can help next to the arithmetic, for example to match an invoice line to a purchase order.
• Should I use Jev for SLA deadlines and date checks?No. Deadlines, business hours and time zones are date arithmetic, and code does them exactly. Jev can classify the ticket that starts the clock.

Verdict: a reasoning LLM

• Should I use Jev to extract data from emails?Not alone. Jev returns choices, not text, so it cannot pull a name out of an email. It can pick the right candidate that your code found.
• Can Jev work with screenshots and images?No. Jev takes no image input today. Convert the screen to text first, or use a vision model. This task also broke our first rubric.
• Should I use Jev for summaries and writing?No. Jev never generates text. Use an LLM to write, and use Jev before and after it: to decide what needs a summary and to check the result.
• Should I use Jev for planning and scheduling?No. Plans need many dependent steps, and schedules need constraint solving. Jev makes single judgments. It can rank or label the inputs.

Verdicts produced by Jev. Text written by a person. How the tool works: the report.