KYC human handoff with Jev
Jumio-class vendors, sanctions lists, and liveness stay the system of record. Jev can ask whether the leftover narrative looks complete or internally inconsistent. It does not verify a passport and it is not a licensed KYC program.
This unofficial page is the human handoff slice of the KYC residual-text decisions pack. Intent: apply the Jev (TypeSafe System One) decision model to KYC residual-text decisions human handoff. Primary search language: KYC 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): Vendor attests identity; Jev only labels residual application text after structured checks. Fail closed — not a clone of KYC-vendor IA or an “AI KYC” product page.
KYC use-case context
Handoff is a first-class outcome for KYC residual-text decisions, not a failure of Jev. When the KYC queue router cannot auto-act, a human sees a packed application narrative + vendor result summary — 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: KYC vendors.
Human Handoff inputs
Humans should see what the model saw (filtered), not the warehouse dump you correctly refused to POST:
{
"application": { "id": "APP-19", "narrative": "I live in Lisbon but the business is registered in Delaware for tax reasons." },
"vendor": { "id_result": "pass", "sanctions_hit": false, "country_claimed": "PT" },
"policy": { "consistency": "Flag country or occupancy claims that contradict vendor country_claimed." }
}Decision signals and actions
| Signal | Typical reason enum (you name it) |
|---|---|
| Vendor fail / sanctions | do_not_use_jev |
| narrative_consistent high (contradiction) | text_inconsistency |
| residual other / low confidence | kyc_analyst |
| packet_complete Score low | incomplete_file |
These are application outcomes next to HTTP 200, not invented TypeSafe status codes.
Send the reviewer:
- APP id + filtered narrative
- Vendor result summary (not the raw biometric blob)
- Noul + Choice probabilities
- Which floor fired; account not opened
Do not treat a Noul of 0.5 as a “medium” KYC residual-text decisions 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 KYC residual-text decisions, treat auto_approve_account as the high bar (opening an account or attesting identity). 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 KYC pack? Start with KYC confidence thresholds and KYC audit trail. Cluster hub: Use cases.
Can Jev replace Jumio / Onfido / our list provider? No. Keep the vendor of record. This page is leftover text triage. See Jev vs KYC vendors.
Is this legal advice or a KYC certification? No. Unofficial field notes. Counsel and your program own attestation.
What this page does not claim
- Not a substitute for KYC/AML programs.
- No pass-rate or false-accept 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.