Jev on-call team match

Match affected services to their declared on-call teams

Give the affected services and a fictional ownership directory. Select their shared team or a cross-team handoff, keeping missing and conflicting owners visible.

on-call team matchLive API
Try an example

The named service has an explicit owner.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Use the supplied directory and explicitly affected services.

Decision rules and labels
PlatformSearchPaymentsCross-teamReview
A real response from the Jev API

Edit any input to explore a different decision. No request is sent until you run it.

Your next decision

Not run yet

Choose an example or write your own input, then run it to see the ranked choices.

Results are not stored by this site. Your submitted text is processed by the API provider.

The decision

What the decision checks

The ownership directory is part of the input, not model memory. Keep it current and identify services using trusted application metadata where possible.

A single service with contradictory owner records needs Review. That is different from two services whose unambiguous owners belong to different teams.

Cross-team describes the supplied ownership map. It does not choose an incident commander or determine which team caused the problem.

The source-linked on-call project demonstrates service-oriented triage. This page returns a proposed match and sends no notifications.

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Illustration of choosing one tool from the supplied alternatives
Illustration of the decision flow.
How it works

Try the example in four steps

Use the sample to understand the rule, then test your own input for on-call team routing.

  1. Illustration of adding the text or evidence for a decision

    Add the information to check

    Give the affected services and a fictional ownership directory.

  2. Illustration of defining a question and its allowed choices

    Confirm the question and labels

    Open the decision rules and keep the intended distinction between Platform, Search, Payments, Cross-team, Review. Edit the choices only when testing your own rule.

  3. Illustration of sending one input and comparing the returned choices

    Run the decision

    Use a sample first, then try your own input. Compare the selected label with the other returned probabilities.

  4. Illustration of reviewing a result and an uncertain item before using it

    Review the next step

    Review Review before using a result. The label is a decision about the supplied information, not an executed action.

Our API test

Recorded API observations

Recorded API observations
Original inputObserved labelLeading probability
Search endpointSearch100%
Payment pathPayments100%
Cross-team incidentCross-team100%
Unknown serviceReview99.0%
Trace dependencyPlatform99.0%
Conflicting directoryReview100%

These are six original synthetic inputs, tested once per request revision. The percentage is the leading option probability, not measured accuracy. Authored expectations and any disagreements remain in the downloadable evidence. 6 of 6 results matched the authored fixture expectations.Verified

Understand the results

On-call team routing: six recorded examples

The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.

Using the result in your application

The single-request SDK runner uses your private TYPESAFE_API_KEY. The offline consumer reads saved observations, checks request hashes and prints a pending output. It does not call the model or change any external system.

Replay options

Inspect saved outputs or request a new decision

View the code example
Two independent commands
# Offline: inspect the downloaded saved observations. No API key is needed.
python preview_choice_workflow.py samples.json saved-api-results.json

# Optional live request: install the SDK and set TYPESAFE_API_KEY privately.
npm install @typesafe-ai/sdk@0.6.0
node run-choice-sample.mjs samples.json case-1
# The live response prints to the terminal; it does not update saved-api-results.json.
Scope of this demo

Where this decision fits

Useful scope

  • Testing ownership routing before connecting a paging integration.
  • Finding incident summaries that omit a recognizable service.
  • Distinguishing an ownership-record conflict from a multi-service incident.

Outside this demonstration

  • Inferring a real person’s responsibility from prose.
  • Paging staff or claiming root cause from the selected team.
Example FAQ

Using this example

The input contract and these limits define what the result means.

Is a conflicting directory a cross-team incident?

Not under this rule. Conflicting records for one service leave ownership unresolved. Cross-team requires at least two affected services, each with an unambiguous owner.

Why not pick a team from the error text?

Library names and host names do not reliably identify the affected service. This contract requires an explicit affected-service fact and a matching directory entry.

What happens with several services?

Return the common team when they share an owner. Return Cross-team for several owners, or Review if an owner is missing.

Does the leading probability measure accuracy?

It describes the distribution over the supplied choices for this request. These six synthetic examples are functional tests with authored expectations, not a production accuracy benchmark.

Will a result change an external system?

No. The demo displays a label and distribution. The downloadable consumer produces a pending preview packet. Application code and a separate authorization policy would control any real action.

Test a different input

Edit the example above to see how a changed fact affects the decision, or open the Playground for another task.