Jev decision log reuse fit

Check whether an earlier decision still applies

Provide the prior resolution, its conditions and the current question. Compare a reusable answer with changed conditions or a genuinely different decision.

Does the prior resolution cover this question?Live API
Try an example

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

Source: Background discussion on X

Source and example scope

These fictional inputs and decision rules were written for this page. The linked X discussion provides background; the technical implementation follows TypeSafe's Choice contract.

Compare prior resolution, its conditions and current question.

Decision rules and labels
Reusable resolutionChanged conditionsDifferent questionUnclear applicabilityNeed 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

Reuse a resolution only with its conditions.

The first two presets state both questions, the recorded resolution, its required condition and the current facts. Jev compares this supplied record. It does not retrieve a decision log or decide whether the original resolution was correct.

A decision log records why a choice was made. Reusing the label without that condition can carry an outdated conclusion into a new task. The XML example exposes a changed condition rather than treating both tasks as identical exports.

Different question keeps unrelated decisions apart even when they share a word such as archive. Unclear applicability leaves an unresolved condition visible instead of assuming that nothing changed.

The output is context for a review step. It does not replace mandatory rules, silently approve a current action or prove that the recorded resolution was correct in the first place.

These fictional inputs and decision rules were written for this page. The linked X discussion provides background; the technical implementation follows TypeSafe's Choice contract.

Illustration of matching a question to supplied passages and identifying missing evidence
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 decision reuse.

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

    Add the information to check

    Provide the prior resolution, its conditions and the current question.

  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 Reusable resolution, Changed conditions, Different question, Unclear applicability, 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 Unclear applicability, 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
Same approved conditionReusable resolution94.0%
Target changedChanged conditions100%
Different decisionDifferent question96.0%
Condition unresolvedChanged conditions78.0%
Same words, different purposeDifferent question96.0%
No prior resolutionNeed evidence100%

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. 5 of 6 results matched the authored fixture expectations. For Condition unresolved, the expectation was Unclear applicability; the observed choice was Changed conditions.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 applicability of an explicit decision log
  • Avoiding stale conditions in repeated work
  • Replaying the exact synthetic requests and inspecting their distributions

Outside this demonstration

  • Treating any similar keyword as a reusable answer
  • Executing an old approval in a new context
  • Treating six fixture expectations as measured production accuracy
Example FAQ

Questions about decision log reuse fit.

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

Is this the same as checking memory freshness?

Freshness asks whether a note still reflects current evidence. This question asks whether a recorded resolution answers this particular current decision under its stated conditions.

Does Reusable resolution authorize an action?

No. It supplies relevant prior context. The current application still owns approvals, mandatory rules and execution.

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 decision log reuse fit input

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