Jev story context scope

Choose the relevant story context for a planned scene

Compare a fictional history note with a scene plan. Identify character context, a world constraint or a plot dependency, keeping unrelated history separate from the scene's requirements.

What role does this history note play in the scene?Live API
Try an example

Original input for the Character context outcome. Edit the evidence to send a new request.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This is an original synthetic demonstration adapted from the cited workflow discussion. It does not reproduce the source application or verify its performance, adoption or security claims.

Compare the planned scene with the history note.

Decision rules and labels
Character contextWorld constraintPlot dependencyUnrelated historyNeed 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

Choose context for the scene that is actually planned.

A long fictional history can contain useful constraints alongside details that do not affect the next scene. This example classifies the role a note plays in a supplied plan instead of asking the model to write the chapter.

Character context explains a relationship or motive. World constraint supplies a setting rule. Plot dependency points to an unresolved event that the scene needs to address. The distinctions help a writer inspect why a note is being loaded.

A familiar character name alone does not make a note useful. The pet-pebble fixture names Mira but explicitly disconnects the detail from the confrontation. The demo neither verifies a published canon nor invents hidden story facts.

This is an original synthetic demonstration adapted from the cited workflow discussion. It does not reproduce the source application or verify its performance, adoption or security claims.

Illustration of selecting a caption token for emphasis in an edit timeline
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 story context roles.

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

    Add the information to check

    Compare a fictional history note with a scene plan.

  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 Character context, World constraint, Plot dependency, Unrelated history, Need 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 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
A character motiveCharacter context98.0%
Setting ruleWorld constraint100%
Unresolved promisePlot dependency100%
Distant historyUnrelated history100%
Familiar name, unrelated detailUnrelated history100%
No scene planNeed 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. 6 of 6 results matched the authored fixture expectations.Verified

Understand the results

Source and example scope

Compare each saved result with its authored expectation. A disagreement remains in the fixture review; the call is not repeated to obtain a preferred label.

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

  • Organizing fictional scene context
  • Explaining why a retrieved history note is relevant
  • Replaying the exact synthetic requests and inspecting their distributions

Outside this demonstration

  • Generating a chapter or completing missing lore
  • Checking external copyrighted canon without its source
  • Treating six fixture expectations as measured production accuracy
Example FAQ

Questions about story context scope.

The rubric explains the decision; the application owns the next step.

Is Plot dependency the same as a setting rule?

No. A dependency comes from an unresolved event, such as a promised delivery. A setting rule describes how the fictional world operates.

Can one note have several roles?

Yes. These fixtures make one role primary. For notes with equally central roles, use a multi-question or multi-label contract rather than silently discarding a role.

Does the leading probability measure production accuracy?

No. It is the model distribution for this one request. The six examples are functional checks with authored expectations, not a representative benchmark. Inspect disagreements and evaluate your own examples before using the label.

What happens when the API fails?

The window shows an error and supplies no fresh judgment. The downloadable runner sends one request without retries. Need evidence is a valid outcome about incomplete input; it does not stand in for a network or provider failure.

Try your own story context scope input

Edit the evidence above or use the Playground to test another bounded question.