Incident response input contracts with Jev
Prometheus rules and PagerDuty already page on numeric thresholds. Jev is optional on messy customer-reported incidents or multi-alert narratives: which SEV band, which runbook class? It does not roll back deploys or page people.
This unofficial page is the input contracts slice of the incident response classification pack. Intent: apply the Jev (TypeSafe System One) decision model to incident response classification input contracts. Primary search language: Incident response 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): Runbooks and pagers stay; Jev classifies messy alert/customer text into SEV / runbook class, then code pages. Not a runbook-clone or status-page IA photocopy.
Incident response use-case context
An input contract is the allow-list of fields you will ever POST for incident response classification. It is a decision contract for the alert/customer incident narrative: 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: incident runbooks.
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 incident response classification:
{
"report": { "id": "INC-44", "text": "Checkout 500s since 14:02 UTC after the payments deploy. Status page still green." },
"signals": { "error_rate_bucket": "high", "payments_deploy_recent": true },
"policy": { "sev1": "SEV1 = complete checkout loss or safety." }
}Bind paths: report.text, policy.sev1, signals.error_rate_bucket.
Refuse at the wrapper (do not send):
- raw Prometheus matrices and flame graphs
- entire Slack incident channel history
- PII in customer tickets you have not redacted
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 |
|---|---|---|
sev |
Choice | sev1 / sev2 / sev3 / other |
runbook |
Choice | payments_deploy / dependency / capacity / unknown / other |
customer_impact |
Noul | Does the narrative describe user-visible loss vs policy.sev1? |
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” incident response classification 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 sev. TypeSafe’s confidence-gated examples use a lower bar for recoverable reads than for irreversible actions. Those numbers are illustrations. For incident response classification, treat page_sev1 as the high bar (paging SEV1 / rolling back via automation). Tune on labels — see offline evaluation.
Evaluation and rollout notes
Version the contract (field list + criteria git SHA) next to the pinned model. Replay SEV gold from ICs, runbook-class gold, and whether a page was warranted 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 raw Prometheus matrices and flame graphs. 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 Incident response pack? Start with Incident response decision workflow and Incident response evidence collection. Cluster hub: Use cases.
If metrics already say critical, should we wait for Jev? No. Metrics page now. Jev is for leftover messy text. See safe defaults.
Can Jev write the status-page update? Not in this workflow. Classification only. Generation is a different job.
What this page does not claim
- Not a pager, status page, or IR retainer.
- No MTTR or uptime claims.
- 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.