Jev recovery approach change

Compare the methods in a failed attempt and a recovery

Supply the failed start and successful finish of the same task. Check whether the method changed or the same approach later succeeded, without claiming that the change caused success.

Was the successful approach different from the failed one?Live API
Try an example

The parsing method changed materially.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

The API-collected roundup links the cited project. Its pinned source defines the decision adapted here. These synthetic inputs and explicit missing-context outcomes are original to this demonstration. The window returns a label; it does not run the linked application, execute its downstream actions or verify its performance claims.

Compare the failed start and successful finish of the same task.

Decision rules and labels
Changed approachSame approachNeed recovery
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 successful retry can move the task forward without changing the method.

The CSV preset replaces comma splitting with a parser that handles quoted fields, then checks the same fixture. The manifest preset sends the identical request after a recorded service outage ends. Both supply a successful finish, but only the first changes the approach.

Passing a navigation test cannot establish recovery from a CSV parsing failure. The missing-start preset also stays unresolved because it supplies no earlier method to compare. Success and failure must concern the same task.

The source memory.outcome decision asks whether the way out of a problem differs from the initial approach. This original comparison returns a label from the supplied record. It does not establish causality, save a lesson or prove that a later retry will succeed.

The API-collected roundup links the cited project. Its pinned source defines the decision adapted here. These synthetic inputs and explicit missing-context outcomes are original to this demonstration. The window returns a label; it does not run the linked application, execute its downstream actions or verify its performance claims.

Illustration of checking a code change and reviewing a flagged line
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 recovery approach comparison.

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

    Add the information to check

    Supply the failed start and successful finish of the same task.

  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 Changed approach, Same approach, Need recovery. 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 recovery 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
Replace the parsing methodChanged approach100%
Use a different lookup methodChanged approach100%
External service recoversSame approach100%
Unchanged retry succeedsSame approach100%
Success belongs to another taskNeed recovery99.0%
Starting method missingNeed recovery100%

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

Replay the saved synthetic requests to inspect each recorded decision

Replay the saved synthetic requests to inspect each recorded decision. Authored expectations and model disagreements remain available; these examples are not a production accuracy benchmark.

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 the method used during a documented recovery
  • Separating changed approaches from unchanged retries
  • Finding mismatched task or missing starting evidence

Outside this demonstration

  • Claiming what caused a successful result
  • Writing lessons to an experience store
  • Forecasting reliability after one successful retry
Example FAQ

Questions about recovery approach change.

Input scope and downstream handling determine what this judgment means.

Does Changed approach prove the change caused success?

No. It identifies a material difference between supplied methods. Other conditions may also have changed, so a causal claim needs additional evidence.

Can Same approach still represent progress?

Yes. An unchanged request can succeed after an external service recovers. This page compares methods rather than deciding whether the task made progress.

Is the leading probability an accuracy measurement?

No. It is one value in the returned distribution over this request’s choices. The six synthetic fixtures have authored expectations; they do not measure production accuracy.

What happens on an API failure?

The window displays an error without a fresh judgment. An incomplete-input outcome describes the supplied evidence and is not used as a fallback for provider failure.

Try your own recovery approach change input

Edit the input above, or open the Playground to explore another decision.