Churn evaluation with Jev
Usage curves belong to your warehouse. Jev reads why someone is unhappy (cancel language, effort, save-offer fit). Code blends the two.
This unofficial page is the evaluation slice of the churn risk decisions pack. Intent: apply the Jev (TypeSafe System One) decision model to churn risk decisions evaluation. Primary search language: Churn 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): Evidence-first risk bands from tickets and language, with arithmetic in code — not a black-box churn-model clone or rival recipe IA.
Churn use-case context
Evaluation for churn risk decisions is a frozen harness, not a vibe check and not an opinion-blog “Jev review.” Labels: cancel-intent gold and whether the chosen save play was appropriate. We publish no unofficial accuracy.
Hub: Use cases. Compare, when the other tool is the real job: churn models.
Evaluation inputs
Replay the same contract you ship:
{
"account": { "id": "A-12", "plan": "pro", "seats": 40 },
"usage": { "wow_delta_bucket": "down_gt_30", "last_active_days_bucket": "21_plus" },
"tickets": { "latest": "We are moving to a competitor unless SSO ships." },
"nps": { "comment": "Setup took weeks." }
}Freeze questions, criteria, and jev-1.13.0. Record the response model.
Decision signals and actions
Score these, not a blog-grade star rating:
- Precision of exec_save pages
- Missed competitor-threat language
- Do not attribute revenue save to Jev without a designed experiment
Pair auto-act errors with handoff rate. If the success router never acts, you have not evaluated churn risk decisions — you have evaluated a human queue.
Do not treat a Noul of 0.5 as a “medium” churn risk decisions 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 churn risk decisions, treat exec_outreach_or_discount as the high bar (exec outreach or a commercial concession). 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 account language + pre-aggregated usages. 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 Churn pack? Start with Churn failure modes and Churn production rollout. Cluster hub: Use cases.
Can Jev replace our churn model? No. Keep warehouse risk; use Jev on unstructured complaints and save-offer fit.
TypeSafe mentions churn in the use-case map — is that a product? It is an example of more questions on ticket state, not a separate TypeSafe churn API.
What this page does not claim
- No causal save-rate numbers.
- Not a billing system.
- 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.