Jev narrative surprise cue

Compare a story ending with its stated expectation

Provide the passage's expectation and ending. Check whether the ending reverses or fulfills that expectation, or remains unresolved, using only the story facts you supply.

Does the ending overturn the stated expectation?Live API
Try an example

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

Source: Background discussion on X

Source and example scope

These fictional inputs and decision rules were written for this page. The linked X discussion provides background; the technical implementation follows TypeSafe's Choice contract.

Compare the stated expectation and ending.

Decision rules and labels
ReversalExpected endingNo expectationUnresolved endingNeed 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

An unusual event is not automatically a reversal.

The village arrival is a reversal because the setup says the keeper was expected alone. A description of a strange object without an established expectation would not provide the same comparison.

An open ending leaves the expectation unresolved. The model is not asked to invent what happened next, judge literary quality or measure a reader’s emotional reaction.

The source discussion notes uncertainty around surprise and humour. These fictional passages expose one narrow comparison; they are not an evaluation of the novels or model results mentioned there.

These fictional inputs and decision rules were written for this page. The linked X discussion provides background; the technical implementation follows TypeSafe's Choice contract.

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 narrative expectation check.

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

    Add the information to check

    Provide the passage's expectation and ending.

  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 Reversal, Expected ending, No expectation, Unresolved ending, 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
Unexpected visitorReversal100%
Promise fulfilledExpected ending100%
Description without setupNo expectation96.0%
Open endingUnresolved ending100%
Negative reversalReversal100%
No passageNeed evidence99.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

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

  • Annotating explicit reversals in fictional passages
  • Checking whether an excerpt supplies a complete comparison
  • Replaying the exact synthetic requests and inspecting their distributions

Outside this demonstration

  • Measuring literary quality or a reader’s surprise
  • Inventing an ending to resolve missing evidence
  • Treating six fixture expectations as measured production accuracy
Example FAQ

Questions about narrative surprise cue.

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

Can an ending be surprising without a stated expectation?

A reader may find it surprising, but this rubric deliberately requires an expectation in the supplied passage. That keeps the judgment tied to inspectable evidence.

Is an unresolved ending a missing passage?

No. The text may be present and deliberately open. Need evidence is reserved for an absent essential input; Unresolved ending describes the passage itself.

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 narrative surprise cue input

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