Compliance evaluation 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 evaluation slice of the compliance evidence pre-score pack. Intent: apply the Jev (TypeSafe System One) decision model to compliance evidence pre-score evaluation. Primary search language: Compliance Jev evaluation. 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
Evaluation for compliance evidence pre-score is a frozen harness, not a vibe check and not an opinion-blog “Jev review.” Labels: gap / ready / review gold from control owners, plus production-mention gold. We publish no unofficial accuracy.
Hub: Use cases. Compare, when the other tool is the real job: compliance checklists.
Evaluation inputs
Replay the same contract you ship:
{
"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." }
}Freeze questions, criteria, and jev-1.13.0. Record the response model.
Decision signals and actions
Score these, not a blog-grade star rating:
- Missed staging-only blobs on a planted set
- Owner override rate
- Drift after prompt edits (replay; do not “feel” it)
Pair auto-act errors with handoff rate. If the GRC pre-scorer never acts, you have not evaluated compliance evidence pre-score — you have evaluated a human queue.
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
Promote a threshold only when the harness says auto-act error ≤ SLA and reviewers still catch the residual. 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
After any criteria edit, rerun before production. Cookbook lifts you see on TypeSafe pages are vendor claims — re-measure on your control prompt + evidence blobs. 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 | audit trail |
| How it breaks | failure modes |
| Labeled replay | you are here |
| Shadow → canary | production rollout |
FAQ
Will jev.pro publish a leaderboard for this use case? No. Measure on your labels. Vendor cookbook figures stay labeled as vendor claims.
What must stay frozen? Questions, criteria, and the pinned model id. Aliases can move.
Where is the rest of the Compliance pack? Start with Compliance failure modes and Compliance production rollout. 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.