Jev score anchor clarity

Check whether a score anchor stands on its own

Show one score anchor with its instructions and glossary. Check whether it defines a concrete condition, depends on an unavailable neighbor or only names an undefined degree.

score anchor clarityLive API
Try an example

The instructions supply the facts the anchor references.

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.

Inspect one anchor with its instructions and glossary.

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

Jev Score compares state with individual anchor descriptions. A useful anchor needs enough meaning in its own text and the shared instructions; a missing previous level cannot supply that meaning.

This demonstration uses Choice to review anchor wording. Standalone does not mean the full scale is complete, non-overlapping or calibrated. Those are separate properties that require the other anchors and representative inputs.

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 score anchor clarity.

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

    Add the information to check

    Show one score anchor with its instructions and glossary.

  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 Standalone, Neighbor, Degreeonly, Unclear. 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 Unclear 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
Concrete coverageStandalone96.0%
Missing previous levelNeighbor98.0%
An undefined adjectiveDegreeonly100%
A supplied termStandalone48.0%
Missing definitionUnclear84.0%
An empty anchorUnclear100%

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

Score anchor clarity: 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

  • Finding missing neighbor references
  • Checking whether a glossary defines anchor terms
  • Reviewing Score wording before representative tests

Outside this demonstration

  • Running a Score request
  • Checking unseen scale coverage or overlap
  • Calibrating a production scoring scale
Example FAQ

Using this example

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

Can an anchor use terms from the instructions?

Yes. The evaluator receives the instructions. A term defined there can make a short anchor concrete without repeating the definition.

Why does Standalone not mean the scale is good?

One anchor can be understandable but overlap another or leave gaps. This page only checks whether this one anchor can be interpreted from its supplied context.

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.