Onboarding audit trail 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 audit trail slice of the onboarding exception routing pack. Intent: apply the Jev (TypeSafe System One) decision model to onboarding exception routing audit trail. Primary search language: Onboarding Jev audit trail. 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 audit trail for onboarding exception routing is a decision trace: replayable inputs, typed answers, floors, and the action the onboarding coordinator router took. It is not a chat log and not a clone of a SIEM product page.
Hub: Use cases. Compare, when the other tool is the real job: onboarding checklists.
Audit Trail inputs
Persist the filtered payload (the contract), not whatever arrived at the edge:
{
"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." }
}Redact secrets before the object hits cold storage.
Decision signals and actions
Minimum fields:
- note.id + person id (internal)
- answers + pin
- queue
- whether access was provisioned (must be a human/IT system)
Also store usage.input_tokens (vendor meter) and the full probabilities map — argmax-only logs cannot explain a close blocker.
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
If you cannot explain provisioning access or closing a legal form from the trace, you are not ready to auto-act. 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
Traces are the eval warehouse. Replay against blocker-class gold from coordinators, plus accommodation gold (always human) after criteria or alias 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 |
input contracts |
| What to gather first | evidence collection |
| Atomic rules | policy checks |
| Act / review / abstain | confidence thresholds |
| Reviewer payload | human handoff |
| What to persist | you are here |
| How it breaks | failure modes |
| Labeled replay | evaluation |
| Shadow → canary | production rollout |
FAQ
Is the HTTP log enough? No. Persist the filtered state, full probabilities, floors, and downstream action as a decision trace.
May I log raw secrets? Redact in code. Jev will not be your DLP layer.
Where is the rest of the Onboarding pack? Start with Onboarding human handoff and Onboarding evaluation. 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.