Jev Feels
Bind typed Jev questions to Ruby object fields for validation and routing.
Added to Jevfast
How it uses Jev
jev-feels binds named questions to object fields. It sends the field text and the registered Noul, Choice, or Score definition to Jev; callers receive a boolean/probability, selected choice, or ordinal score and use that typed result in validation or application logic. The documented SupportEmail example uses a Choice result to route a support request.
What Jev decides
Choose a support team for an emailExample answers · not a recorded Jev response · Source ↗
Question 1 · support team
YOUR APP
INSTRUCTION
Choose the support team that should handle the email, using the defined team descriptions.
STATE
The documented example supplies the SupportEmail body as state and asks which team should handle the request. The options and meanings below are the README's declared definition; the illustrative selection does not claim a captured Jev result.
JEV · CHOICE
- billing
- technical
- other
App workflow
- Define the app vocabulary
Register named questions with Jev.define, including descriptions and Choice or Score values where needed.
- Bind questions to a field
Use Jev::Model declarations such as feels, decide, or score to read text from an object, or call the string refinement/API directly.
- Send and type the result
The client builds a Jev request from the field text and definition, then returns a typed result or a convenient collapsed value.
- Apply the decision
Use the result in validation, routing, batching, pattern matching, or Jev.match; uncertainty can be handled with configured thresholds or confidence.
Why it is interesting
It turns repeated natural-language decisions into a small, typed application vocabulary. The same definitions can serve Rails models, plain Ruby objects, string refinements, batch calls, and pattern matching while keeping the underlying Jev request out of each caller.