Email audit trail 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 audit trail slice of the outbound email decisions pack. Intent: apply the Jev (TypeSafe System One) decision model to outbound email decisions audit trail. Primary search language: Email Jev audit trail. 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 audit trail for outbound email decisions is a decision trace: replayable inputs, typed answers, floors, and the action the send gate took. It is not a chat log and not a clone of a SIEM product page.
Hub: Use cases. Compare, when the other tool is the real job: email automation.
Audit Trail inputs
Persist the filtered payload (the contract), not whatever arrived at the edge:
{
"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 }
}Redact secrets before the object hits cold storage.
Decision signals and actions
Minimum fields:
- message id
- template version
- answers
- send/hold/rewrite
- ESP id after send
Also store usage.input_tokens (vendor meter) and the full probabilities map — argmax-only logs cannot explain a close policy_ok.
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
If you cannot explain sending to a real recipient from the trace, you are not ready to auto-act. 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
Traces are the eval warehouse. Replay against send / hold / rewrite gold from brand+legal, plus policy-violation gold after criteria or alias 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 |
input contracts |
| What to gather first | evidence collection |
| Atomic rules | policy checks |
| Act / review / abstain | confidence thresholds |
| Reviewer payload | human handoff |
| What to persist | you are here |
| How it breaks | failure modes |
| Labeled replay | evaluation |
| Shadow → canary | production rollout |
FAQ
Is the HTTP log enough? No. Persist the filtered state, full probabilities, floors, and downstream action as a decision trace.
May I log raw secrets? Redact in code. Jev will not be your DLP layer.
Where is the rest of the Email pack? Start with Email human handoff and Email evaluation. 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.
Sources
Public TypeSafe or adjacent documentation only. No private claims.