Jev form values on failure

Jev form values on failure. What happens to the input when submission fails?

Follow the failure branch and the state it owns before deciding whether entered values survive.

Does this failure path keep the entered values?Live API
Try an example

The failure branch explicitly clears the value owner.

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.

Inspect the supplied failure path and final value ownership.

Decision rules and labels
Values clearedValues preservedNot a failure pathNeed source
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

An error return before reset behaves differently from reset inside the error branch.

The first preset clears the editable values after a rejection. The return-before-reset preset leaves the same reset operation on the successful path, so its failure branch preserves the input. The location of the operation changes the result.

The restoration preset captures the values before submitting and writes them back after failure. A helper called reset cannot establish either outcome when its implementation is omitted. The demonstration therefore asks for both the failure branch and value ownership.

The source rule is marked review-only and looks for explicit value clearing on an error path. This original demonstration returns a behavior label from supplied code. It does not submit a form, run JavaScript or decide whether a deliberate clearing policy is appropriate.

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.

Conceptual illustration of supplied evidence entering a typed decision contract.
Shared conceptual illustration of the input contract; not a screenshot or measured performance result.
How it works

Run form values on failure in four steps.

Supply complete evidence, read the rule, run a judgment and keep the observation with its input.

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

    Supply the evidence

    Supply the failure branch, relevant helpers and value owner.

  2. Illustration of defining a question and its allowed choices

    Read the allowed outcomes

    The decision rule and the choice labels are sent with the evidence. Trace clearing, preservation or restoration only along the shown path.

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

    Run and inspect the distribution

    The window makes a fresh server-side API request. It displays the highest-probability label, elapsed request time and estimated token cost. A provider failure produces an error, not a missing-evidence label.

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

    Replay a pending local result

    Use the observation to plan a real form test separately. Download the requests and saved observations. The offline consumer validates their hashes and prints a pending packet without executing it.

Our API test

Recorded API observations

Recorded API observations
Original inputObserved labelLeading probability
Reset after rejectionValues cleared100%
Return before resetValues preserved82.0%
Restore saved valuesValues preserved100%
Successful reset onlyNot a failure path100%
Unknown reset helperNeed source90.0%
Form tag onlyNeed source57.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

Worked example

Replay the exact requests

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.

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.

Sample requests and authored expectations

Saved API observations

Single-request SDK runner

Offline preview consumer

Compare other decision examples

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 rejected form-submission path
  • Distinguishing success-only reset from failure clearing
  • Finding missing state or helper implementations

Outside this demonstration

  • Executing the submitted code
  • Proving a form works in a browser
  • Assuming every deliberate clearing policy is wrong
Example FAQ

Questions about form values on failure.

Input scope and downstream handling determine what this judgment means.

Does Values cleared automatically mean a defect?

No. It identifies the supplied behavior. A deliberate policy, such as removing sensitive input, requires a separate product and security review.

Why provide reset implementation details?

A reset helper can clear an error message, editable values or another state. Its name alone does not establish what users lose.

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 form values on failure input

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