NewAutoRAG Jev Decisions
An optional Jev tool gives a local document agent typed classification, routing, and scoring decisions while the caller keeps thresholds and execution policy.
Added to Jevfast
NewHow it uses Jev
AutoRAG can register an optional Jev tool for its document agent. The agent sends one state with typed Noul, Choice, or Score questions and receives structured verdicts with confidence and escalation details. The caller retains thresholds and decides how to act. The tool is disabled by default and omitted in remote P2P sessions.
What Jev decides
Documented payout triage exampleExample answers · not a recorded Jev response · Source ↗
Question 1 · is urgent
YOUR APP
INSTRUCTION
Does this convey urgency?
STATE
A customer says payouts have been failing for three days. This is the repository-owned tool example, not a captured AutoRAG run.
JEV · NOUL
YesNo
Question 2 · department
YOUR APP
INSTRUCTION
Which team should handle this? Billing handles payments, invoices, and refunds; technical handles bugs, outages, and integrations.
STATE
A customer says payouts have been failing for three days. This is the repository-owned tool example, not a captured AutoRAG run.
JEV · CHOICE
- billing
- technical
App workflow
- Enable the optional tool
A Jev section in user or workspace configuration enables tool registration. Remote P2P sessions omit it because state would leave the machine.
- Request a typed judgment
The host agent calls the registered tool with one state and one or more narrow questions; jev-use selects a backend and validates the response.
- Apply caller policy
The agent reads answers and confidence. Escalated verdicts return the step to the LLM; thresholds remain with the caller.
Why it is interesting
A document agent can use a small decision model for classification and ranking while its host retains execution policy. Configuration separates this paid external judgment tool from local document retrieval.