Jev NPC attention target

Choose what a fictional NPC should notice first

Provide perceived observations and the NPC's attention goal. Select a relevant candidate or preserve uncertainty when cues compete; the example does not infer hidden actors or trigger pursuit.

NPC attention targetLive API
Try an example

B is the observed condition relevant to the stated goal.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Choose A, B or C only from supplied observations perceived by this fictional NPC.

Decision rules and labels
ABCNoneReview
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

What the decision checks

An NPC should select from what its perception system supplied. Designer knowledge about a hidden player is a different input and must not silently become an observed clue.

Attention is narrower than an action. The result names a clue to examine; it does not tell a character to chase, attack, accuse or raise an alarm. The examples use fictional rooms and explicit attention goals.

The linked Heist One implementation has separate attention and intent fields and checks returned targets against permitted options. This independent text example isolates attention; visibility calculation, target validation and game actions remain application work.

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Illustration of choosing one tool from the supplied alternatives
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 npc attention selection.

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

    Add the information to check

    Provide perceived observations and the NPC's attention goal.

  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 A, B, C, None, Review. 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 Review 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
Open display caseB100%
Unexplained crashA100%
Visible leak clueC100%
Routine roomNone96.0%
Hidden information is not perceptionNone58.0%
Two equal cluesReview91.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

NPC attention selection: six recorded examples

The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.

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.

Replay options

Inspect saved outputs or request a new decision

View the code example
Two independent commands
# Offline: inspect the downloaded saved observations. No API key is needed.
python preview_choice_workflow.py samples.json saved-api-results.json

# Optional live request: install the SDK and set TYPESAFE_API_KEY privately.
npm install @typesafe-ai/sdk@0.6.0
node run-choice-sample.mjs samples.json case-1
# The live response prints to the terminal; it does not update saved-api-results.json.
Scope of this demo

Where this decision fits

Useful scope

  • Reviewing which observed clue deserves an NPC's attention.
  • Testing whether routine authorized activity is wrongly selected.
  • Separating designer-only information from a character's perception.

Outside this demonstration

  • Evaluating real people as suspicious or making a real security decision.
  • Computing visibility, pathfinding or pursuit behavior from a text label.
Example FAQ

Using this example

The input contract and these limits define what the result means.

Why is there both None and Review?

None means a complete observation list has no relevant cue. Review means required evidence or the rule for competing cues is unresolved.

Does choosing a target tell the NPC to chase it?

No. Attention identifies an observation. A separate action policy would decide whether and how the character responds.

Does the leading probability measure accuracy?

It describes the distribution over the supplied choices for this request. These six synthetic examples are functional tests with authored expectations, not a production accuracy benchmark.

Will a result change an external system?

No. The demo displays a label and distribution. The downloadable consumer produces a pending preview packet. Application code and a separate authorization policy would control any real action.

Test a different input

Edit the example above to see how a changed fact affects the decision, or open the Playground for another task.