Onboarding input contracts with Jev
Checklists already track “watch the video / ship the laptop.” Jev reads “I’m stuck because…” and picks a helper queue (access, equipment, accommodation). It does not mark tasks done and it does not approve legal forms.
This unofficial page is the input contracts slice of the onboarding exception routing pack. Intent: apply the Jev (TypeSafe System One) decision model to onboarding exception routing input contracts. Primary search language: Onboarding 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): LMS/HRIS own task state; Jev routes free-text blockers. Not a checklist-clone or HRIS IA photocopy — I-9 and legal holds never Jev-only.
Onboarding use-case context
An input contract is the allow-list of fields you will ever POST for onboarding exception routing. It is a decision contract for the new-hire or customer onboarding note: 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: onboarding checklists.
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 onboarding exception routing:
{
"note": { "id": "ONB-55", "text": "I finished payroll forms at my last employer. Also I cannot sign in to the IdP on a screen reader." },
"checklist": { "idp": "blocked", "laptop": "shipped" },
"policy": { "access": "IdP or assistive-tech blockers go to IT-access, not LMS nudges." }
}Bind paths: note.text, policy.access, checklist.idp.
Refuse at the wrapper (do not send):
- full HRIS profile novels
- I-9 images or tax PDFs
- unrelated benefits PDFs
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 |
|---|---|---|
blocker |
Choice | access / equipment / training / accommodation / already_done / other |
stuck_severity |
Score | How blocked is the person vs a simple FAQ? |
needs_human |
Noul | Should a coordinator reply (vs an LMS nudge)? |
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” onboarding exception routing 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 blocker. TypeSafe’s confidence-gated examples use a lower bar for recoverable reads than for irreversible actions. Those numbers are illustrations. For onboarding exception routing, treat provision_access as the high bar (provisioning access or closing a legal form). Tune on labels — see offline evaluation.
Evaluation and rollout notes
Version the contract (field list + criteria git SHA) next to the pinned model. Replay blocker-class gold from coordinators, plus accommodation gold (always human) 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 full HRIS profile novels. 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 Onboarding pack? Start with Onboarding decision workflow and Onboarding evidence collection. Cluster hub: Use cases.
Employee or customer onboarding? Same pattern: checklist owns tasks; Jev routes leftover language. Keep legal holds out of auto-act.
Can Jev fill the I-9? No. Never Jev-only on statutory forms.
What this page does not claim
- Not an HRIS, LMS, or immigration product.
- No time-to-productivity claims.
- 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.