Route a support request
Send each message to the right handler, with an explicit fallback.
Which support team should handle this message? Choose other when the request does not fit a listed team.
THE JEV DECISION LIBRARY
Find a use case. Copy the prompt and code.
Put Jev to work in your application.
Send each message to the right handler, with an explicit fallback.
Which support team should handle this message? Choose other when the request does not fit a listed team.
Separate a predicted label from the decision to act on it.
What action is the customer asking for? Choose unclear if the message does not establish a specific action.
Find changes worth a closer human review before inspecting every line.
Does file.patch directly support that this change likely introduces incorrect runtime behavior?
Combine specific quality judgments with weights you control.
How usable are this report’s reproduction steps?
Ask whether an older tool call and its full output still matter to the current task.
Tool call t1 (read_file) should stay in the history: knowing this call was made, with its input, still matters for what the assistant does next
Turn an urgency question into a measurable signal for your response queue.
Does this ticket need a response today?
Identify functions whose names and contracts hide observable changes.
Does this function change observable state in a way that is not apparent from its name or supplied contract?
Screen out conversational turns before selecting from a tool catalog.
Does answering this turn require calling a tool at all?
Ask independent questions about one document without resending the context.
Does this release note describe a change that can break an existing integration?
Contribute one decision, its input, and what you learned.