Jev research evidence increment

Compare a new finding with existing research evidence

Provide the research question, accepted evidence and new finding. Check whether it repeats a known result, adds compatible detail or challenges a comparable finding under the supplied conditions.

research evidence incrementLive API
Try an example

A new wording does not add a new finding.

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.

Compare the new finding with the accepted evidence for the research question.

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

Novelty depends on the research question and the current evidence set. A repost of the same run is different from an independent repeat, even when the headline sounds new.

Keep measurement conditions visible. A result from another setup may extend the known scope; it should not be presented as a contradiction unless the comparison actually supports that reading.

The linked research pipeline distinguishes repeated findings, additional information and changes to a question's answer. These fictional software measurements demonstrate the editorial classification, not a real benchmark or automatic truth assessment.

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 matching a question to supplied passages and identifying missing evidence
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 research evidence comparison.

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

    Add the information to check

    Provide the research question, accepted evidence and new finding.

  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 Known, Adds detail, Challenges, 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
A repeated observationKnown100%
Additional reported dimensionAdds detail100%
Comparable disagreementChallenges100%
A new tested settingAdds detail99.0%
Conditions omittedReview99.0%
No existing evidenceReview97.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

Research evidence comparison: 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

  • Deduplicating research updates without losing new details.
  • Separating a new setting from a directly comparable disagreement.
  • Recording why more source context is needed before updating a brief.

Outside this demonstration

  • Treating a stored answer as true merely because it was accepted earlier.
  • Combining incompatible benchmarks into a single performance claim.
Example FAQ

Using this example

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

Does Challenges mean the old finding was wrong?

No. It means a comparable new observation conflicts with the stored answer. Both sources and their methods still need review.

Can a different setup add useful evidence?

Yes. It can extend the tested scope when the changed conditions are explicit. It should not silently replace a result measured under another setup.

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.