HR human handoff with Jev
Inbound applications and tickets mix eligibility, policy questions, and messy free text. The ATS, payroll, and your employment counsel still own outcomes. Jev can score job-related criteria you wrote. It is not an ATS and must not become a proxy for protected-class decisions.
This unofficial page is the human handoff slice of the HR screening operations pack. Intent: apply the Jev (TypeSafe System One) decision model to HR screening operations human handoff. Primary search language: HR Jev human handoff. Confirm patterns on docs.typesafe.ai. This site does not sell, issue, or proxy TypeSafe keys. Use a credential you already have from the console or a documented gateway.
Independent angle (cover ≠ clone): Job-criteria Nouls with an explicit do-not-encode-protected-class lint — not a clone of an ATS or HR-screening product page.
HR use-case context
Handoff is a first-class outcome for HR screening operations, not a failure of Jev. When the screening worker cannot auto-act, a human sees a packed application or HR ticket text — not a chat transcript. We do not ask Jev to write the reviewer essay.
Hub: Use cases. Compare, when the other tool is the real job: HR screening.
Human Handoff inputs
Humans should see what the model saw (filtered), not the warehouse dump you correctly refused to POST:
{
"app": { "id": "c-190", "text": "5 years Python; no work auth mentioned; relocating July." },
"role": { "must": "Python in production; authorized to work without sponsorship this cycle." },
"ticket": { "type": "inbound_app" }
}Decision signals and actions
| Signal | Typical reason enum (you name it) |
|---|---|
| screen other / low confidence | recruiter_review |
| work_auth_clear low | hold_docs |
| reject path | recruiter_confirm |
| Any protected-class lint | do_not_call_jev |
These are application outcomes next to HTTP 200, not invented TypeSafe status codes.
Send the reviewer:
- app.id + filtered text
- role.must version
- answers + probabilities
- Confirmation no auto-reject email went out
- Reason code you will store
Do not treat a Noul of 0.5 as a “medium” HR screening operations score — it means yes and no are equally likely. Conjunctions stay in your code.
Guardrails and escalation
Do not page humans on a single Score unless your conjunction says so. Pair with confidence thresholds. TypeSafe’s confidence-gated examples use a lower bar for recoverable reads than for irreversible actions. Those numbers are illustrations. For HR screening operations, treat auto_reject as the high bar (auto-rejecting a candidate or taking employment action). Tune on labels — see offline evaluation.
Evaluation and rollout notes
Write the gold label back into the offline set. That is how floors move. Pin jev-1.13.0 (the versioned id) after you fit thresholds. jev-latest and the marketing line jev-1.13 can move. Log the response model. TypeSafe’s published list price for jev-1.13 is $0.042 per million input tokens (vendor claim — confirm on the models page); output tokens are free on that same page. Unused distractors still bill as input.
Official Python and JavaScript SDKs read TYPESAFE_API_KEY and retry documented 429/529. This site does not sell, issue, or proxy TypeSafe keys. Use a credential you already have from the console or a documented gateway.
Pack map
| Slice | Page |
|---|---|
| Graph and primitives | decision workflow |
What may enter state |
input contracts |
| What to gather first | evidence collection |
| Atomic rules | policy checks |
| Act / review / abstain | confidence thresholds |
| Reviewer payload | you are here |
| What to persist | audit trail |
| How it breaks | failure modes |
| Labeled replay | evaluation |
| Shadow → canary | production rollout |
FAQ
Is handoff a Jev failure? No. It is a first-class outcome. Abstention is “no auto action”; handoff is the queue you send that case to (glossary).
Should Jev draft the reviewer note? No. Send structured answers. Generation is the wrong job.
Where is the rest of the HR pack? Start with HR confidence thresholds and HR audit trail. Cluster hub: Use cases.
Is this an ATS or hiring decision system of record? No. It is an unofficial typed-screening pattern. Employment law stays with you and counsel.
Can we score “culture fit”? We recommend you do not. Keep criteria job-related and lint for proxies.
What this page does not claim
- Not an ATS, not employment-law advice, not a fairness certificate.
- No quality-of-hire numbers.
- Not official TypeSafe.
- Official TypeSafe status, or that jev.pro issues API keys.
- That a schema-constrained answer is automatically factually correct.
Disclaimer
This is an independent unofficial site and is not affiliated with TypeSafe AI; official documentation is available at https://docs.typesafe.ai.
Primary documentation: https://docs.typesafe.ai. Hub: Use cases.
Sources
Public TypeSafe or adjacent documentation only. No private claims.