Use cases· Last updated 2026-09-21

Triage input contracts with Jev

Incoming tickets need a queue, a temperature reading, and a sense of time pressure — then code routes. Jev judges; it does not write the reply.

This unofficial page is the input contracts slice of the support triage pack. Intent: apply the Jev (TypeSafe System One) decision model to support triage input contracts. Primary search language: Triage 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): Full triage pack (contracts → thresholds → handoff → audit) beats a single support-triage-choice recipe. We do not clone rival recipe IA.

Triage use-case context

An input contract is the allow-list of fields you will ever POST for support triage. It is a decision contract for the support ticket: 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: Support triage hub. Compare, when the other tool is the real job: keyword triage.

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 support triage:

{
  "ticket": { "id": "T-1042", "body": "Card charged twice after the outage.", "channel": "email" },
  "customer": { "plan": "pro", "open_incidents": 1 },
  "policy": { "p1": "P1 = safety issue or complete outage" }
}

Bind paths: ticket.body, policy.p1, customer.plan.

Refuse at the wrapper (do not send):

• full CRM activity novels
• raw HTML email chrome
• unrelated account notes
• images or screenshots (not accepted)

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” support triage 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 department. TypeSafe’s confidence-gated examples use a lower bar for recoverable reads than for irreversible actions. Those numbers are illustrations. For support triage, treat page_oncall as the high bar (paging on-call or issuing a refund flag). Tune on labels — see offline evaluation.

Evaluation and rollout notes

Version the contract (field list + criteria git SHA) next to the pinned model. Replay queue gold, urgency gold, and whether a human would have paged 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 full CRM activity novels. 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 Triage pack? Start with Triage decision workflow and Triage evidence collection. Cluster hub: Use cases.

Can Jev replace the support agent? No. It classifies and scores. Agents, macros, or humans act. See the support triage hub.

Should every company copy TypeSafe’s 0.5 intent floor? No. Official numbers are illustrations. Fit on offline evaluation.

What this page does not claim

• No invented triage accuracy or SLA.
• Schema-safe department ≠ the customer named the right product.
• Not official TypeSafe documentation.
• 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.