Use cases· Last updated 2026-09-21

Email input contracts with Jev

A draft exists (human or LLM). Jev judges policy, tone, and whether a promise is unsupported. Code sends, holds, or requests a rewrite. Jev does not deliver mail.

This unofficial page is the input contracts slice of the outbound email decisions pack. Intent: apply the Jev (TypeSafe System One) decision model to outbound email decisions input contracts. Primary search language: Email 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): Send/hold/rewrite as typed decisions + policy excerpts — not a clone of email-automation IA or a drip-builder page.

Email use-case context

An input contract is the allow-list of fields you will ever POST for outbound email decisions. It is a decision contract for the email draft + recipient context: 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: email automation.

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 outbound email decisions:

{
  "draft": { "subject": "Your Q4 discount", "body": "Locked 40% off if you reply today." },
  "recipient": { "segment": "trial", "consent_email": true },
  "policy": { "promises": "Do not invent discounts not in offer_table.", "tone": "No urgency dark patterns." },
  "offer_table": { "trial_discount_pct": 20 }
}

Bind paths: draft.subject, draft.body, policy.promises, offer_table.trial_discount_pct.

Refuse at the wrapper (do not send):

• the full CRM timeline
• MIME / HTML chrome
• other recipients’ messages (BCC leaks)

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:

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” outbound email decisions 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 policy_ok. TypeSafe’s confidence-gated examples use a lower bar for recoverable reads than for irreversible actions. Those numbers are illustrations. For outbound email decisions, treat send as the high bar (sending to a real recipient). Tune on labels — see offline evaluation.

Evaluation and rollout notes

Version the contract (field list + criteria git SHA) next to the pinned model. Replay send / hold / rewrite gold from brand+legal, plus policy-violation gold 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

FAQ

What happens if I send the whole warehouse row? jev-1.13 loses accuracy as distractors grow (official jaggedness note). Drop the full CRM timeline. 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 Email pack? Start with Email decision workflow and Email evidence collection. Cluster hub: Use cases.

Does this page sell email infrastructure? No. It is an unofficial decision-layer pattern. We do not sell keys or ESP access.

Can Jev write the email? Not in this workflow. Generate elsewhere; Jev gates. That keeps cite/send decisions inspectable.

What this page does not claim

• Not an ESP or CDP.
• No deliverability benchmarks.
• 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.