jev-search

1# Searching with Jev
2 
3A research turn is usually three decisions and one piece of writing:
4 
5- which of the results to actually open (the other thirty are noise),
6- whether what has been read answers the question, or another round is needed,
7- which query to run next.
8 
9Those are picks and a yes/no. Jev answers them in about half a second for a fraction of a cent, and the expensive model is left to do the writing — which is the only part of this Jev cannot do. **Jev never writes a query.** You write the candidates; Jev picks one or says none of them would add anything.
10 
11`jev search` runs one round of that loop and hands back the decision. Use it instead of guessing, and instead of burning a frontier turn on "should I search again?".
12 
13## Do this
14 
151. Search the way you always do (`web_search`, an API, a site). Give it the question, and write two to five candidate queries for the next round if this one is not enough.
162. Run one round:
17 
18   ```bash
19   echo '{"question":"what does the decision API cost",
20          "queries_tried":["decision model pricing"],
21          "candidate_queries":["typesafe pricing page","decision api rate limits","free tier"],
22          "round_index":1,
23          "results":[{"id":"a","title":"...","url":"https://...","snippet":"..."}]}' | jev search
24   ```
25 
26   Or call the `jev_search` tool with the same fields.
27 
283. Read `decision` and do exactly that:
29 
30| `decision` | What it means | What you do |
31|---|---|---|
32…