HR input contracts 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 input contracts slice of the HR screening operations pack. Intent: apply the Jev (TypeSafe System One) decision model to HR screening operations input contracts. Primary search language: HR Jev input contracts. 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
An input contract is the allow-list of fields you will ever POST for HR screening operations. It is a decision contract for the application or HR ticket text: if a field is not named in instructions, it should not be in state. That is how you beat noisy “dump the object” integrations — the rival-intent failure mode — without cloning anyone’s IA.
Hub: Use cases. Compare, when the other tool is the real job: HR screening.
Input Contracts inputs
Documented System One inputs: state (string, object, or array of text) and a questions map. English is the primary training language. Images, audio, and video are not accepted.
Allow for HR screening operations:
{
"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" }
}Bind paths: app.text, role.must.
Refuse at the wrapper (do not send):
- photos, CVs as images, or video interviews
- demographic / protected-class fields — drop in the wrapper
- the entire employee file for a policy ticket
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.
Decision signals and actions
The contract exists so each primitive stays atomic:
| Id | Type | Job |
|---|---|---|
screen |
Choice | advance / hold_docs / reject_role_mismatch / other |
must_have_fit |
Score | none of the musts → all musts evidenced |
work_auth_clear |
Noul | Text clearly meets role.must work-auth clause? |
If a new CRM field appears, either add a question that names it or drop it. Do not “just include it.” 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
Contracts are a guardrail: missing required text → do not call Jev (or ask a Noul “is enough information present?”). That is cheaper than a confident wrong screen. 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
Version the contract (field list + criteria git SHA) next to the pinned model. Replay screen gold from recruiters, work-auth gold, and whether a human would have held docs when either changes. 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 |
you are here |
| What to gather first | evidence collection |
| Atomic rules | policy checks |
| Act / review / abstain | confidence thresholds |
| Reviewer payload | human handoff |
| What to persist | audit trail |
| How it breaks | failure modes |
| Labeled replay | evaluation |
| Shadow → canary | production rollout |
FAQ
What happens if I send the whole warehouse row?
jev-1.13 loses accuracy as distractors grow (official jaggedness note). Drop photos, CVs as images, or video interviews. 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.
Can I send images of the artifact? No. State is text (string, object, or array of text). Transcribe first.
Where is the rest of the HR pack? Start with HR decision workflow and HR evidence collection. 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.