Jev home command scope

Identify the device scope of a household command

Provide the command and device catalog. Distinguish one named device from a room, the whole home or another explicit set before resolving any action.

How broad is the requested target?Live API
Try an example

One named device is the complete target.

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.

Classify the explicit target set using the supplied device catalog.

Decision rules and labels
Single deviceOne roomWhole homeOther explicit scopeNeed scope
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

Naming a kitchen lamp does not mean every light in the kitchen.

The corner-lamp preset names one device and uses the kitchen only to locate it. The kitchen-lights preset explicitly says all lights in that room. Those commands therefore have different target scopes even though both mention the kitchen.

The two-room preset is explicit but falls outside the three common scopes. It receives Other explicit scope rather than being stretched into Whole home. A reference such as those remains unresolved without a supplied target set.

The linked voice-command example separates scope from device kind and downstream actions. This original window keeps that boundary: it returns a scope label without connecting to Home Assistant or changing a device.

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 home command scope.

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

    Add the information to check

    Provide the command and device catalog.

  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 Single device, One room, Whole home, Other explicit scope, Need scope. 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 scope 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
Named desk lampSingle device100%
Kitchen lightsOne room100%
Lights everywhereWhole home99.0%
Two roomsOther explicit scope100%
One lamp in a roomSingle device100%
Unresolved referenceNeed scope100%

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

  • Testing explicit target scope in household commands
  • Distinguishing one named device from a room-wide request
  • Finding unresolved references before target selection

Outside this demonstration

  • Executing smart-home commands
  • Discovering devices on a network
  • Inferring device states from a command
Example FAQ

Questions about home command scope.

Input scope and downstream handling determine what this judgment means.

Does a room name always mean One room?

No. A command can name one device in a room. One room requires the stated scope to cover all devices of a kind in that room.

What happens to a command covering two rooms?

When the set is explicit it is Other explicit scope. It is not silently expanded to every room in the home.

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 home command scope input

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