Churn input contracts 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 input contracts slice of the churn risk decisions pack. Intent: apply the Jev (TypeSafe System One) decision model to churn risk decisions input contracts. Primary search language: Churn 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): 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
An input contract is the allow-list of fields you will ever POST for churn risk decisions. It is a decision contract for the account language + pre-aggregated usage: 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: churn models.
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 churn risk decisions:
{
"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." }
}Bind paths: tickets.latest, nps.comment, usage.wow_delta_bucket.
Refuse at the wrapper (do not send):
- event-level product analytics (pre-aggregate buckets in code)
- every ticket since 2019
- payment card data
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 |
|---|---|---|
cancel_intent |
Noul | Is the latest text a cancellation / competitor threat? |
effort |
Score | How painful is the described experience? |
save_offer |
Choice | none / education / discount_review / exec_outreach / other |
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” churn risk 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 cancel_intent. 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
Version the contract (field list + criteria git SHA) next to the pinned model. Replay cancel-intent gold and whether the chosen save play was appropriate 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 event-level product analytics (pre-aggregate buckets in code). 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 Churn pack? Start with Churn decision workflow and Churn evidence collection. 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.