Jev device protection role

Identify a household device's stated protective role

Give the device's complete functional description. Distinguish smoke, leak or entry warnings from convenience-only features without inferring danger from its name.

Is a protective function actually described?Live API
Try an example

The described purpose matches an explicitly listed warning function.

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.

First choose Need role if function evidence is missing, incomplete or conflicting.

Decision rules and labels
Protective functionConvenience functionNeed role
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 name such as Guardian does not establish a protective function.

The smoke and water-leak presets describe warning functions directly. The remote preset states a complete convenience-only role. These examples rely on what the device does, not on its brand or where it is installed.

The low-battery preset supplies neither a function nor a reliable inventory entry. The conflicting-record preset cannot establish whether the same unit is a remote or a smoke alarm. Both require role information instead of an assumption from the device name.

The cited battery blueprint includes a question about devices that protect people or the house. This original inventory demonstration isolates that role question. It does not assess working condition, predict a hazard or recommend when a battery can safely be replaced.

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 one spreadsheet row producing two separate classification results
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 device protection roles.

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

    Add the information to check

    Give the device's complete functional description.

  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 Protective function, Convenience function, Need role. 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 role 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
Smoke warningProtective function100%
Water leak warningProtective function100%
Television remoteConvenience function100%
Name and battery onlyNeed role100%
Conflicting inventoryNeed role80.0%
No device descriptionNeed role100%

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 device-inventory descriptions
  • Finding entries with missing function information
  • Separating explicit warning roles from convenience roles

Outside this demonstration

  • Assessing whether an alarm works
  • Prioritizing battery replacement by this result alone
  • Inferring hazards from a low-battery message
Example FAQ

Questions about device protection role.

Input scope and downstream handling determine what this judgment means.

Does Protective function mean the device is working?

No. The result describes the supplied role. It says nothing about testing, battery condition or whether the device will detect an event.

Can the name alone determine the category?

No. A suggestive name such as Guardian is not a functional specification.

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 device protection role input

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