Legal evaluation with Jev
Intake forms and emails mix contract, employment, privacy, and “please just send a letter.” Counsel still owns advice. Jev routes the text you already collected after your privilege/PII filter. It does not draft opinions or file anything.
This unofficial page is the evaluation slice of the legal intake routing pack. Intent: apply the Jev (TypeSafe System One) decision model to legal intake routing evaluation. Primary search language: Legal 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): Matter-type + privilege-risk Noul on redacted text — not a clone of a legal-intake SaaS page or “AI lawyer” voice.
Legal use-case context
Evaluation for legal intake routing is a frozen harness, not a vibe check and not an opinion-blog “Jev review.” Labels: matter-type gold from intake counsel, privilege-risk gold, and whether the queue was acceptable. We publish no unofficial accuracy.
Hub: Use cases. Compare, when the other tool is the real job: legal intake.
Evaluation inputs
Replay the same contract you ship:
{
"intake": { "id": "m-302", "text": "Vendor wants to use our logs to train models; need redlines this week." },
"playbook": { "privacy": "Training-on-logs or model-training clauses → privacy_queue." },
"meta": { "requestor_role": "procurement", "deadline_band": "this_week" }
}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 restricted_queue on planted privilege-seeking text
- Wrong matter_type at your floor
- False restricted (throughput vs safety)
Pair auto-act errors with handoff rate. If the matter router never acts, you have not evaluated legal intake routing — you have evaluated a human queue.
Do not treat a Noul of 0.5 as a “medium” legal intake routing 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 legal intake routing, treat auto_send_external as the high bar (sending work product outside the firm or closing a matter). 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 intake narrative (redacted)s. 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 Legal pack? Start with Legal failure modes and Legal production rollout. Cluster hub: Use cases.
Is this legal advice? No. Independent routing notes only. Counsel owns advice. Confirm facts on docs.typesafe.ai.
Can Jev write the contract redline? Not in this pack. Generation is a different job; keep this URL as typed routing.
What this page does not claim
- Not legal advice, not a law firm, not a privilege ruling.
- No accuracy 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.