Jev versus incident runbooks: a practical comparison
An incident runbook is a sequenced response: page, mitigate, communicate. Jev can help pick which runbook from a page of alert text. It does not page people or roll back deploys.
Unofficial operate note. Official: code owns side effects. docs.typesafe.ai.
Comparison scope
PagerDuty/Opsgenie stay. Prometheus rules stay. Jev is optional on messy customer-reported incidents or multi-alert narratives.
Criteria that decide the architecture
| Axis | Jev (System One) | Incident runbooks |
|---|---|---|
| Page on-call | Your code after a gate | Runbook / paging tool |
| SEV label | Choice + confidence abort | Human IC |
| Mitigation steps | No | Wins |
| Numeric error rates | Code / metrics | Code |
Decision quality and control
Paging on a 0.55 Noul is how you burn the team. Fail to “page human IC” on timeout. Do not ask Jev to compare burn rates (math jaggedness).
Integration trade-offs
Alert text + recent deploy titles (filtered) → Choice over runbook ids + unknown → execute only on high confidence. Log everything in the incident timeline.
TypeSafe’s public models page lists jev-1.13 at $0.042 per million input tokens with output tokens free — a vendor claim, not a jev.pro measurement. Confirm on the models page before you bid.
When each approach fits
Prefer Jev when
- Customer-written incident text that does not match a metric name
Prefer Incident runbooks when
- The alert already maps 1:1 to a runbook
- Mitigation is the hard problem
Metrics page; Jev suggests a runbook; humans and automation execute the steps.
What this page does not claim
-
Not an IR platform.
-
No MTTR claims.
-
Schema-safe output is not the same as factual correctness.
-
No independent bake-off numbers live here.
FAQ
Can Jev roll back Kubernetes? No. Your controller does, if policy allows.
Should SEV be a Score? Only if levels are descriptive rubrics, not “SEV-1 means 5.” Humans still own severity.
Disclaimer
This is an independent unofficial site and is not affiliated with TypeSafe AI; official documentation is available at https://docs.typesafe.ai. Never treat jev.pro as TypeSafe official documentation. We do not sell, issue, or proxy API keys.
Hub: Comparisons. Siblings: vs security automation, observability guide, safe defaults. Canonical: https://docs.typesafe.ai.
Sources
Public TypeSafe or adjacent documentation only. No private claims.