Jev laundry collection state

Check whether a finished laundry load still needs collecting

Describe the machine's cycle and whether the load was removed. Distinguish a finished load awaiting collection from an active programme, an emptied machine or missing evidence.

What state does the evidence establish?Live API
Try an example

Both completion and remaining load are supplied.

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.

Use supplied cycle evidence.

Decision rules and labels
Collection pendingCycle activeAlready collectedNeed cycle 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 low-power pause is not proof that the wash has finished.

The pending preset supplies two facts: the programme is complete and the load remains inside. The collected preset adds explicit removal after completion. Neither outcome follows from a power reading alone.

The pause preset deliberately includes low power during an unfinished programme. It stays Cycle active. The door-open preset lacks a mapping that would establish removal, so the window asks for collection evidence instead of treating every opening as an emptied machine.

The linked laundry blueprint combines power and optional door evidence to ask about a finished load. This original text adaptation displays stricter completion and removal boundaries. It reads only the input box and sends no reminder or appliance command.

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 routing a message into one of several label groups
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 laundry collection check.

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

    Add the information to check

    Describe the machine's cycle and whether the load was removed.

  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 Collection pending, Cycle active, Already collected, Need cycle 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 cycle 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
Finished, load insideCollection pending100%
Wash phaseCycle active100%
Load removedAlready collected100%
Low-power pauseCycle active100%
Door opened onlyCollection pending80.0%
Cycle unavailableNeed cycle 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 Door opened only, the expectation was Need cycle evidence; the observed choice was Collection pending.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

  • Testing laundry-reminder evidence rules
  • Distinguishing a programme pause from completion
  • Keeping removal assumptions explicit

Outside this demonstration

  • Reading a live power sensor
  • Operating a washing machine
  • Treating every door opening as collection
Example FAQ

Questions about laundry collection state.

Input scope and downstream handling determine what this judgment means.

Can a door sensor establish collection?

Only when the supplied mapping explicitly makes that event evidence of removal. Otherwise a door opening alone leaves collection unresolved.

Why does the low-power preset remain active?

Its programme record explicitly says it is paused before the final rinse. The power reading does not override that supplied state.

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 laundry collection state input

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