Jev evaluation retry disposition

Apply an evaluation policy to a recorded outcome

Provide the evaluation policy and observed outcome. Compare Pass, Retry, Escalate and Block decisions under the stated conditions without running another attempt.

What should follow this evaluation result?Live API
Try an example

Original input for the Pass outcome. Edit the evidence to send a new request.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This is an original synthetic demonstration adapted from the cited workflow discussion. It does not reproduce the source application or verify its performance, adoption or security claims.

Apply the stated evaluation policy.

Decision rules and labels
PassRetryEscalateBlockNeed evidence
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

A failure label does not specify the next step.

A transient timeout and a forbidden output can both fail an evaluation, but they need different dispositions. The first may qualify for a budgeted retry; the second belongs under the supplied block policy.

Retry availability is a precomputed fact. The model interprets the outcome against the policy while the application owns attempt counts, backoff and budgets. Escalate preserves an unresolved required judgment instead of claiming that a partial pass is complete.

The source describes a decision layer after an evaluation. These synthetic cases show that policy interpretation only; the window does not run an evaluator or start another attempt.

This is an original synthetic demonstration adapted from the cited workflow discussion. It does not reproduce the source application or verify its performance, adoption or security claims.

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 evaluation retry decisions.

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

    Add the information to check

    Provide the evaluation policy and observed outcome.

  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 Pass, Retry, Escalate, Block, Need evidence. 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 Need evidence 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
All checks passedPass99.0%
Transient provider errorRetry100%
No retry leftEscalate100%
Forbidden outputBlock98.0%
Unresolved quality checkEscalate100%
Missing policyNeed evidence88.0%

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

Source and example scope

Compare each saved result with its authored expectation. A disagreement remains in the fixture review; the call is not repeated to obtain a preferred label.

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.

Runnable offline example

Run one sample, then inspect the local packet

View the code example
Single-request replay
npm install @typesafe-ai/sdk@0.6.0
# Set TYPESAFE_API_KEY privately in your shell.
node run-choice-sample.mjs samples.json case-1
python preview_choice_workflow.py samples.json saved-api-results.json
Scope of this demo

Where this decision fits

Useful scope

  • Reviewing a supplied evaluation outcome
  • Keeping transient failure separate from a forbidden result
  • Replaying the exact synthetic requests and inspecting their distributions

Outside this demonstration

  • Claiming a test passed without its evidence
  • Running unlimited retries based on a model label
  • Treating six fixture expectations as measured production accuracy
Example FAQ

Questions about evaluation retry disposition.

The rubric explains the decision; the application owns the next step.

Can a passing tool test make the whole evaluation Pass?

Only when the supplied policy requires no other checks. An unresolved required factual review remains a reason to escalate.

Does Retry execute another request?

No. It is a pending disposition. Attempt limits and scheduling are owned by code, and the downloadable consumer performs no external action.

Does the leading probability measure production accuracy?

No. It is the model distribution for this one request. The six examples are functional checks with authored expectations, not a representative benchmark. Inspect disagreements and evaluate your own examples before using the label.

What happens when the API fails?

The window shows an error and supplies no fresh judgment. The downloadable runner sends one request without retries. Need evidence is a valid outcome about incomplete input; it does not stand in for a network or provider failure.

Try your own evaluation retry disposition input

Edit the evidence above or use the Playground to test another bounded question.