Analytics policy checks 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 policy checks slice of the analytics alert triage pack. Intent: apply the Jev (TypeSafe System One) decision model to analytics alert triage policy checks. Primary search language: Analytics Jev policy checks. 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
A policy check is a typed question whose instructions + criteria are your rules about the alert narrative + metric bands. Jev scores compliance; the alert router enforces. This is not a certification, and it is not a photocopy of a rival “policy engine” page — we keep rules atomic and ANDed in code.
Hub: Use cases. Compare, when the other tool is the real job: analytics alerts.
Policy Checks inputs
Put policy text and the artifact in structured state (never hope the model memorized last quarter’s PDF):
{
"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." }
}Name alert.title, alert.body, runbook.page, bands.p95_ratio_band.
Decision signals and actions
| Id | Rule | Enforce |
|---|---|---|
math_in_code |
Threshold crossings computed before POST | monitor |
pii |
Strip user ids from alert bodies | wrapper |
page_budget |
page_now high + severity high → page; else ticket | code conjunction |
Typical primitives on the same request:
| 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.*? |
violations = [name for name, ans in policy_nouls.items() if ans.noul >= T_VIOLATION]
if violations:
return review(violations)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
Policy-in-state can be attacked (“ignore the policy”). High-risk paging on-call or auto-suppressing a user-facing alert still needs deterministic checks. 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
Gold labels are policy-versioned. A criteria edit without replay is how silent false-allows ship. 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 | you are here |
| 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
One Score for “compliant”? No. Atomic Nouls per rule, AND/OR in code. Money and dates: extract in code first (jaggedness).
If a regex can enforce it, should I still call Jev? Skip Jev. Official “how to build” guidance: keep deterministic rules in code when you can.
Where is the rest of the Analytics pack? Start with Analytics decision workflow and Analytics human handoff. 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.