Analytics human handoff with Jev
On-call already drowns in threshold alerts. Warehouses and anomaly detectors still own the math. Jev judges whether the written incident is actionable given numbers you already computed. It does not detect spikes or query the warehouse.
This unofficial page is the human handoff slice of the analytics alert triage pack. Intent: apply the Jev (TypeSafe System One) decision model to analytics alert triage human handoff. Primary search language: Analytics Jev human handoff. 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): Alert-class + actionability on narrative + precomputed bands — not a clone of a BI-alert product or anomaly-SaaS IA.
Analytics use-case context
Handoff is a first-class outcome for analytics alert triage, not a failure of Jev. When the alert router cannot auto-act, a human sees a packed alert narrative + metric bands — not a chat transcript. We do not ask Jev to write the reviewer essay.
Hub: Use cases. Compare, when the other tool is the real job: analytics alerts.
Human Handoff inputs
Humans should see what the model saw (filtered), not the warehouse dump you correctly refused to POST:
{
"alert": { "id": "a-991", "title": "Checkout p95 up", "body": "p95 2.1s vs 1.2s baseline; error rate flat." },
"bands": { "p95_ratio_band": "1.5-2x", "error_rate_delta_band": "flat" },
"runbook": { "page": "Page if latency ≥ 1.5× and user-facing checkout, unless error_rate also explains it." }
}Decision signals and actions
| Signal | Typical reason enum (you name it) |
|---|---|
| klass other / low confidence | analyst_review |
| page_now mid-band | ambiguous_page |
| severity high + noise klass | inconsistent |
| Missing bands | do_not_call_jev |
These are application outcomes next to HTTP 200, not invented TypeSafe status codes.
Send the reviewer:
- alert.id + filtered body
- bands + runbook version
- answers + probabilities
- Whether a page already fired
Do not treat a Noul of 0.5 as a “medium” analytics alert triage score — it means yes and no are equally likely. Conjunctions stay in your code.
Guardrails and escalation
Do not page humans on a single Score unless your conjunction says so. Pair with confidence thresholds. TypeSafe’s confidence-gated examples use a lower bar for recoverable reads than for irreversible actions. Those numbers are illustrations. For analytics alert triage, treat page_oncall as the high bar (paging on-call or auto-suppressing a user-facing alert). Tune on labels — see offline evaluation.
Evaluation and rollout notes
Write the gold label back into the offline set. That is how floors move. 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 | you are here |
| What to persist | audit trail |
| How it breaks | failure modes |
| Labeled replay | evaluation |
| Shadow → canary | production rollout |
FAQ
Is handoff a Jev failure? No. It is a first-class outcome. Abstention is “no auto action”; handoff is the queue you send that case to (glossary).
Should Jev draft the reviewer note? No. Send structured answers. Generation is the wrong job.
Where is the rest of the Analytics pack? Start with Analytics confidence thresholds and Analytics audit trail. Cluster hub: Use cases.
Can Jev replace the anomaly detector? No. Detectors emit numbers. Jev reads the write-up and your runbook excerpt.
Should we send the whole timeseries?
No. Summarize to bands in code. Distractors hurt jev-1.13 and still bill as input (vendor claim).
What this page does not claim
- Not a warehouse, detector, or APM.
- No MTTA/MTTD benchmarks.
- 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.