Jev household cycle timing fit

Review appliance-cycle timing under a comfort-first rule

Give cycle readiness, household disturbance and precomputed energy bands. Compare a run candidate with waiting for people or energy under the displayed comfort-first policy.

How does this timing scenario fit the rule?Live API
Try an example

The complete scenario satisfies the displayed energy condition without disturbance.

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.

Evaluate a ready cycle using supplied bands.

Decision rules and labels
Wait for peopleRun candidateWait for energyNeed context
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

Cheap electricity does not override the stated rule about waking somebody.

The quiet, cheap-energy preset and the sufficient-solar preset both meet the displayed energy condition. The sleeper preset has those same favorable bands but receives Wait for people because the rule gives disturbance priority.

Priority applies after resolving contradictory evidence. The conflicting-household preset cannot establish whether the cycle would disturb anyone, so it stays Need context. Missing energy bands also remain unresolved when no disturbance already settles the result.

The cited energy-window example considers electricity, solar and household activity. This original demonstration uses supplied categorical bands, not live prices or occupancy inference. Run candidate is a label for review; it does not start an appliance or calculate a saving.

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 appliance cycle timing.

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

    Add the information to check

    Give cycle readiness, household disturbance and precomputed energy bands.

  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 Wait for people, Run candidate, Wait for energy, Need context. 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 context 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
Cheap and quietRun candidate98.0%
Solar covers the cycleRun candidate99.0%
Would wake a sleeperWait for people100%
Costly with no surplusWait for energy99.0%
Conflicting household stateNeed context96.0%
Missing bandsNeed context99.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

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

  • Comparing comfort and supplied energy conditions
  • Testing precedence in a household timing policy
  • Keeping contradictory input out of an action route

Outside this demonstration

  • Starting an appliance
  • Calculating a tariff or saving
  • Inferring who is home
Example FAQ

Questions about household cycle timing fit.

Input scope and downstream handling determine what this judgment means.

Where do the energy bands come from?

The person or system supplying the input must compute them beforehand. This page treats the supplied bands as evidence and performs no tariff calculation.

Does Run candidate start the cycle?

No. It is only the result of this text policy. Readiness checks and any device command belong in a separate system.

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 household cycle timing fit input

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