Compliance human handoff with Jev
SOC 2 / ISO rows have owners, cadence, and pass/fail. Jev can flag “this evidence blob never mentions production.” The control owner still attests. Jev is not the auditor and not the GRC system of record.
This unofficial page is the human handoff slice of the compliance evidence pre-score pack. Intent: apply the Jev (TypeSafe System One) decision model to compliance evidence pre-score human handoff. Primary search language: Compliance 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): Checklist is the control; Jev pre-scores whether evidence language looks complete. Owner still signs — not a GRC-clone or rival checklist-IA photocopy.
Compliance use-case context
Handoff is a first-class outcome for compliance evidence pre-score, not a failure of Jev. When the GRC pre-scorer cannot auto-act, a human sees a packed control prompt + evidence blob — 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: compliance checklists.
Human Handoff inputs
Humans should see what the model saw (filtered), not the warehouse dump you correctly refused to POST:
{
"control": { "id": "CC-6.1", "prompt": "Evidence must describe production access reviews this quarter." },
"evidence": { "title": "Access review export", "text": "We reviewed staging users in January." },
"policy": { "env": "Staging-only language is a gap for production controls." }
}Decision signals and actions
| Signal | Typical reason enum (you name it) |
|---|---|
| mentions_prod low | gap_queue |
| next other / low confidence | owner_review |
| completeness Score low | need_more_evidence |
| Legal hold on the control | skip_jev |
These are application outcomes next to HTTP 200, not invented TypeSafe status codes.
Send the reviewer:
- control.id + prompt version
- evidence excerpt as POSTed
- answers + suggested next
- Reminder that Jev did not pass the control
Do not treat a Noul of 0.5 as a “medium” compliance evidence pre-score 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 compliance evidence pre-score, treat mark_control_passed as the high bar (marking a control passed or signing attestation). 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 Compliance pack? Start with Compliance confidence thresholds and Compliance audit trail. Cluster hub: Use cases.
Can Jev be our auditor? No. It pre-scores language. Owners and auditors sign. See governance.
May we send screenshots? Not as images. Transcribe what the screenshot shows, then ask snap questions.
What this page does not claim
- Not an auditor, GRC, or certification.
- No readiness or pass-rate 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.