go-jev
Use typed Jev decisions in Go programs and UNIX command pipelines.
Added to Jevfast
How it uses Jev
The Go SDK accepts JSON-compatible state and typed questions through `Ask` for one question or `Evaluate` for a named question map. It returns structured Noul probabilities, Choice labels, or weighted Scores; the bundled CLI exposes these decisions to shell pipelines.
What Jev decides
Support-ticket typed questions (illustrative)Example answers · not a recorded Jev response · Source ↗
Question 1 · urgent
YOUR APP
INSTRUCTION
Decide whether the request is urgent.
STATE
The source README sends a JSON state with from=alice and text=refund me to two named questions in one Evaluate call.
JEV · NOUL
YesNo
Question 2 · frustration
YOUR APP
INSTRUCTION
Rate the customer's frustration on the ordered levels Calm, Frustrated, Very angry.
STATE
The source README sends a JSON state with from=alice and text=refund me to two named questions in one Evaluate call.
JEV · SCORE
0
App workflow
- Create client
Construct a client with API key and optional model, endpoint, timeout, or retry settings.
- Provide state and questions
Call Ask for one typed question or Evaluate with a state value and a named map of questions.
- Consume typed answers
Read the answer's Noul, Choice, or Score field and use it in application logic.
- Use CLI when useful
The bundled `jev-cli` supports direct typed commands, JSON questions, stdin, and line-oriented pipelines.
Why it is interesting
The package brings typed Jev requests into Go programs and Unix workflows, including JSON state, multiple named questions in one call, ordered options, line-by-line processing, and CLI exit status for yes/no decisions.