Analytics input contracts 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 input contracts slice of the analytics alert triage pack. Intent: apply the Jev (TypeSafe System One) decision model to analytics alert triage input contracts. Primary search language: Analytics 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): Alert-class + actionability on narrative + precomputed bands — not a clone of a BI-alert product or anomaly-SaaS IA.
Analytics use-case context
An input contract is the allow-list of fields you will ever POST for analytics alert triage. It is a decision contract for the alert narrative + metric bands: 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: analytics alerts.
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 analytics alert triage:
{
"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." }
}Bind paths: alert.title, alert.body, runbook.page, bands.p95_ratio_band.
Refuse at the wrapper (do not send):
- raw time-series arrays for Jev to “eyeball”
- the entire dashboard JSON
- PII in query strings
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 |
|---|---|---|
klass |
Choice | latency / errors / data_quality / noise / other |
severity |
Score | ignore → user-facing outage language |
page_now |
Noul | Meets runbook.page given bands.*? |
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” analytics alert 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 klass. 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
Version the contract (field list + criteria git SHA) next to the pinned model. Replay class gold from on-call, page-now gold, and whether the page was justified 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 time-series arrays for Jev to “eyeball”. 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 Analytics pack? Start with Analytics decision workflow and Analytics evidence collection. 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.