Legal input contracts 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 input contracts slice of the legal intake routing pack. Intent: apply the Jev (TypeSafe System One) decision model to legal intake routing input contracts. Primary search language: Legal Jev input contracts. 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
An input contract is the allow-list of fields you will ever POST for legal intake routing. It is a decision contract for the intake narrative (redacted): if a field is not named in instructions, it should not be in state. That is how you beat noisy “dump the object” integrations — the rival-intent failure mode — without cloning anyone’s IA.
Hub: Use cases. Compare, when the other tool is the real job: legal intake.
Input Contracts inputs
Documented System One inputs: state (string, object, or array of text) and a questions map. English is the primary training language. Images, audio, and video are not accepted.
Allow for legal intake routing:
{
"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" }
}Bind paths: intake.text, playbook.privacy, meta.requestor_role.
Refuse at the wrapper (do not send):
- unredacted opposing-counsel email chains
- scans of passports or wet-ink signatures
- the entire matter folder as unused tokens
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.
Decision signals and actions
The contract exists so each primitive stays atomic:
| Id | Type | Job |
|---|---|---|
matter_type |
Choice | commercial / employment / privacy / disputes / other |
urgency |
Score | routine → hard deadline language |
privilege_risk |
Noul | Looks like advice-seeking or counsel comms that should stay restricted? |
If a new CRM field appears, either add a question that names it or drop it. Do not “just include it.” 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
Contracts are a guardrail: missing required text → do not call Jev (or ask a Noul “is enough information present?”). That is cheaper than a confident wrong matter_type. 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
Version the contract (field list + criteria git SHA) next to the pinned model. Replay matter-type gold from intake counsel, privilege-risk gold, and whether the queue was acceptable when either 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 |
you are here |
| 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 | evaluation |
| Shadow → canary | production rollout |
FAQ
What happens if I send the whole warehouse row?
jev-1.13 loses accuracy as distractors grow (official jaggedness note). Drop unredacted opposing-counsel email chains. 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.
Can I send images of the artifact? No. State is text (string, object, or array of text). Transcribe first.
Where is the rest of the Legal pack? Start with Legal decision workflow and Legal evidence collection. 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.