Use case · Gate · Score · Route
Use Jev for Recruiting Review
Assist structured screening with explicit gates, team routing, and scoring rubrics.
Input
Interview notes
Structured state sent to the decision layer.
Decision
advance + team + rubric scores
Should this candidate advance, where do they fit, and what concerns exist?
100Candidate notes
typedRubrics
reviewHuman in loop
auditStructured decisions
How it works
Turn the workflow into decisions.
Define explicit review criteria.
Pass interview notes as state.
Ask advancement and fit questions.
Score defined dimensions.
Keep human review for consequential decisions.
Try this pattern
Should this candidate advance, where do they fit, and what concerns exist?
state: {
source: "...",
context: "..."
}
question:
"Should this candidate advance, where do they fit, and what concerns exist?"
pattern:
"Gate · Score · Route"
When not to use Jev
If the task requires open-ended writing, deep synthesis, or novel code generation, keep a generative model in that step. Use Jev around the decision points.