kelvinmade✳Independent maker ↗
JEV USE CASE

Security Incident Triage.

Turn alert context into bounded severity and routing decisions while preserving an analyst-review path.

THE DECISION CONTRACT
STATE

Endpoint alert, asset criticality, user history, observed process tree and containment status.

QUESTION

What is the next handling route?

CHOICES

close investigate contain escalate

TYPESCRIPT EXAMPLE

Ask for one bounded answer

This Vercel AI SDK-shaped example is illustrative. Check the current provider documentation before shipping.

import { experimental_evaluate as evaluate } from 'ai';

const result = await evaluate({
  model: 'typesafe-ai/jev',
  state: "Endpoint alert, asset criticality, user history, observed process tree and containment status.",
  questions: {
    decision: {
      type: 'choice',
      instructions: "What is the next handling route?",
      options: ["close","investigate","contain","escalate"]
    }
  }
});

// Validate permissions and thresholds before acting.
console.log(result.answers.decision);
SAFE IMPLEMENTATION

Keep the boundary clear

Guardrail

Never let a model suppress high-impact evidence by itself. Preserve raw telemetry and require review for uncertain or destructive actions.

  • Log the input, answer distribution, chosen threshold and resulting route.
  • Test on labelled examples from your own production distribution.
  • Send low-confidence, high-impact or out-of-distribution cases to a safer fallback.
  • Re-evaluate thresholds when the model or workflow changes.
PRIMARY SOURCES

Read before implementing

TypeSafe AI: Introducing System One Models and Jev ↗

Vercel: Jev available on AI Gateway ↗