Jev binary criteria alignment

Check the meaning of true and false criteria

Provide a proposition and both outcome definitions. Check whether true and false match the question, are reversed or introduce a different condition.

binary criteria alignmentLive API
Try an example

Both definitions follow the stated proposition.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This original wording-review exercise applies guidance in the repository explicitly named by the cited post. The inputs and review labels are ours. The repository teaches Jev integration; it does not implement this page's analyzer or establish its accuracy.

Use Needcriteria first if the proposition or either criterion is absent or too vague to compare.

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

This check reads the question and both definitions together. A pair of individually plausible descriptions can still be reversed under the keys true and false. Negative questions need the same explicit reading.

Noul can be called without optional criteria. Needcriteria does not reject that API format; it means this particular alignment review lacks the wording it compares. An alignment result does not explain every wrong model answer or prove the request is accurate.

This original wording-review exercise applies guidance in the repository explicitly named by the cited post. The inputs and review labels are ours. The repository teaches Jev integration; it does not implement this page's analyzer or establish its accuracy.

Illustration of one spreadsheet row producing two separate classification results
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 binary criteria alignment.

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

    Add the information to check

    Provide a proposition and both outcome definitions.

  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 Aligned, Reversed, Inconsistent, Needcriteria. 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 Needcriteria 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
Matching polarityAligned97.0%
Both labels swappedReversed96.0%
Different conditionInconsistent93.0%
Missing false definitionNeedcriteria95.0%
A negative propositionAligned99.0%
Both sides affirmInconsistent99.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

Binary criteria alignment: 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 explicit Noul criteria
  • Spotting reversed truth labels
  • Checking negative questions before fixtures

Outside this demonstration

  • Declaring optional criteria mandatory
  • Diagnosing every model error from one response
  • Automatically changing production question definitions
Example FAQ

Using this example

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

Are missing criteria an invalid Noul request?

No. The criteria can be optional in the API. This wording check needs both definitions, so its contract expects Needcriteria when either is absent. A model response can still disagree; compare the result with the supplied rule.

Why is a negative question not automatically reversed?

True should support the proposition as written. If the question asks whether something is absent, a definition of absence is correctly aligned with true.

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.